Windows Desktop client constantly logs out

[klein]

I just installed a new NC instance and installed a local Desktop client for my Windows PC.

However, that thing disconnects every few minutes, prompting me to log in again.

This happens especially if I use a browser to log into the admin account of the NC instance: immediately, the Desktop client logs out and prompts me to log in AND then shows the admin user account as proposed account.

That makes ZERO sense.

There is a reason why dedicated admin accounts exist.

I want to use the desktop client to sync files for my actual user.

When I log into the web interface as admin, it is because I want to perform administrative tasks.

This should have ZERO impact on the desktop client. But it does. Why?

I manage half a dozen Office 365 tenants and use multiple OneDrive instances to keep files from every tenant (using different tenant specific users) in sync with my Windows PC. Works flawlessly. It NEVER prompts me to re-login. It NEVER suggests that a OneDrive instance previously synced with a user account suddenly logs in with an admin account. o365 keeps all that very neatly separate.

Am I doing something wrong?

[jtr]

This is not normal. Something sounds wrong with your environment.

Wild guess: you’re using a reverse proxy such as NPM with its Asset Caching option toggled on.

[klein]

Thank you for your quick reply. I do not use a reverse proxy to my knowledge, but I still had the issue that I had an endless loop of

1. the Desktop client saying I am logged out and need to log in,
2. me logging in through the browser (which then said login was successful and I can close the window),
3. me then closing the browser window,
4. and the Desktop agent then logging me out again, rinse and repeat.

After restarting the PC a few times, this eventually stopped. But I believe I know what the root cause may have been: my internal DNS record had not fully propagated and was not used by my Windows machine. When I did a nslookup, it gave me my public IP address even though my Laptop and my NC Server are in my local network. And for some reason, I cant access the server with my public IP unless I am VPNed into a different network and pretend to come from the outside.

After the internal DNS record resolved properly, the Desktop Client did not have this strange behaviour.

However, even with not having access, it should not have this type of behaviour. If NC aims at eventually replacing Office 365 and Google Workspace, it needs to be rock solid and dead simple for total tech noobs that are just users and know nothing about technology. NC still seems to have some serious maturing to do, it seems, but I hope it gets there eventually.