# OpenID with Authelia: redirect url /auth/openid/authelia 404 not found

**URL:** <https://community.vikunja.io/t/openid-with-authelia-redirect-url-auth-openid-authelia-404-not-found/4271>\
**Category:** Support\
**Created:** [26 January 2026 14:41 UTC](https://community.vikunja.io/t/openid-with-authelia-redirect-url-auth-openid-authelia-404-not-found/4271 "2026-01-26T14:41:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nils](https://community.vikunja.io/letter_avatar_proxy/v4/letter/n/d6d6ee/32.png) [@nils](https://community.vikunja.io/u/nils)\
**Post date:** [26 January 2026 14:41 UTC](https://community.vikunja.io/t/openid-with-authelia-redirect-url-auth-openid-authelia-404-not-found/4271/1 "2026-01-26T14:41:17Z")

</div>

Hi,

I can’t get my new Vikunja installation to work with authelia as OpenID provider.

The “Login with Authelia” button appears, redirects me to Authelia, I can login, then I get redirected to the redirect URL, which then returns HTTP 404 with the content `{"message":"Not Found"}`

I noticed also:  
After opening `https://vikunja.mydomain.com`, i get redirected to `https://vikunja.mydomain.com/login`. When directly accessing `https://vikunja.mydomain.com/login`, I get the same 404 message. In Vikunja, there are also 404 requests to `https://vikunja.mydomain.com/workbox-v7.3.0/workbox-sw.js`

- Vikunja v1.0.0-rc4 in docker
- Using cosmos cloud as proxy to access via `https://vikunja.mydomain.com`
- No errors logged in authelia
- Vikunja works with username and password

Vikunja logs:

```auto
level=ERROR component=http method=GET uri="/auth/openid/authelia?code=authelia_ac_v8KAbce0Aypxxxx&iss=https%3A%2F%2Fauthelia.mydomain.com&scope=openid+profile+email&state=47ubp2unb0s" status=404 latency=175.977µs err="Not Found"

```

Vikunja config:

```auto
auth:
  openid:
    enabled: true
    providers:
      authelia:
        name: 'Authelia'
        authurl: 'https://authelia.mydomain.com'
        clientid: 'vikunja'
        clientsecret: 'secret'
        scope: 'openid profile email'

```

Authelia config:

```auto
      - client_id: 'vikunja'
        client_name: 'Vikunja'
        client_secret: 'hashed client secret'
        public: false
        consent_mode: 'implicit'
        authorization_policy: 'two_factor'
        require_pkce: false
        pkce_challenge_method: ''
        redirect_uris:
          - 'https://vikunja.mydomain.com/auth/openid/authelia'
        scopes:
          - 'openid'
          - 'profile'
          - 'email'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'

```

Container env:

```auto
"VIKUNJA_SERVICE_PUBLICURL=https://vikunja.mydomain.com",
"VIKUNJA_SERVICE_ROOTPATH=/app/vikunja/",
"VIKUNJA_DATABASE_PATH=/db/vikunja.db",
"VIKUNJA_SERVICE_JWTSECRET=secret",

```

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [26 January 2026 14:53 UTC](https://community.vikunja.io/t/openid-with-authelia-redirect-url-auth-openid-authelia-404-not-found/4271/2 "2026-01-26T14:53:25Z")

</div>

This sounds like you’re hitting this error: [https://github.com/go-vikunja/vikunja/issues/2149](https://github.com/go-vikunja/vikunja/issues/2149)

Does it work with an unstable build?

---

<div class="post-metadata">

**Author:** ![nils](https://community.vikunja.io/letter_avatar_proxy/v4/letter/n/d6d6ee/32.png) [@nils](https://community.vikunja.io/u/nils)\
**Post date:** [26 January 2026 15:41 UTC](https://community.vikunja.io/t/openid-with-authelia-redirect-url-auth-openid-authelia-404-not-found/4271/3 "2026-01-26T15:41:16Z")

</div>

Yes, it works with the unstable build, thank you very much!

I was looking for a solution since 2 days, started with checking the github issues, seems like I was there only a few hours before the bug was posted 😐