# Perspective Hangs / Websocket issue **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [March 10, 2023, 8:51am UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891 "2023-03-10T08:51:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\ **Post date:** [March 10, 2023, 8:51am UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891/1 "2023-03-10T08:51:41Z")
I have a situation where my perspective session hangs, or maybe better put; stops updating the variables/bindings on the screen. Now this is a SFF PC running only an perspective session and it is connected to the ignition server with an ethernet cable, through the company's server rack which has firewall units and smart switches. A refresh 'fixes' the issue temporarily. but it is reoccurring. I also don't see a pattern, it seems to happen and random intervals. Here is the event captured in the logs: ![websocket log](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/c/ac6365dcb729f5c6ff9a93462caf904589c98f8b.png) I would really appreciate any help regarding this issue as I do not know how to fault find this one. I would like to prevent this from happening, and if possible do some scripting to respond to this event to make the system more robust. Something like restarting the session, or refreshing the page ---
**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:** [March 10, 2023, 4:20pm UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891/2 "2023-03-10T16:20:27Z")
"An existing connection was forcibly closed by the remote host" Something in the network between the gateway and wherever this session is running (that _is not the gateway_) explicitly told the gateway to close the session. ---
**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\ **Post date:** [March 10, 2023, 5:36pm UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891/3 "2023-03-10T17:36:19Z")
Thank you for translating that. Would that be something I could spot using wireshark? ---
**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:** [March 10, 2023, 5:39pm UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891/4 "2023-03-10T17:39:07Z")
Wireshark on the gateway probably wouldn't tell you much more; you'll see the explicit end message on the socket - but it'll just come from `` - you need to dig into what there is between the gateway and the client machine. It's not the best test in the world, but if you're able to open long-lived sessions on different hosts (e.g. the gateway machine itself, on other hosts) you might be able to pinpoint what's going on. It might also be something you could take to your IT group - you can give them an exact timestamp and ask if any of the firewalls/switches/etc report doing anything at that time. ---
**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\ **Post date:** [March 10, 2023, 6:43pm UTC](https://forum.inductiveautomation.com/t/perspective-hangs-websocket-issue/70891/5 "2023-03-10T18:43:57Z")
Thank you! I'll do just that