# Exit login gets stuck in step connecting

**URL:** <https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [December 10, 2024, 1:58pm UTC](https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627 "2024-12-10T13:58:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Janis\_Voss](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@Janis\_Voss](https://forum.inductiveautomation.com/u/Janis_Voss)\
**Post date:** [December 10, 2024, 1:58pm UTC](https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627/1 "2024-12-10T13:58:51Z")

</div>

Hey,  
I am running an Edge Gateway with version 8.1.35.  
A customer discovered that sometimes it is not possible to exit login via the "EXIT LOGIN" button. The session deadlocks in a loading screen on step "Connecting". The only way to get out of it is to leave the session, which means to turn off and on the device a focused window.

I can not reconstruct this in my test lab (pretty much same setup), but I was able to get the logs from this project. These logs are coming while the login and exit login process:

| timestmp | formatted\_message | logger\_name | level\_string |
| --- | --- | --- | --- |
| 1732722656001 | /system/pws/HMI\_POD/33bdf30e | org.eclipse.jetty.server.HttpChannel | WARN |
| 1732722633567 | WebSocket disconnected from session. | perspective.ClientSession | INFO |
| 1732722628963 | Shutting down delegate for '0:0:3'! | com.inductiveautomation.perspective.ComponentModel | INFO |
| 1732722628963 | Shutting down delegate for '0:0:1'! | com.inductiveautomation.perspective.ComponentModel | INFO |
| 1732722598785 | Starting up delegate for '0:0:3'! | com.inductiveautomation.perspective.ComponentModel | INFO |
| 1732722598785 | Starting up delegate for '0:0:1'! | com.inductiveautomation.perspective.ComponentModel | INFO |
| 1732722570227 | Created auto-backup of internal database "config.idb" in 989 ms | Platform.InternalDatabase | INFO |
| 1732722569238 | Creating auto-backup of internal database "config.idb"... | Platform.InternalDatabase | INFO |
| 1732722569076 | WebSocket disconnected from session. | perspective.ClientSession | INFO |

Did somebody else noticed this behavior or has an idea how to solve this? I could not find something in the forum so far.

---

<div class="post-metadata">

**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:** [December 10, 2024, 6:43pm UTC](https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627/2 "2024-12-10T18:43:18Z")

</div>

Those aren't complete logs - do you have full logs with stacktraces? Have you contact our [support department](https://support.inductiveautomation.com) officially?

---

<div class="post-metadata">

**Author:** ![Janis\_Voss](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@Janis\_Voss](https://forum.inductiveautomation.com/u/Janis_Voss)\
**Post date:** [December 12, 2024, 10:02am UTC](https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627/3 "2024-12-12T10:02:28Z")

</div>

I have the .idb file which you get when you press the download button in the Logs page, but I don't want to share the complete logs in public.  
No, I haven't yet. I wanted to ask here first, maybe somebody already has made the same experience 🙂

---

<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:** [December 12, 2024, 1:29pm UTC](https://forum.inductiveautomation.com/t/exit-login-gets-stuck-in-step-connecting/99627/4 "2024-12-12T13:29:24Z")

</div>

> [@Janis\_Voss](#):
>
> don't want to share the complete logs in public.

Then IA support is the only group that can help you.
