I set up Immich on a spare mini PC running Linux Mint with a spare external HDD to store the library. Used Docker compose as recommended on the website. Everything was working great last night. Then this morning I decided to move the mini PC to a more permanent location. I powered down and moved it. When everything restarted though I discovered that I was unable to c9nnect to the immich server. I went onto the mini PC and the local host and all it says is, “connection was reset.” I have tried restarting docker from terminal several times and it says the immich services are running. I still cannot connect to the server though. What can I do to fix this?

  • patrick@lemmy.bestiver.se
    link
    fedilink
    English
    arrow-up
    2
    ·
    13 hours ago

    I can’t help, just chiming in to say that I’ve also had that experience with Immich. It’s the one service I’ve used that has somehow managed to break itself multiple times like this.

    No idea how it happens, I don’t do anything weird with the setup and it just breaks. I’d heard that feedback from other people too but didn’t believe it until it happened to me. It’s been a few months so maybe I’ll try again, I’m just not too happy importing hundreds of gigs of photos multiple times.

    So yea just… you’re not alone, good luck.

  • ifmu@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    12 hours ago

    The only issue I’ve had was when Immich doesn’t have enough memory. Immich is a memory hog and will slowly creep up its memory usage over time. Eventually it’ll crash and restart itself. Docker still shows it running, but the server its elf cannot be connected to.

    It sounds like it might be related to this.

  • Monkey With A Shell@lemmy.socdojo.com
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 days ago

    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.

    • qwestjest78@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      2 days ago

      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

      • qwestjest78@lemmy.caOP
        link
        fedilink
        English
        arrow-up
        26
        ·
        2 days ago

        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

      • gray@pawb.social
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        22 hours ago

        don’t do this, use DHCP reservations instead so you actually have a list of all your servers and most routers register hostnames in DNS for you which is even better.

        • SatanClaus@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          16 hours ago

          Confused what you mean.? I have a range of IPs for my servers and such IE 192.168.2.2-12. And then the DHCP pool 192.168.2.13-xxx. I set the servers IP static on its OS. And then set a static in my routers settings for the same IP I set in the OS. What is it that I would be doing incorrect in this setup?

          • gray@pawb.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            12 hours ago

            Instead of doing a manual action in two different places and having to keep them in sync, just do it once on the DHCP server. Setting a static IP on the server is superfluous.

            • Monkey With A Shell@lemmy.socdojo.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              1 hour ago

              While handy on a personal net, on a larger corporate net this isn’t practical and even adds a security risk. By having servers request leases you run the chance that someone gets into a segment, funds the ARP association for an IP/MAC combo and can take over a server’s spot simply by spoofing their own MAC to match at the time of lease renewal.

              In the post above about setting a static address in two spots that in itself isn’t required either. So long as there are no duplicates you would just set the static address on the end device, then the network will sort it out with ARP ‘who has’ requests in local segments, or routing in the case of distinct subnets.

              Edit: the duplicate I suppose could be referring to putting names into a DNS registry, in which case yes you would need that double entry, or just reference things by IP if the environment is small enough for it to be practical.

  • ocean@lemmy.selfhostcat.com
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    2 days ago

    If your photos are externally linked I would just delete and rerun the dockers.

    I just had a weird immich issue where all my photos disappeared. Deleting Redis solved it for me.

  • Hiro8811@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    Hey, if you changed the Internet cable then the ip address most likely changed as well. Find you PC new ipv4 address and you’ll be able to connect

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    5
    ·
    2 days ago

    I shut down my Immich server two months ago and moved it halfway across the state and did not have this issue.

    All my files are on an internal disk.