Ok, got it. I think it generally gets to the container. Tab shows correct name etc. but then the website displayed either times out or just shows a spinning circle where it would normally show a login page.
The container needs Websocket support, is there anything I need to do on the Caddy side for that?
At this point I do not know what other than the Caddy Log I could be providing.
The container we are talking about is ShellNGN. Like I said, works with Nginx Reverse Proxy. So somehow Nginx musst do something that my Caddy does not currently do.
I checked the container log for shellngn but that however the shellngn container log really doesn’t show a whole lot other than that the container started successfully.
What specifically can I check at this point to track it down?
Lastly is there a way to limit access to bitwarden.my-domain.com/admin
?
I have seen this in the forum respond /admin* "The admin panel is disabled, please configure the 'ADMIN_TOKEN' variable to enable it"
Where would I put it? Under reverse proxy, within handle
?
*.my-domain.com {
tls {
dns cloudflare TOKEN
resolvers 1.1.1.1
}
# Standard reverse proxy
@bitwarden host bitwarden.my-domain.com
handle @bitwarden {
reverse_proxy http://10.10.1.119:5555
}