# Domain login to designer, problem returning after connection lost

**URL:** <https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 20, 2023, 11:33am UTC](https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699 "2023-04-20T11:33:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michal\_Goralczyk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michal_goralczyk/32/55564_2.png) [@Michal\_Goralczyk](https://forum.inductiveautomation.com/u/Michal_Goralczyk)\
**Post date:** [April 20, 2023, 11:33am UTC](https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699/1 "2023-04-20T11:33:36Z")

</div>

Hello,

We use domain login for our Ignition designers. Our problem is that sometimes the Internet connection is unstable and there is a temporary dropout. Unfortunately, after the connection is lost, a re-login is required which causes a lot of problems and loss of changes over the project. Is there any way to prolong the timeout or deactivate the need to log in again after a lost connection?

The following message is displayed:

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/c/cc75337132ad12525e41895f15fe539f5004c4a1.png)

Best regards,  
Michał

---

<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:** [April 20, 2023, 11:48am UTC](https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699/2 "2023-04-20T11:48:06Z")

</div>

> [@Michal\_Goralczyk](#):
>
> sometimes the Internet connection is unstable

Sorry, but I'd say that makes your environment unfit for domain-based functionality. IMNSHO.

Consider using a local domain controller where your designers are running.

---

<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:** [April 20, 2023, 3:26pm UTC](https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699/3 "2023-04-20T15:26:38Z")

</div>

What version of Ignition is this? There's been some recent changes to try to hold authentication state better in the Designer and Vision.

---

<div class="post-metadata">

**Author:** ![Michal\_Goralczyk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michal_goralczyk/32/55564_2.png) [@Michal\_Goralczyk](https://forum.inductiveautomation.com/u/Michal_Goralczyk)\
**Post date:** [April 20, 2023, 8:58pm UTC](https://forum.inductiveautomation.com/t/domain-login-to-designer-problem-returning-after-connection-lost/72699/4 "2023-04-20T20:58:06Z")

</div>

My version below:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/f/3f523d4ea8450b11d28177f9651455b51fb000eb.png)
