# Launcher not connecting - wrong gateway address **URL:** \ **Category:** Ignition\ **Created:** [April 18, 2018, 2:49am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750 "2018-04-18T02:49:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [April 18, 2018, 2:49am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/1 "2018-04-18T02:49:02Z")
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: ```auto ``` to ```auto ``` (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. ```auto 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.(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)? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 18, 2018, 2:59am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/2 "2018-04-18T02:59:08Z")
Try deleting the `.ignition/cache` folder from your user directory instead of clearing the general Java cache. ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [April 18, 2018, 3:27am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/3 "2018-04-18T03:27:32Z")
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. ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [April 18, 2018, 3:43am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/4 "2018-04-18T03:43:20Z")
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. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 18, 2018, 4:01pm UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/5 "2018-04-18T16:01:20Z")
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](https://docs.inductiveautomation.com/display/DOC79/Native+Client+Launchers#NativeClientLaunchers-CustomLaunchSettings) ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [April 18, 2018, 10:15pm UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/6 "2018-04-18T22:15:37Z")
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 `javaws.sr.project.version=Staging` 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? ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [April 19, 2018, 5:19am UTC](https://forum.inductiveautomation.com/t/launcher-not-connecting-wrong-gateway-address/17750/7 "2018-04-19T05:19:53Z")
I got this to work by adding the following to info.plist (note the “-D”): `-Djavaws.sr.project.version=Staging`