Question
Parse Dashboard has stopped working (ERR_CONNECTION_REFUSED)
- Posted on October 26, 2019
- Ubuntu 16.04DNSAPIDigitalOcean
Asked by appcarrareto
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 (ERR_CONNECTION_REFUSED)
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.
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
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:
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
Hope that this helps. Regards, Bobby