As I was trying to edit firewall rules based on what I saw in this article (https://docs.digitalocean.com/products/networking/firewalls/how-to/configure-rules/), it appeared that some of my devices aren’t allowed to access VPN services (running on Wireguard), particularly in Uzbekistan. When I insert addresses, specified in network interface config file, e.g 10.10.10.1, inside Source field for a custom firewall rule the connection doesn’t work. Could anyone clarify what is wrong there?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
The address you mentioned (10.10.10.1) is not an Internet address, it is only a local address a.k.a. “not routable”. It may be used by your VPN provider, but that will be enclosed in the VPN, and invisible to the firewall.
You need to figure out what Internet address your VPN software is actually using to connect to the VPN. That is NOT the address you gave. It is something else completely.
Hello,
I believe that it is not DigitalOcean that is blocking any countries specifically, but the local ISPs in those countries are blocking DigitalOcean.
You could try reaching out to your IPS and ask them to lift the block.
You can also run an
mtror atracerouteto figure out where exactly the connection is being dropped.Best,
Bobby
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Sign up now