frankynov
Authentik update 2024.12.2 (bis) not working
I got an update for Authentik, but it seems to have broken something 😦
I have :
Error response from daemon: driver failed programming external connectivity on endpoint authentik (8ced59e30ce9e8b3f7a38ae6da006540dd6f3b352ae6e1bf77a27b678f35307f): Bind for 0.0.0.0:9443 failed: port is already allocated
64 replies
Remote acces with Tailscale
Hey !
I also use tailscale, it's super cool 🙂
In the settings of the app (in Tipi dashboard), have you entered the following parameters ?
- TS_ROUTES (for me it's the subnet of the server, for example 10.10.0.0/16)
- TS_EXTRA_ARGS (not mandatory but I put --advertise-exit-node)
Make sure you approve these changes in tailscale admin dashboard
7 replies
Authentik update 2024.12.2 (bis) not working
Yes yes, npm is generating a valid certificate on top of it, no issue here. I think it really didn't like the
wrong version number
response.
Anyway, thanks a lot for your time and digging, really appreciate 🙂64 replies
Authentik update 2024.12.2 (bis) not working
Ok cool. Yes I'll check what Nicolas can see about it - it's getting complex for me now as per which port is bound to what 😄
FYI, I did a rollback on the version before the upgrade (the one which was working fine).
And the curl is just warning me about the self certificate, not
wrong version number
:
And I can access the app with the self signed certficate from the browser, that's why nginx proxy manager was working in that case64 replies
Authentik update 2024.12.2 (bis) not working
Oh my. I got it working with your hints.
But it's weird.
Accessing the https://10.10.0.2:8770/ I was getting the SSL issue
( 10.10.0.2 sent an invalid response. ERR_SSL_PROTOCOL_ERROR )
A curl from the server itself gives this :
But, it is working on HTTP on same port.
So I have changed my nginx proxy manager to redirect from https to the http, and now it's working.
It's really weird. Maybe something changed in the way the internal certificate of Authentik is served. But I'm glad I have a workaround now64 replies
Authentik update 2024.12.2 (bis) not working
Yeah, I agree. Not ideal...
I just installed from scratch on my test environment (using the default traefik from tipi and its default ports) and it seems to work without issue.
Either I will use traefik specifically for Authentik, or I will try to understand why that update in particular seems to break on my main instance.
Meanwhile I will revert my backup to its original state.
64 replies
Authentik update 2024.12.2 (bis) not working
With that, the app starts but still has the 502 bad gateway error.
In the logs of authentik I see still some references to port 9000, such as :
authentik | {"auth_via": "secret_key", "domain_url": "0.0.0.0", "event": "/api/v3/core/brands/?page=1&page_size=100", "host": "0.0.0.0:9000", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 58, "remote": "127.0.0.1", "request_id": "1bd1ac42375242288967da1320948c79", "runtime": 38, "schema_name": "public", "scheme": "http", "status": 200, "timestamp": "2025-01-21T22:58:12.037206", "user": "ak-outpost-4348a29d08574ff4bb1978fe5baf2ecb", "user_agent": "goauthentik.io/outpost/2024.12.2"}
Probably because it might still be reading the port from the docker-compose.json and not the yml file ? (I don't know really the inner works of Docker, still learning it with Tipi 🙂 )64 replies
Authentik update 2024.12.2 (bis) not working
Ok, I've done a docker-compose.yml in the user config with this :
Unfortunately now it doesn't start at all :
See output here :
https://pastebin.com/YwwkF0vD
64 replies
Issue with user-config volumes and Jellyfin
Merci beaucoup !
I will have to dig a bit still about these permissions. If I understand correctly, it means that it runs as root ?
I can't find any reference of PUID or PGID on the Immich compose file so now I don't understand why it's working there since the beginning 🤪
17 replies