-
Hi, I am somewhat new to the scene with all this setup, and figuring out what is wrong with the config to the point where the container seems to loop when trying to find the best server to connect to. I feel as though over many troubleshoot replies on other pages, and things I try, I can't seem to get it to work. It seems to fail to resolve DNS at the beginning, and loop when trying to find the best Nord server to connect to. Here's my latest log:
And then this is my compose:
Any ideas as to why it has decided to fault? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
Hello, your container has no dns resolution and/or internet access. As you have defined google's dns, I bet the container has no route to internet. |
Beta Was this translation helpful? Give feedback.
-
Good to hear, I’ll try to add a link in the documentation then
…On Thu, Sep 30, 2021 at 18:21 Xalvas ***@***.***> wrote:
Hurrah!
Having that backend for libsec has worked a charm. Loads just fine now.
*Thank you* for your help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1975 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYUXFXXQVOJS2HTBTGDUEQTYLANCNFSM5E7MQL3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
Hello,
your container has no dns resolution and/or internet access. As you have defined google's dns, I bet the container has no route to internet.
several clues:
WARNING: initial DNS resolution test failed
curl: (28) Timeout was reached