-
Notifications
You must be signed in to change notification settings - Fork 107
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
:nxdomain when calling Goth.Token.for_scope/1 #60
Comments
Hi, sorry to be a nuisance, but any direction on this would be super helpful! Thank you!! |
Sorry, I somehow completely missed this initial issue report! Goth should only be falling back to hitting that internal Google metadata host when it can't find any other configuration. Have you configured Goth to use your service account json credentials, most likely via something like this in a config file: # via a variable that contains the json
config :goth, json: credentials_json
# or, via an ENV var
config :goth, json: {:system, "MY_GCP_CREDENTIALS"} (There are other ways to pass in your credentials, but those are the two most common.) |
@peburrows Thanks for being patient with my issues. |
I think this is an error with how :inet_res works on newer erlang versions. 10.4.4 ERTS for example cannot parse a domain with a trailing /, but 10.2.2 ERTS can. |
I have been trying to auth with Google with
Goth.Token.for_scope/1
, and would get this error:Looking in to the code base, I found it is trying to call
http://metadata.google.internal
, hence the:nxdomain
error. I feel I missed something during the setup, but can't figure it out. How should I understand this error?Thanks
The text was updated successfully, but these errors were encountered: