# Designer over SSL

**URL:** <https://forum.inductiveautomation.com/t/designer-over-ssl/15040>\
**Category:** Ignition\
**Created:** [August 10, 2017, 11:54pm UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040 "2017-08-10T23:54:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\
**Post date:** [August 10, 2017, 11:54pm UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040/1 "2017-08-10T23:54:33Z")

</div>

Cannot get designer to launch when gateway is setup to use non-standard SSL port

port 8042 - Ignition Edge - Designer won’t start - socket timeout error  
port 8043 - Ignition Full - Designer works fine  
port 8044 - Ignition Full - Designer won’t start - socket timeout error

All on Ubuntu 16.04 LTS  
All 7.9.3  
Can navigate to gateway via SSL on all.

Bug, configuration, or ID-10-T issue???

---

<div class="post-metadata">

**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:** [August 11, 2017, 12:19am UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040/2 "2017-08-11T00:19:16Z")

</div>

Once you configure SSL on 8044 do you download a new JNLP file before you try to launch?

---

<div class="post-metadata">

**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\
**Post date:** [August 11, 2017, 9:15am UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040/3 "2017-08-11T09:15:27Z")

</div>

Yes, I have downloaded many JNLPs from the gateway since changing the ssl port…

I have also tried the client launcher and get the following in its log:

ERROR [GatewayConfigPanel] [05:14:14,403]: PingWorker: Caught Exception:  
java.net.SocketException: Unexpected end of file from server  
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)  
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)  
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)  
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)  
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)  
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)  
at java.net.HttpURLConnection.getResponseCode(Unknown Source)  
at com.inductiveautomation.ignition.client.nativelaunch.util.GatewayCommUtil.getGatewayConnection(GatewayCommUtil.java:96)  
at com.inductiveautomation.ignition.client.nativelaunch.util.GatewayCommUtil.getGatewayRawResponse(GatewayCommUtil.java:126)  
at com.inductiveautomation.ignition.client.nativelaunch.util.GatewayCommUtil.pingGateway(GatewayCommUtil.java:152)  
at com.inductiveautomation.ignition.client.nativelaunch.ui.GatewayConfigPanel$PingWorker.doInBackground(GatewayConfigPanel.java:1624)  
at com.inductiveautomation.ignition.client.nativelaunch.ui.GatewayConfigPanel$PingWorker.doInBackground(GatewayConfigPanel.java:1608)  
at javax.swing.SwingWorker$1.call(Unknown Source)  
at java.util.concurrent.FutureTask.run(Unknown Source)  
at javax.swing.SwingWorker.run(Unknown Source)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.lang.Thread.run(Unknown Source)  
ERROR [GatewayConfigPanel] [05:14:14,408]: Gateway did not return a status of RUNNING: Unexpected end of file from server

---

<div class="post-metadata">

**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\
**Post date:** [August 11, 2017, 12:29pm UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040/4 "2017-08-11T12:29:28Z")

</div>

A bit more information…

All works fine when I try to run the designer from a computer on the same network as the Ignition server. The failures only occur when the connection is going through a router. I have three Ignition servers and am using 3 different SSL ports. The server using 8043 works fine, the other two (8042 and 8044) fail.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 11, 2017, 3:09pm UTC](https://forum.inductiveautomation.com/t/designer-over-ssl/15040/5 "2017-08-11T15:09:58Z")

</div>

Ignition uses both SSL and non-SSL ports when in SSL mode. You’ll have to change the non-ssl port for the two other servers and make sure they pinhole through your router, too.
