frankynov
Apps containers not starting after 4.0.0 upgrade
Aaaah ok !
So, I did briefly open the firewall to 8080, connected to tipi GUI from the WAN and started tailscale.
From there I disabled again the firewall and started all the other containers and apps in the GUI.
All seems to be good, and I validated with a reboot of the machine, all apps are starting again
26 replies
Apps containers not starting after 4.0.0 upgrade
indeed, internally it is started, I can see the login page with curl on localhost :
But I don't know why the apps won't start 😦
I do have a recent docker :
Docker version 28.1.1, build 4eba377
26 replies
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