Launcher not connecting - wrong gateway address

I am trying to access the Ignition designer/launcher remotely, using port-forwarding.
Port-forwarding has been setup to forward ports 8088/8043 to the remote ignition gateway.
I can access the gateway web interface by going to 127.0.0.1:8088, so I know that is working.
I downloaded the designer.jnlp from the gateway webpage, and because I’m using port-forwarding remotely, I modified the designer.jnlp file, changing the lines:

    <property name="javaws.sr.gateway.addr.0" value="10.8.50.10:8088:8043/main"/>
    <property name="javaws.sr.gateway.addr.1" value="10.8.50.11:8088:8043/main"/>

to

    <property name="javaws.sr.gateway.addr.0" value="127.0.0.1:8088:8043/main"/>
    <property name="javaws.sr.gateway.addr.1" value="127.0.0.1:8089:8044/main"/>

(where 10.8.50.10 is the internal address of the gateway)

However, when I run it the launcher can’t connect. It shows the error
“Error launching application: SocketTimeoutException: connect timed out”

The console shows it is trying to download manifest from 10.8.50.10:8088, even after changing designer.jnlp.

Starting Bootstrap Loader v3.0
Connect Step [attempt 1] connecting to: http://10.8.50.10:8088/main...
Downloading manifest at http://10.8.50.10:8088/main/system/launchmf/D?os=osx&arch=x64
Connect attempt 1 for address http://10.8.50.10:8088/main failed.
java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
	at sun.net.www.http.HttpClient.New(HttpClient.java:339)
	at sun.net.www.http.HttpClient.New(HttpClient.java:357)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)
	at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:146)
	at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.downloadManifest(ConnectStep.java:104)
	at com.inductiveautomation.ignition.client.launch.steps.ConnectStep.run(ConnectStep.java:48)
	at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:32)
	at java.lang.Thread.run(Thread.java:748)

I’ve tried clearing the java cache and running it again, but the results are the same.

How is the launcher still trying to download from 10.8.50.10?
Is there a way to force it to look at another address (ie. 127.0.0.1)?

Try deleting the .ignition/cache folder from your user directory instead of clearing the general Java cache.

Thanks.
It still appeared to behave the same, but I have downloaded the native client launcher and input the address manually and it is working.

So, using the client launcher I can launch the designer and the published projects. However, launching a project from the designer doesn’t work, so I can’t run the staging version of a project.

You can add command line arguments to the shortcuts generated by the client launcher to specify certain flags, including:
javaws.sr.project.version=Staging

https://docs.inductiveautomation.com/display/DOC79/Native+Client+Launchers#NativeClientLaunchers-CustomLaunchSettings

1 Like

Does this work on a mac?

I’ve tried running the following in terminal, but it just launches the published version.
open ~/Desktop/MainSCADA.app/ --args javaws.sr.project.version=Staging

I also tried adding <string>javaws.sr.project.version=Staging</string> under JVMArguments in ~/Desktop/MainSCADA.app/Contents/info.plist but it fails to launch and shows Error: Could not find or load main class javaws.sr.project.version=Staging in clientlauncher.log.

What’s the proper way to do this?

I got this to work by adding the following to info.plist (note the “-D”):
<string>-Djavaws.sr.project.version=Staging</string>

1 Like