By Hammad
Hello, I was busy with my job and other things. Today, when I tried to log into my drop, which is an InfluxDB dashboard, it is not loading for me.
First of all, the page will not even load in Safari (I used to use Safari before), giving this error
## Application error: a client-side exception has occurred while loading www.digitalocean.com (see the browser console for more information).
Then I switched to Chrome and login finally worked but my site is no longer works. Actually, it is very unpredictable, one time site was loaded but it did not prompt for login credentials (which is usually does) and the dashboard has incomplete information.
I am wondering if anything has changed in the past 3 months? Did anyone exerpeince similar issues? What do I need to fix it?
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!
Hi there,
Nothing on the DigitalOcean side would randomly break HTTP access just because you were away for a few months. This almost always turns out to be a droplet-level issue.
First thing I would check is whether the InfluxDB service and whatever is serving the dashboard (nginx, Apache, or the built-in UI) is actually running. After a long uptime, crashes, failed updates, or disk-full situations are very common. A quick systemctl status on the related services usually tells the story.
The Safari error is just a frontend symptom. The fact that Chrome sometimes loads partial data and skips auth strongly points to a broken backend service, corrupted state, or a reverse proxy misbehaving.
Also check:
- Disk space with
df -h(full disks break databases in weird ways) - Droplet CPU and memory graphs in the DigitalOcean dashboard around the time it started acting up
- Any OS updates that might have been applied before things went unstable
Let me know how it goes!
Heya, @hammadcoral
DigitalOcean itself did not change anything that would break your InfluxDB dashboard. Safari’s “Application error” is just the DO control panel failing to load in that browser, not a problem with your Droplet. Since Chrome works, you can ignore that part.
When an InfluxDB dashboard suddenly becomes unreliable, doesn’t always load, or skips the login screen, the cause is almost always inside the Droplet. The most common issues are a full disk, an InfluxDB service that crashed or is stuck restarting, or a reverse proxy returning partial responses because of a certificate or upstream error. Sometimes the browser cache can also cause inconsistent behaviour.
The quickest way to diagnose is to open the Droplet console or SSH and check the disk with df -h and check whether InfluxDB is running with systemctl status influxdb (or docker ps if you run it in a container). If those look normal, try loading the dashboard in a private/incognito window to rule out browser issues.
Regards
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 AI-native businesses
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.