My NYC2 droplet seems to be behaving weirdly since the upgrade.
I can’t seem to pull from my git repo which is hosted on AMS droplet and requests from originating from my server to my subdomain which is on the same server times out.
My domains and subdomains can all be accessed without any problems from my own laptop at home.
It clearly seems to be a internal network configuration problem. It seems to have started since after the NYC2 network upgrade. There has been no changes to my setup at all before this problem started.
I would greatly appreciate some insight into why this could be happening?
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!
Some things weird here too. <br> <br>One of the droplet does not communicate with the external world. I can access it via ssh and through the web (httpd), but the droplet cannot get data from outside. No wget, curl, rsync, etc. ping works. It also works with other droplets, both IP and private IP. ip6tables: Firewall is not running. <br> <br>I would also be grateful for any hints. <br>
My droplet can connect with anything outside the DO network. Wget, apt, git everything works fine. I only have a problem when sending request within the DO network.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.