oidc_util_http_call: curl_easy_perform() failed on: https://<<endpoint>> (getaddrinfo() thread failed to start\n) #977
Replies: 2 comments
-
some googling suggests that it is due to a local issue, firewall- or resource- related |
Beta Was this translation helpful? Give feedback.
-
yeah, I have the same idea as well and I had a network resource to trace the network routing and indeed it was a firewall issue and after the firewall issue was fixed, I could see traffic going through to the OIDCProviderMetadataURL https://<>/ext/.well-known/openid-configuration endpoint by testing it with curl -v https:///ext/.well-known/openid-configuration And I even tried with And the same configuration works in our stage env. But off course our stage env has a different OIDCProviderMetadataURL https://<>/ext/.well-known/openid-configuration endpoint I have looked at curl and libcurl and compared it to the stage env and its all the same installations Here is the OIDC config |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
does any one seen such problem ?
oidc_util_http_call: curl_easy_perform() failed on: https://<> (getaddrinfo() thread failed to start\n)
where
OIDCProviderMetadataURL https://<>/ext/.well-known/openid-configuration
Beta Was this translation helpful? Give feedback.
All reactions