#Google Social Login Setup and Blank Errors

1 messages · Page 1 of 1 (latest)

plain jungle
#

I have completely started over with a new Authentik instance after using this for a very long time. Currently, I'm trying to set up Google social login and cannot even save the main configuration screen, instead getting an error. Unfortunately, due to this bug (https://github.com/goauthentik/authentik/issues/10464) I have no idea what the error is. Are these error logged somewhere other than the main logs that I could see so I can hopefully set up the social login properly?

I was using the guide (https://docs.goauthentik.io/docs/sources/google/) to walk me through it, but the flow to set this up has completely changed and without errors, I have no idea what I'm doing wrong.

GitHub
Blank Error Boxes · Issue #10464 · goauthentik/authentik

Describe the bug The error box is empty and does not contain text To Reproduce Steps to reproduce the behavior: Do anything which would result in an error. Ex: Fill out #10463 Click enter You shoul...

Google | authentik

Support level: Community

solemn tangle
#

@plain jungle if you open the network tab when attempting to save, do you see an error 400 bad request?

#

try looking in the response the error should appear

plain jungle
#

Ah ha! Thank you! Now to figure out why it's failing.

Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7ac2e448da30>: Failed to resolve 'accounts.google.com' ([Errno -3] Temporary failure in name resolution)

plain jungle
#

Well, this is going to take some digging. Name resolution is fine on the host. The server is responding without issue to all internal and external traffic. But no go on DNS lookups, even though DNS is set to 8.8.8.8, 1.1.1.1

plain jungle
#

Well that was a fun thing to track down. Somehow (still haven't figured out how), I literally blocked all traffic from my containers. 🤪 At least it was an easy fix once I found what I did.

solemn tangle
#

im still convinced the saying "it's always dns" is true

plain jungle
#

I've decided my brain just didn't want to work the other day. As soon as you pointed me to where to find the errors, I at least knew where to look. It oddly wasn't DNS, it was a VERY badly configured firewall rule. Still, same difference - it couldn't reach even the internal DNS server, let alone the ones outside!

solemn tangle
#

Hey @cinder cove sorry to bother. would it be possible to know if there's a status update on the linked issue? Seems like a fairly annoying issue and it would be fun to see it patched in the next release.

cinder cove
#

it wont be in time for 2024.8 but we'll work on it right after, as a workaround you can open the browser developer tools and you should see the error in the request response

solemn tangle
#

👍