Immich•3y ago

Broken after upgrading to the latest -- /api/oauth/config returning 502

Hi, I just upgraded from 1.43.0 to 1.43.1 and I get an error that says "Unable to connect". Looking at the network logs the call in the title of this post returns a 502. I never had any oauth configured, so I'm curious what's going on and how to fix this. Thanks!

9 Replies

Alex Tran•3y ago

Hello this is on us this time. You might need to include the additional environment variable DB_HOSTNAME=immich_postgres hold on from 1.43 to 1.43.1?

HummingbirdOP•3y ago

i already have that and redis at the root .env file 😦 i believe so, was running fine on saturday

Alex Tran•3y ago

Have you try restarting the stack?

HummingbirdOP•3y ago

just pulled whatever since then and it's broken yup, twice, and individual containers

Alex Tran•3y ago

can you post the log on the server and microservice?

HummingbirdOP•3y ago

server and microservice only show startup info, is there a way to get more logs? last couple lines of each:

[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/server-info/stats, GET} route +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RoutesResolver] JobController {/jobs}: +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/jobs, GET} route +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/jobs/:jobId, PUT} route +0ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [NestApplication] Nest application successfully started +38ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [ImmichServer] Running Immich Server in PRODUCTION environment - version 1.43.1 - Listening on port: 3001
[Nest] 1  - 01/30/2023, 8:33:45 PM    WARN [ImmichServer] Machine learning is enabled

[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/server-info/stats, GET} route +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RoutesResolver] JobController {/jobs}: +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/jobs, GET} route +1ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [RouterExplorer] Mapped {/jobs/:jobId, PUT} route +0ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [NestApplication] Nest application successfully started +38ms
[Nest] 1  - 01/30/2023, 8:33:45 PM     LOG [ImmichServer] Running Immich Server in PRODUCTION environment - version 1.43.1 - Listening on port: 3001
[Nest] 1  - 01/30/2023, 8:33:45 PM    WARN [ImmichServer] Machine learning is enabled

```[Nest] 1  - 01/30/2023, 8:33:58 PM     LOG [InstanceLoader] MicroservicesModule dependencies initialized +0ms
[Nest] 1  - 01/30/2023, 8:33:59 PM     LOG [MetadataExtractionProcessor] Reverse Geocoding Initialised
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG [NestApplication] Nest application successfully started +9846ms
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG [ImmichMicroservice] Running Immich Microservices in PRODUCTION environment - version 1.43.1 - Listening on port: 3002
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG checksum generation done!

```[Nest] 1  - 01/30/2023, 8:33:58 PM     LOG [InstanceLoader] MicroservicesModule dependencies initialized +0ms
[Nest] 1  - 01/30/2023, 8:33:59 PM     LOG [MetadataExtractionProcessor] Reverse Geocoding Initialised
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG [NestApplication] Nest application successfully started +9846ms
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG [ImmichMicroservice] Running Immich Microservices in PRODUCTION environment - version 1.43.1 - Listening on port: 3002
[Nest] 1  - 01/30/2023, 8:34:08 PM     LOG checksum generation done!

jrasm91•3y ago

502 implies a proxy connection error. You could try removing the log driver: none from compose for the immich proxy container and then looking at the logs for that container.

HummingbirdOP•3y ago

hm, looks like doing a full docker-compose down then up resolved this. restarts didn't fix it thanks anyway, guess there's nothing to report

Alex Tran•3y ago

Ah restarting mean down and up 😛 sorry I didn't know you are not using the command line from the start

Gaming

Programming

Broken after upgrading to the latest -- /api/oauth/config returning 502

Did you find this page helpful?