-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in app 'security' when starting Caddy server with oAuth2 with Google #135
Comments
@sidbena , thank you for the issue! There were no code changes that might have the described impact. Is it possible that you server traffic is proxied or firewalled? |
Yeah, that’s what’s a little odd, I haven’t touched the setup in weeks, since moving to the ‘security’ plug-in from the old setup that required two plugins, like ‘jwt’ and one other. I really don’t know what’s changed, really frustrating. |
@sidbena , you could add “debug” to your config. The error io/timeout suggests that your tcp connection fails. |
This is really ridiculous ... I tried adding |
@sidbena , it could have been something on the network side. Glad it worked out! |
@sidbena , I am looking to add testimonial sections to https://authcrunch.com. Could you please write one and send it to me at greenpau@outlook.com? |
Describe the issue
Since today (it seems), I'm getting the below error while trying to spin up my Caddy2 instance. This config has worked flawlessly for at least a few weeks.
{"level":"error","ts":1657485825.2251232,"logger":"security","msg":"failed provisioning app server instance","app":"security","error":"server initialization failed: failed configuring identity provider: failed to fetch metadata for OAuth 2.0 authorization server: Get \"https://accounts.google.com/.well-known/openid-configuration\": dial tcp: lookup accounts.google.com: i/o timeout"}
Attempting to contact
accounts.google.com
works just fine with curl or wget.Configuration
Paste full
Caddyfile
below:Version Information
Provide output of
caddy list-modules -versions | grep git
below:Expected behavior
I'd like the server to run smoothly again.
The text was updated successfully, but these errors were encountered: