That's definitely not how it should work. Leaving your LAN should not invalidate a session.
Is this in your browser, or are you talking about the desktop client?
this post was submitted on 05 Dec 2025
12 points (100.0% liked)
Selfhosted
53360 readers
196 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
It's the desktop client, should have mentioned that. My browser remembers my device.
In that case, something is invalidating the login. Are you sure that it is happening due to leaving your LAN, and not just coinciding with that?
Does restarting the laptop log you out, or temporarily disconnecting from the internet? Could you test by switching to a wifi hotspot on your phone, and switching back, for example?
The client stores your session token in the OS credentials manager (kwallet for linux kde, for example) and the issue can lie there, as well.
I will try restarting and temporarily disconnect and see if the issue pops up. Probably should have done that before...
It might turn out to be something different - but just in case it does log you out after a system restart (but maybe not after network disconnect) it would probably have something to do with kwallet (the key ring which has your credentials) not unlocking correctly.
If that’s the case this or this might be further pointers to look into.
Are you using a Mac? Could be Apples private wifi thing that gives you a new MAC address each time you connect. You can set it to use the same MAC every time for your home wifi and see if that fixes it.
Nextcloud shouldn't be seeing your MAC address. However, my guess is that Nextcloud has been configured to invalidate the session if the client IP changes, and randomizing the MAC address is one way that can happen.
Fortunately I'm not in Apple's walled garden. I'm running Fedora KDE :D