Does not reconnect after losing internet for a while
- Thread starter hhspiny
- Start date
Looks like the problem is not limited to booter process. had long internet outage today, both server's booter process and client became off-line after internet was resumed. the client machine needed to retype username and password. The server needed to log into admin account, but no need to re-type user name and password.
I will check when does the auto logout occur. If I remember well there were such cases in past versions but after introducing auto reconnect Remotly should eventually login to you account again when internet returns. You can check this after starting Remotly host. There will be a "Trying to log in..." message which will close after internet is back.
I have just done a 1 hour test:
- Disable network
- Start Remotly host
- Remotly stays in "Trying to log in..." state
- Enable network after 1h
- Remotly logs in
Pressin "CANCEL" on this "Trying to log in..." dialog deletes your encrypted login credentials and will switch to Remotly login screen.
- Disable network
- Start Remotly host
- Remotly stays in "Trying to log in..." state
- Enable network after 1h
- Remotly logs in
Pressin "CANCEL" on this "Trying to log in..." dialog deletes your encrypted login credentials and will switch to Remotly login screen.
Please try overwriting the res.bin file located in the installation folder with this one:
Please let me know if these is any improvement with the internet drop/recovery.
Please let me know if these is any improvement with the internet drop/recovery.
had some time in the weekend, and attempted to replicate the problem. but could not. both client and server were able to reconnect without needing re-login after cutting off internet for more than half-hour. tried to cut off at computer, or cut off at router, same.
even when starting remotly without internet, it was able to re-login itself after internet is resumed.
even closing and restarting without internet -- and pressing "cancel" and back to login screen -- it re-logs itself in once internet is resumed.
it was also a fact a few days earlier that both client/server did require re-login. not sure what the difference was.
the only thing I could think of was that my router had problem then, and I was troubleshooting, internet was on and off again and again, also switching from cable to cellular network and back again and again. maybe it confused remotly -- for example, the login process itself was interrupted.
anyway, maybe this turns out to be a false alert again.
even when starting remotly without internet, it was able to re-login itself after internet is resumed.
even closing and restarting without internet -- and pressing "cancel" and back to login screen -- it re-logs itself in once internet is resumed.
it was also a fact a few days earlier that both client/server did require re-login. not sure what the difference was.
the only thing I could think of was that my router had problem then, and I was troubleshooting, internet was on and off again and again, also switching from cable to cellular network and back again and again. maybe it confused remotly -- for example, the login process itself was interrupted.
anyway, maybe this turns out to be a false alert again.
"maybe it confused remotly -- for example, the login process itself was interrupted"
This could have happened. In fact if there was a non-standard error the auto login process would not start and instead enter unlogged state. In the new res.bin file I have uploaded it should be fixed.
This could have happened. In fact if there was a non-standard error the auto login process would not start and instead enter unlogged state. In the new res.bin file I have uploaded it should be fixed.