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
blocked ip in spam Question Question
Having MongoDB Startup Errors! Question Question

Question

Parse Dashboard has stopped working (ERR_CONNECTION_REFUSED)

Posted October 26, 2019 1.2k views
DigitalOceanAPIDNSUbuntu 16.04

My server is configured (Parse Server).

I already restarted the services, but the Parse Dashboard access ip (http://SERVER_IP:4040/login) has stopped working. displayed the error (ERRCONNECTIONREFUSED)

This occurred when you informed the status: https://status.digitalocean.com/incidents/l9rrfkfrdhnd (Oct 24, 2019
DNS issues with Managed Databases)

Please tell me a solution, this was not my fault, thanks.

Add a comment
appcarrareto
By:
appcarrareto
edited by bobbyiliev

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
blocked ip in spam Question Question
Having MongoDB Startup Errors! 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 October 28, 2019

Hello,

DNS stands for Domain Name System. The DNS can not really affect your application as you are visiting it via your IP address and in this case DNS is not being used at all. The DNS issue that you’ve mentioned would only affect your domain name in case that it was using the DigitalOcean’s Nameservers.

I would recommend checking the following things on your server:

  • Check if port 4040 is open for incoming TCP connections:
sudo ufw status

  • If the port is not open, then you would need to open it

  • Make sure that the parser server is actually running after the restart

  • Check your syslogs

sudo cat /var/log/syslog

Hope that this helps.
Regards,
Bobby

Reply Report

Related

Looking for something else?

Ask a new question Search for more help