Use ddns on your router with a domain so you can then get something like wireguard.example.com and then use that as the endpoint in your wireguard.
Set the wireguard DNS as your pihole.
To make life easier set your home network IP space to something that another WiFi would never use, ie 192.168.46.xx
That way it will never conflict if you are on a public WiFi and you can access anything on your home lab when you need.
I've been using this setup for years on laptop, phone etc
This. S0idle was pushed by Microsoft and Intel and amd followed. Now all new non apple CPUs are an embarrassment when it comes to sleep ability which essentially any normal person would expect without thinking about it so when they buy a brand new laptop and it ends up with a dead batter every morning people immediately just buy a Mac and get a much better experience.
Just completely shooting themselves in the foot. Same story with shitty laptop screens for nearly 5 years while Macs had retina displays.
Use the multi container extension for Firefox and have all your Google stuff in one container, banks in another, social media in another etc.
https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/
Thrown away your current ssh client and get
Is it not in the immich_pgdata or immich-app_pgdata folder?
The volumes themselves should be stored at /var/lib/docker/volumes
For future reference, doing operations like this without backing up first is insane.
Get borgmatic installed to take automatic backups and send them to a backup like another server or borgbase.
The main reason stadia failed is because they have cancelled so many projects before stadia that people were taking bets on when stadia would close before it even started.
No one wanted to buy into a service that was going to shut down and they created a self fulfilling prophecy.
Essentially all new Google projects wikl forever be doomed to this fate.
Highly recommend Authentik for SSO.
I run it on it's own sub domain and all my other apps on their own sub domains.
It has pretty much every login protocol you could want (oauth, saml, ldap) etc.
Currently using it for jellyfin, immich, linkwarden, freshrss, and seafile.
The general principle is called single sign on (sso).
The idea is that instead of each all keeping track of users itself, there is another app (sometimes called an identity provider) that does this. Then when you try to log into an app, it takes to the to login of your identity provider instead. When the IP says you are the correct user, it sends a token to the app saying to let you access your account.
The huge benefits are if you are already logged into the IP on a browser for example, the other apps will login automatically without having to put in your password again.
Also for me the biggest benefit is not having to manage passwords for a large number of apps so family that uses my server have 1 account which gives them access to jellyfin, seafile, immich, freshrss etc. If they change that password it changes it for everything. You can enforce minimum password requirements. You can also add 2FA to any app now immediately.
I use Authentik as my identity provider: https://goauthentik.io/https://goauthentik.io/
There's good guides to settings it up with traefik so that you get let encrypt certificates and can use traefik for proxy authentication on web based apps like sonarr. There are many different authentication methods an app can choose to use and Authentik essentially supports everything.
SSO should really be the standard for self hosted apps because this way they don't have to worry about ensuring they have the latest security for user management etc. The app just allows a dedicated identity provider to worry about user management security so the app devs can focus on just the app.
SQL is literally structured query language
Most people that have password managers are already using different passwords for each website. Usually randomly generated. What's the difference between that and a passkey?
Wait starfield works on SD? I thought it was too slow. Has there been a new patch?
This is a deep sleep issue. A google search will show that many modern processors can't actually deep sleep (S3) and therefore the only option is to hibernate or shut it off.
To find out if you can, sleep the computer, wake it up then run:
journalctl | grep S3There should be a line about what type of sleep is available and another line about what type of sleep your computer was just in.
If S3 is not listed as an available sleep mode you might get lucky and be able to turn it on in the bios. If you can't then you are out of luck.
Since I use fedora atomic, I used this to turn on deep sleep:
rpm-ostree kargs --append="mem_sleep_default=deep"On non atomic I forget exactly how but I think this is the way: https://unix.stackexchange.com/questions/720514/cannot-write-into-sys-power-mem-sleep-in-fedora-36