Question
Why Can't I Connect to my (Droplet's) Server? It's Working
- Posted on May 7, 2023
- Getting Started
Asked by TinyAzureDolphin
I have a Next.js server. It’s up and running, and I know because when I do wget myserveripaddress:30002 from the server itself, I get a (valid) index.html file.
However, when I do the exact same thing from my own machine (or use my browser), the request times out. It’s like there’s a firewall that I never setup blocking things.
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.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
It turns out there is a firewall installed by default. I was able to open it up (thanks to a little help from Digital Ocean support) with the command:
Hello @tinyazuredolphin
You can check the address is resolving, e.g the domain name is reachable. There might be a DNS conflict or some DNS cache that can prevent you to load the resource from your local machine.
You’ve correctly checked that the next.js server is running and also that the wget command will return successful result, but this happens only on the server. You can test this from another machine as well or using different network.
Regards
Hi @tinyazuredolphin,
Are you using a domain? If it is, see if your domain is pinging from your Droplet:
Additionally, enter your Droplet via SSH and see in your logs if anything is being blocked.