When trying to connect to my Ignition Gateway from Ignition Designer Launcher i get the following error: Error Launching Application: ConnectException: Connection refused: connect
I am using CentOS 7 linux server with firewall disabled. If I restore the gateway backup on a local ignition gateway, I'm able to launch using Ignition Designer Launcher and can access the projects. However it does not work when launching from the linux server.
I looked up the launch error text file and noticed the following:
Local third party Python modules are different than the ones on the server. Will download updated modules now.
Downloading "https://IgnitionServer:8043/system/scriptModules"...
Download attempt #0 for third party Python modules failed.
java.net.ConnectException: Connection refused: connect
at java.base/java.net.PlainSocketImpl.waitForConnect(Native Method)
at java.base/java.net.PlainSocketImpl.socketConnect(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
at java.base/java.net.Socket.connect(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at java.base/sun.net.NetworkClient.doConnect(Unknown Source)
at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsClient.(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep.download(DownloadPyLibStep.java:248)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep.downloadPyLib(DownloadPyLibStep.java:204)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep$DownloadPyLibZip.maybeDownload(DownloadPyLibStep.java:146)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep$DownloadPyLibZip.run(DownloadPyLibStep.java:85)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep$DownloadPyLibZip.run(DownloadPyLibStep.java:72)
at com.inductiveautomation.ignition.client.launch.steps.AbstractLaunchStep.runLockedAction(AbstractLaunchStep.java:95)
at com.inductiveautomation.ignition.client.launch.steps.BaseStep.runLockedAction(BaseStep.java:21)
at com.inductiveautomation.ignition.client.launch.steps.DownloadPyLibStep.run(DownloadPyLibStep.java:62)
at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:33)
at java.base/java.lang.Thread.run(Unknown Source)
Did you get to the bottom of this, I’m getting the same error trying to connect to a remote gateway and I’m having trouble running down what’s causing the connection refusal: VM config issue? gateway config issue?
This may or may not be the issue, but in some cases it’s possible to have a designer stuck in this situation if your gateway does not have SSL enabled but Force Secure Redirect is enabled. If your gateway does not have SSL enabled (using an http url instead of https) navigate to the Config > Web Server and see if Force Secure Redirect is enabled. It will look like:
If you are in this state, you can either enable SSL temporarily so you can disable Force Secure Redirect before disabling SSL again or navigate to your gateways data/gateway.xml file and set the entry for gateway.forceSecureRedirect to false (this requires a gateway restart). After that, your designer should be able to connect again. This is a bug currently on our end currently waiting prioritization.
I was struggling with an error with Designer after disabling SSL. I was getting a “Connection Refused” exception. I thought I’d try my luck and googled [ignition designer “connection refused”] and this was the first hit. Setting
I have installed 8.1.39 and neither SSL certificate is enabled nor 8043 port is set. But when I open my designer. It takes around 40sec to verify signature as shown in picture. After verifying signature my designer is getting started to open. So, total time would be more than 1 minute. I haven't seen this before on my previous version.
Yes, You are right Phil, We have a tight firewall. Seems like Inductive automation making their product more secure. I think, It's trying to verify the Digi certificates.
I had the same issue but running the gateway within Docker. Somehow editing the gateway.xml via the Docker Desktop was not working, it was always disabled after the restart. Finally deleting the gateway.xml solved the issue (i didn't mind to lose the configuration).
