# Gateway connection issue after client sleep/hibernate **URL:** \ **Category:** Ignition\ **Created:** [May 15, 2013, 9:00pm UTC](https://forum.inductiveautomation.com/t/gateway-connection-issue-after-client-sleep-hibernate/6490 "2013-05-15T21:00:48Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![bpirtle](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@bpirtle](https://forum.inductiveautomation.com/u/bpirtle)\ **Post date:** [May 15, 2013, 9:00pm UTC](https://forum.inductiveautomation.com/t/gateway-connection-issue-after-client-sleep-hibernate/6490/1 "2013-05-15T21:00:48Z")
Every time I open my computer after it has gone into hibernate, any running clients or the designer will all give the following error every 30 seconds, and never connect to the gateway again (Gateway is up) unless I close them all down and launch them again: Message: Connection to Gateway lost, due to exception. Time: Wed May 15 1:58:53PM Severity: WARN Logger: com.inductiveautomation.ignition.client.gateway\_interface.GatewayConnectionManager Stack Trace: com.inductiveautomation.ignition.client.gateway\_interface.GatewayException: Reply from SOCKS server has bad version     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.newGatewayException(GatewayInterface.java:312)     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.getResponse(GatewayInterface.java:450)     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.getResponse(GatewayInterface.java:318)     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.ping(GatewayInterface.java:869)     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.publicPing(GatewayInterface.java:862)     at com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection.testComm(AbstractGatewayConnection.java:325)     at com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection.fishForAliveServer(AbstractGatewayConnection.java:379)     at com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection$GatewayReconnectTask.run(AbstractGatewayConnection.java:592)     at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)     at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)     at java.util.concurrent.FutureTask.runAndReset(Unknown Source)     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)     at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Reply from SOCKS server has bad version     at java.net.SocksSocketImpl.connectV4(Unknown Source)     at java.net.SocksSocketImpl.connect(Unknown Source)     at java.net.Socket.connect(Unknown Source)     at sun.net.NetworkClient.doConnect(Unknown Source)     at sun.net.www.http.HttpClient.openServer(Unknown Source)     at sun.net.www.http.HttpClient.openServer(Unknown Source)     at sun.net.www.http.HttpClient.\(Unknown Source)     at sun.net.www.http.HttpClient.New(Unknown Source)     at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)     at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)     at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)     at com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.getResponse(GatewayInterface.java:347)     … 15 more Stack Trace: com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.newGatewayException(GatewayInterface.java:312) com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.getResponse(GatewayInterface.java:450) com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.getResponse(GatewayInterface.java:318) com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.ping(GatewayInterface.java:869) com.inductiveautomation.ignition.client.gateway\_interface.GatewayInterface.publicPing(GatewayInterface.java:862) com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection.testComm(AbstractGatewayConnection.java:325) com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection.fishForAliveServer(AbstractGatewayConnection.java:379) com.inductiveautomation.ignition.client.gateway\_interface.AbstractGatewayConnection$GatewayReconnectTask.run(AbstractGatewayConnection.java:592) java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) java.util.concurrent.FutureTask.runAndReset(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) I am worried that if I deploy a client and it ever hibernates, that my users will have to keep reloading the project and it’s going to become a nuisance. Is there a way to have it automatically reconnect? Another piece of information is that the client machine does have an active internet connection, so there is no reason that it shouldn’t be able to connect again. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [May 23, 2013, 5:30pm UTC](https://forum.inductiveautomation.com/t/gateway-connection-issue-after-client-sleep-hibernate/6490/2 "2013-05-23T17:30:55Z")
This error is not something we have control over. It looks like it is coming from your proxy server. (SOCKS is a proxy system). This means that it has something to do with your networking setup. If IT can’t help you, your best bet would be to configure your OSes not to hibernate/sleep.