Selfhosted
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!
view the rest of the comments
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?
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.
Yep, it was restarting my laptop. Oops. I have updated the post. Interestingly enough, the popup doesn't show when I turn on my laptop outside my local network (e.g. when I'm at school) and only shows up when I'm back home (in my local network), and since I always power off and turn on my laptop at school, I never noticed that restarting was the problem.
Then my first assumption is that the session token is not being correctly stored in kwallet. It can't restore the session after kwallet is closed.
You can open kwallet manager, and delete the wallet. This will prompt your system to re-create it next time you go to use something that needs it (wifi, nextcloud).
This will allow you to essentially reset the default wallet.
The typical settings for it are "blowfish" encryption with either a blank password (which encrypts nothing, but allows the wallet to always open reliably) or using the same password as your user (which allows the wallet to decrypt automatically upon login).
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.