Comment

Comment on My Overconfidence Killed Me and My Immich Installation

Hey so I’m intermediate at best. This to me sounds like permissions problems. No user name specified in startup packet?

This sounds to me like you edited something that starts up postgres such that when it is started up it is not receiving a username.

Shooting in the dark here, but perhaps take a look through logs for postgres. Check postgres and redis configs in these docker containers, they might be set up expecting something you changed, so they’re not receiving anything.

Line you’re sending an unmodified username to a new host name from what I see, right? Is the other side of this connection aware of these modifications?

Fuck that sounds vague. I might not even be right. I’d be digging through error logs for clues.

source

Sort:hotnew top

sabreW4K3@lazysoci.al ⁨5⁩ ⁨months⁩ ago
You truly are providing value and I appreciate you for it. Thank you.

source
- foggy@lemmy.world ⁨5⁩ ⁨months⁩ ago
  😁
  
  source
foggy@lemmy.world ⁨5⁩ ⁨months⁩ ago
I also asked a local instance of the Mixtral llm:

Database URL Format: The DB_URL in the .env file is defined as 192.168.0.89:8765, which is unusual for a PostgreSQL connection. PostgreSQL typically uses a connection string format, not a URL starting with http://. The correct format for a PostgreSQL connection string usually looks like: postgresql://username:password@hostname:port/data…. Changing the DB_URL to match this format might resolve the issue of the application not recognizing the username.

Environment Variable Consistency: Ensure that all references to the database, Redis, and other services within both the .env file and the Docker Compose file are consistent with the new names and ports. This includes checking that the DB_HOSTNAME and REDIS_HOSTNAME in the .env file match the container_name of the services in the Docker Compose file.

PostgreSQL Connection String in Docker Compose: The environment variables for the Immich services in the Docker Compose file are focused on POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB. If Immich constructs its own connection string internally using these components, ensure they’re correctly configured. However, it might be worth directly specifying a full connection string (if supported by Immich) that includes the username, password, host, and database in a single variable, to reduce the chance of misconfiguration.

Network Configuration: Verify that Docker’s network configuration hasn’t been altered in a way that would prevent containers from communicating properly. Docker Compose services communicate over a default network, but if you’ve made network modifications, ensure that these don’t inadvertently block connections between services.

source
- sabreW4K3@lazysoci.al ⁨5⁩ ⁨months⁩ ago
  Thank you so much!
  
  source
  - foggy@lemmy.world ⁨5⁩ ⁨months⁩ ago
    Did ya get it? :)
    
    source