-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
DNS over TLS errors #1731
Comments
OP, what are you doing to address your ipinfo.io issue?
|
I am getting the same error using Windscribe as well. I don't have the "too many requests" error either. I've tried both v3.34.3 and v3.35.0 -- Edit: My issue was due to my firewall. The docker container changed its IP, so I had to add the new subnet to its allowlist. |
I'm not getting any ipinfo.io errors anymore but still having the same issue. I don't think it's an IP issue for me as I'm in bridge mode and my box is bound. I could be wrong though. 2023-07-08T06:09:49+01:00 INFO [vpn] starting |
Bump, I'm still getting errors: |
Try #137 (comment) Unbound is probably crying for whatever reason, it should be dropped out soon. I'm actively working on |
Is this urgent?
No
Host OS
No response
CPU arch
x86_64
VPN service provider
Windscribe
What are you using to run the container
Portainer
What is the version of Gluetun
sha256:5134e8ddb8b747d0bd8623d6635a4872c459d621ac9a19c839dc9feef65032fe
What's the problem 🤔
I've been getting DNS over TLS errors using windscribe that leads to failed healthchecks and my network being unstable (causing my other containers with this as a dependency to crash). Unsure what the problem is might be a permissions issue?
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: