Gateway Script httpGet CONNECTION RESET ERROR

If it’s installed on Windows then by default it’s running as the ‘LocalService’ user (I think… this is a Windows thing and I’m not really a Windows guy). This is known to cause other weird issues too, like the inability to access network drives without explicitly mapping them.

Not certain this is your issue, just a possibility.

You’re probably right about it being a permissions issue, however, how can I modify my gateway OS to allow it to access this url? That is the real question?

I guess, why does the script console run the script as a different user? Shouldn’t it be the same built in gateway “user”?

No… the script console is running in the Designer, which you launched as your user.

So how do I fix this so it runs on the gateway? With your logic, what are the restrictions on what gateway scripts can do?

To execute in the gateway scope you would run it in a tag change script, timer script, or something else that executes on the gateway.

There’s no console or playground for executing in gateway scope.

There aren’t any intentional restrictions within Ignition either. Something external to Ignition is closing down this connection.

I found this interesting:

To test, I am now running the ignition gateway service as an administrative account.

Looks like that didn’t work.

In that other thread, running as an administrator didn't work, either. Did you try the proxy settings as described at the bottom?

I was going to, but I can’t find the ignition.conf file…did it move with a newer version?

Here is where mine sits:

C:\Program Files\Inductive Automation\Ignition\data

Found it, now adding the lines in the config file- hopefully it helps.

I have rested that this is an IT problem and I have taken it as far as I can…I hate to do this but 1-800-HELP-DESK.

Try running the Ignition service as your own OS user:

  1. Open Services
  2. Navigate to the ‘Ignition Gateway’ service
  3. Change the ‘Log On As’ to your own username. You may need to use the ‘browse’ dialog to bring in your qualified domain name correctly.

I did that without success.

A long shot, but we had issues with the URL certificate being rejected.
We had to add the URL to the java allowed access on the Gateway Java settings.
Then use the bypassCertValidation=True on the HttpGet call.

No, that didn’t help.

Was this issue resolved? I am experiencing the exact same response to the httpGet function. Also retrieving weather data. Seems to work occasionally on another machine, if executed as a timer script once per hour or so…

When using httpS
then also add these proxies. ( note the S in Dhttps)
wrapper.java.additional.10=-Dhttps.proxyHost=xx.xx.xx.xx
wrapper.java.additional.11=-Dhttps.proxyPort=xxxx