I don’t know exactly what happened. But I’m guessing he was doxxed and bullied by activists based on this post https://tenforward.social/@zyd/113086796304683411

Good point maybe where I should start is why I never moved to immich in the first place. I have a digital camera as well as a phone, somr photos I process on my workstation. It has the nextcloud app syncing images so I can update files easily using photo editing programs on my workstation. This setup works well for me. I don’t really want to move away from nextcloud if I don’t need to.

Moving to immich looks like I either change my existing process or I use and external album since there is no nextcloud adapter.

The external album setup looked like more work and since I already have nextcloud making it work slightly better for storing photos is a more appealing solution for the time being

I already had nextcloud, never used immach. But I installed memories a few minutes ago, and it seems fast enough. The android app actually works. Truth be told I might still try immach at some point but installing memories was easy to get started with since i already have nextcloud. seems to build on the main in photos app so I’m not too worried about it being a 3rd party addon.

Maybe you need a dockerhub account? Perhaps try the github artifact registry https://github.com/paperless-ngx/paperless-ngx/pkgs/container/paperless-ngx/200691922?tag=latest

This is not helpful for you now, but you should look into etckeeper, it creates a git repo of your /etc directory, it hooks into APT and will create new commits when changes occur. It’s not often that i use it, but it’s reassuring to know that i have a history of the contents of /etc

With all networking problems it’s a process of elimination, so you’ll want to first figure out what problem you are facing.

• can you ping your local router? (maybe it’s 192.168.1.1)
• can you ping the internet? (maybe try 8.8.8.8)

if those both work then you should move on to DNS, if they don’t then you’ll have to jump to trying to figure out what is wrong with your network devices

dns

To debug DNS issues, you can compare the output of running

getent hosts google.com

to something like

nslookup google.com 8.8.8.8

one will use an explicit DNS server (8.8.8.8) and the other is using the resolv conf configuration. if they both work and have somewhat similar output, then it’s not DNS if the getent command fails, then you have a DNS issue.

If you have a problem with the contents of resolv conf, or it’s not working, you’ll first need to figure out which DNS configuration process you are using, it’s probably either network manager, or systemd-resolved. I’m no expert in either, but once you know that you can start looking into how that system is configured.

networking

If it’s not DNS then you need to figure out how your networking device is configured. Check that the networking systemd processes started is a good place to start, but you’ll have to figure out what you are using for network configuration.

for server style /etc/network/interfaces configuration

sudo systemctl status networking.service

for network manager

sudo systemctl status NetworkManager.service