Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Should /etc/hosts have the IP and domain name I want to use with the vps? Question Question
Can I assign a firewall while creating a droplet via API? Question Question

Question

Fresh Droplet loads a lot and browser returns "server not responding"

Posted July 12, 2021 115 views
Getting StartedAPIDigitalOcean Droplets

I have just created a droplet, installed jre, jkd and maven. I uploaded a SPRING project that was running perfectly on my machine in Idea editor, but when I access <ip>:8080, it loads some long time and then browser returns “server not responding”. Why is that?

All that I did was just fetch from GitHub.
Also, this is how I am starting the app:

mvn clean install
java -Xverify:none -Djava.security.egd=file:/dev/./urandom -jar target/app-0.0.1-SNAPSHOT.jar

Also, to permanently deploy the app, all that I do is add an & at the end of the second command. Is it fine? Do you recommend that?

Add a comment
TheJavaDevv2
By:
TheJavaDevv2

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Should /etc/hosts have the IP and domain name I want to use with the vps? Question Question
Can I assign a firewall while creating a droplet via API? Question Question

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.

×
Submit an Answer
1 answer
bobbyiliev July 12, 2021

Hi there @TheJavaDevv2,

If you have a firewall like ufw make sure to open port 8080:

ufw allow 8080

Also I could suggest using netstat to check if the application is actually listening on 0.0.0.0:8080 rather than 127.0.0.1:8080 as if you want it to be accessible from the outside world, it has to be 0.0.0.0:8080:

netstat -plant | grep 8080

Regards,
Bobby

Reply Report

Related

Looking for something else?

Ask a new question Search for more help