Immich•8mo ago

In 1.133.0 I can no longer authenticate with Authelia

Both sides have the

token_endpoint_auth_method: 'client_secret_post'

token_endpoint_auth_method: 'client_secret_post'

token_endpoint_auth_method: 'client_secret_post'

token_endpoint_auth_method: 'client_secret_post' set. But when Authelia returns to immich it says

failed to finish auth

failed to finish auth

failed to finish auth

failed to finish auth with the following error:

[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] OAuth login failed: server responded with an error in the response body
[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] ResponseBodyError: server responded with an error in the response body
    at checkOAuthBodyError (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:865:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async processGenericAccessTokenResponse (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1141:5)
    at async processAuthorizationCodeOAuth2Response (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1373:20)
    at async authorizationCodeGrant (file:///usr/src/app/node_modules/openid-client/build/index.js:942:18)
    at async OAuthRepository.getProfile (/usr/src/app/dist/repositories/oauth.repository.js:53:28)
    at async AuthService.callback (/usr/src/app/dist/services/auth.service.js:178:25)
    at async OAuthController.finishOAuth (/usr/src/app/dist/controllers/oauth.controller.js:46:22) {
  cause: {
    error: 'invalid_client',
    error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'
  },
  code: 'OAUTH_RESPONSE_BODY_ERROR',
  error: 'invalid_client',
  status: 401,
  error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'

[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] OAuth login failed: server responded with an error in the response body
[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] ResponseBodyError: server responded with an error in the response body
    at checkOAuthBodyError (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:865:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async processGenericAccessTokenResponse (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1141:5)
    at async processAuthorizationCodeOAuth2Response (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1373:20)
    at async authorizationCodeGrant (file:///usr/src/app/node_modules/openid-client/build/index.js:942:18)
    at async OAuthRepository.getProfile (/usr/src/app/dist/repositories/oauth.repository.js:53:28)
    at async AuthService.callback (/usr/src/app/dist/services/auth.service.js:178:25)
    at async OAuthController.finishOAuth (/usr/src/app/dist/controllers/oauth.controller.js:46:22) {
  cause: {
    error: 'invalid_client',
    error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'
  },
  code: 'OAUTH_RESPONSE_BODY_ERROR',
  error: 'invalid_client',
  status: 401,
  error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'

[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] OAuth login failed: server responded with an error in the response body
[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] ResponseBodyError: server responded with an error in the response body
    at checkOAuthBodyError (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:865:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async processGenericAccessTokenResponse (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1141:5)
    at async processAuthorizationCodeOAuth2Response (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1373:20)
    at async authorizationCodeGrant (file:///usr/src/app/node_modules/openid-client/build/index.js:942:18)
    at async OAuthRepository.getProfile (/usr/src/app/dist/repositories/oauth.repository.js:53:28)
    at async AuthService.callback (/usr/src/app/dist/services/auth.service.js:178:25)
    at async OAuthController.finishOAuth (/usr/src/app/dist/controllers/oauth.controller.js:46:22) {
  cause: {
    error: 'invalid_client',
    error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'
  },
  code: 'OAUTH_RESPONSE_BODY_ERROR',
  error: 'invalid_client',
  status: 401,
  error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'

[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] OAuth login failed: server responded with an error in the response body
[Nest] 17  - 05/23/2025, 7:48:40 AM   ERROR [Api:OAuthRepository~dweqkoeg] ResponseBodyError: server responded with an error in the response body
    at checkOAuthBodyError (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:865:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async processGenericAccessTokenResponse (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1141:5)
    at async processAuthorizationCodeOAuth2Response (file:///usr/src/app/node_modules/oauth4webapi/build/index.js:1373:20)
    at async authorizationCodeGrant (file:///usr/src/app/node_modules/openid-client/build/index.js:942:18)
    at async OAuthRepository.getProfile (/usr/src/app/dist/repositories/oauth.repository.js:53:28)
    at async AuthService.callback (/usr/src/app/dist/services/auth.service.js:178:25)
    at async OAuthController.finishOAuth (/usr/src/app/dist/controllers/oauth.controller.js:46:22) {
  cause: {
    error: 'invalid_client',
    error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'
  },
  code: 'OAUTH_RESPONSE_BODY_ERROR',
  error: 'invalid_client',
  status: 401,
  error_description: 'Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).'

I have verified the client_id and client_secret is correct as well. I am at a loss.

Immich•5/23/25, 8:01 AM

:wave: Hey @MagicTrevor,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.

References

Container Logs:
```
docker compose logs
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
docker ps -a
```
docs
Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA

Immich•5/23/25, 8:01 AM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
:ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

Your docker-compose.yml and .env files.
Logs from all the containers and their status (see above).
All the troubleshooting steps you've tried so far.
Any recent changes you've made to Immich or your system.
Details about your system (both software/OS and hardware).
Details about your storage (filesystems, type of disks, output of commands like
```
fdisk -l
```
```
fdisk -l
```
and
```
df -h
```
```
df -h
```
).
The version of the Immich server, mobile app, and other relevant pieces.
Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the