Shared script behave differently depending on the way it is lauched

Ignition Version : 7.8.3

Hello all,

I have a stange behavior with shared scoped scripts. I have made a simple one to show the problem:

In Shared, i have a simple script :

def refreshTest():
retour =“”)
return retour

When I call it from the Script Console or a Button, it works just fine. When I put it in a TagEvent Script or Gateway timer script, the script fails and the logs read :

13:42:13 ScriptDispatcher ([#######]WS/TOP_TEST 1, valueChanged) Error executing tag event script: null
Traceback (most recent call last):

File “<tagevent:valueChanged>”, line 6, in valueChanged
File “<module:shared.WS>”, line 72, in refreshTest

at org.python.core.Py.fromIOException(
at org.python.core.Py.IOError(
at com.inductiveautomation.ignition.common.script.builtin.AbstractNetUtilities.httpGet(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.inductiveautomation.ignition.common.script.ScriptManager$
at org.python.pycode._pyx10.refreshTest$3(<module:shared.WSEDF.WS>:74)
at org.python.pycode._pyx10.call_function(<module:shared.WSEDF.WS>)
at org.python.pycode.pyx9.valueChanged$1(<tagevent:valueChanged>:6)
at org.python.pycode.pyx9.call_function(<tagevent:valueChanged>)
at org.python.core.PyFunction.function___call
at com.inductiveautomation.ignition.common.script.ScriptManager.runFunction(
at com.inductiveautomation.ignition.common.sqltags.scripts.TagScriptManager$
at com.inductiveautomation.ignition.common.sqltags.scripts.AbstractTagScript.invoke(
at com.inductiveautomation.ignition.common.sqltags.scripts.TagScriptManager$Task.invoke(
at com.inductiveautomation.ignition.common.sqltags.scripts.TagScriptManager$
at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$
at java.util.concurrent.Executors$ Source)
at Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)|

In both cases, i use the exact same instruction to execute my shared script :


The Gateway and the client both run on the same machine (same internet settings for proxy).
My guess was that the Internet proxy settings would not apply to the JVM so I added those lines in the ignition.conf settings:“localhost|”

with no luck.

I’m a bit stuck with this. If anyone has an idea about all this, it would be very welcomed.


What OS are you running on?

And did you try with an http address too?

If you’re running on Windows f.e. the Ignition gateway will run under a different user than the client, and perhaps the service user doesn’t have access to the SSL certificates needed to make a connection with an https address.

You could also try more native python clients, though I’ve also had https issues with those.

I indeed use Windows. I gave a try to the user account name and changed it to my windows account name.
The service works fine but the webservice still not goes out.

The idea to try an http address was fine has it could confirm that it could work like that (the http request can go outand retreive data that indicate that the document was moved to the https address)

When using httpS
then also add these proxies. ( note the S in Dhttps)

1 Like

I am pretty sure is not recommended anymore. Use and from there use get. Perhaps that will fix the issue.

Thanks, but we are still v7. And looking over the forum for a week I could not get my https get instructions to complete without the IOError.
Adding the proxies did indeed fix it for me (adding the https proxies)


Is the proxy additionnal parameter still available for version 8.1 ?

On a new server, I installed a 8.1 version and added the proxy parameters (Dhttp(s).proxyHost and Dhttp(s).proxyPort) in the ignition.conf file. From there, the httpGet won’t work (IO Error).

On the same server, when I restore the 7.8.3 version, it works perfectly.

So my problem seems to be located on Ignition but I’ve tried all that was suggested here without success.

Anyone have an idea about this ? Any help will be greatly appréciated.


I believe those properties will work with the HttpClient class, which you can use via the script function. Basically, you create a client object, and then you make your GET call via that. There are some good examples in the documentation, hopefully it is enough to get you going…