vocoder Posts - Answer Overflow

vocoder

Explore posts from servers

•Created by vocoder on 1/24/2025 in #help-desk-support

Subnet migration and after, Immich won't start

Moved a previously working immich IPs from 172.30.x.x to 172.20.x.x in my docker-compose.yaml, and UFW. Nothing in dmesg, tried with ufw disabled, no difference. Logs:

docker logs immich -f
Initializing Immich v1.125.1
DEBUG: cgroup v2 detected.
DEBUG: No CPU limits set.
Detected CPU Cores: 12
Starting api worker
Starting microservices worker
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:EventRepository] Initialized websocket server
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MetadataService] Bootstrapping metadata service
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MetadataService] Initializing metadata service
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MapRepository] Initializing metadata repository
microservices worker error: TypeError: Cannot read properties of undefined (reading 'replace')
microservices worker exited with code 1
Killing api process

docker logs immich -f
Initializing Immich v1.125.1
DEBUG: cgroup v2 detected.
DEBUG: No CPU limits set.
Detected CPU Cores: 12
Starting api worker
Starting microservices worker
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:EventRepository] Initialized websocket server
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MetadataService] Bootstrapping metadata service
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MetadataService] Initializing metadata service
[Nest] 7  - 01/24/2025, 1:41:23 PM     LOG [Microservices:MapRepository] Initializing metadata repository
microservices worker error: TypeError: Cannot read properties of undefined (reading 'replace')
microservices worker exited with code 1
Killing api process

LOG_LEVEL=debug. Tried restarting the server, , did:

docker system prune -f
docker image prune -a -f
docker volume prune -f

docker system prune -f
docker image prune -a -f
docker volume prune -f

I tried switching the db url to use the ip instead of the postgres hostname, same problem. Any ideas?

13 replies

HHomarr

•Created by vocoder on 12/18/2024 in #💬・get-help

Redirect URI wrong Protocol

Okay, getting further this time around. I almost could get in past OIDC but homarr's auth is building my redirect_uri as http not https. I tried with / without NEXTAUTH_URL variable set (maybe dep at this point, but didnt make any diff). Authelia is obviously rejecting it, and i can't add http rules as they are insecure. It looks like the new version works with 256 PKCE too. I run homarr as a reverse proxied service in that authelia. looks like it's created with the headers, which may explain it. https://github.com/homarr-labs/homarr/blob/3b7e6cc083220a0e3a0cf4f5243c073067ba5bc7/packages/auth/redirect.ts#L11C14-L11C31 .. Edit.. : https://github.com/homarr-labs/homarr/blob/3b7e6cc083220a0e3a0cf4f5243c073067ba5bc7/packages/common/src/url.ts#L7 This works 100% fine in the old version.

35 replies

Gaming

Programming