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.
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
Did you happen to unplug the external drive when it was moved? Could wonder if the device ID got changed and the server can't find the old location for the library any longer.
Drive was just connected with USB to mini PC so it was also unplugged and I had to remount it to the PC. I looked in the .env file and the path still looked good. I had considered this was an issue too. I figured that restarting docker with the drive properly mounted would fix this though. Still getting, "connection was reset," though
So I checked the config for the external drive again and discovered when it was remounted it had added a, "1" to the end of the drive name. I went back into the .env and changed the library location to reflect this. Restarted docker and it is now connecting again. Obviously it is not ideal to be using a external HDD, but I wanted to test immich out for a while before investing into a bigger self hosting rig for all my services.
Ultimately problem solved though
I would recommend editing your fstab and use the USB drive's UUID to mount it to a consistent location. That way, even if you reboot or disconnect the drive and the reconnect it to, say, a different USB port, it will always mount to the same mountpoint.
See this page from the arch wiki for more info.
This is the answer. Find your UUID with "blkid" and mount it in fstab with the ID.
It's worth learning how. This problem is something everyone goes through (hopefully) once.
https://ostechnix.com/mount-a-drive-permanently-in-linux-using-fstab/