Closed pinpox closed 11 months ago
@pinpox , I am not sure whether this applies, but there are 2 options available for you: delay and retry.
https://authp.github.io/docs/authenticate/oauth/backend-oauth2-endpoint
Keeping it open and waiting on your response.
That is great, but even better would be infinite retries. What sort of status (/metrics ?) can one get about the state of authp?
@pinpox , I am not sure whether this applies, but there are 2 options available for you: delay and retry.
https://authp.github.io/docs/authenticate/oauth/backend-oauth2-endpoint
Keeping it open and waiting on your response.
I managed to get it working with:
delay_start 5
retry_attempts 5
retry_interval 10
Thanks for the hint!
Describe the issue
Caddy can't start if the OIDC provider itself is behind the proxy.
I'm running an OIDC provider (dex) behind caddy as a reverse proxy at
login.mydomain.tld
. Adding caddy-security, makes caddy fail to start with the following error:This seems to be related because of a deadlock: Caddy is not running -> Caddy can't reach
login.mydomain.tld/.well-known/openid-configuration
to start with caddy-security -> Caddy can't startConfiguration
Paste full
Caddyfile
below:Version Information
Provide output of
caddy list-modules -versions | grep git
below:Expected behavior
Caddy should start and retry reaching the metadata url or start the reverse-proxy entries first, then the caddy-security related stuff
Additional context
Add any other context about the problem here.