Hi guys, I recently succeeded in configuring a VPN connection for my droplet. I did however lose my health data in the graphs, probably since the DO graph data can’t be obtained from behind the VPN.
I ran into similar SSH-connection problems because of connecting to a VPN, so I’m guessing this is the same problem. To ensure SSH-availability I excluded port 22 from the VPN to be allowed, so maby if anyone knows which port is used by DO for the droplet health data I’m able to allow that connection aswell? I want to state clear that I’m guessing, any more information about the health data monitoring is much appreciated.
Kind regards, R.
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!
Accepted Answer
Hi there,
I think that the Droplet health metrics stop showing if the monitoring agent can’t reach DigitalOcean’s metrics endpoint. It sends data out over HTTPS (port 443), so if your VPN setup is blocking or rerouting outbound traffic, that’s likely the issue.
Try allowing outbound traffic to metrics.digitalocean.com on port 443 in your VPN config or firewall rules. That should get your graphs back online. Also, good call on excluding port 22 for SSH, same idea applies here, just for monitoring traffic.
- Bobby
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.