Documentation

https://docs.digitalocean.com/products/monitoring/concepts/metrics/#disk-utilization This article needs to be updated to reflect that disk utilization alerts only consider root storage & does not include attached volumes.

doctl compute ssh-key import ... documentation inconsistent with command usage. It says I'm missing required arguments, but no idea from online docs or help option what that would be. From the doc: Usage: doctl compute ssh-key import <key-name> [flags] In reality: $ doctl compute ssh-key import mykey Error: (ssh-key.import.public-key-file) command is missing required arguments [flags] should be optional, so what other arguments are required???

The environment variables page doesn't list an env variable containing the private host for the database to connect from the app in the same VPC.

It should be documented that variable names, such when you do ${my-db.DATABASE_URL} are truncated to 32 chars., i.e. if your db name is too long, you have to use the first 32 chars as the variable name.

I’m deploying a small web-tool that lets users input ID numbers and check public assistance status (similar to a “data lookup” service). I plan to host on DigitalOcean App Platform or a standard droplet + Nginx + Gunicorn. Key concerns: How to manage access security (rate-limiting, IP blocking) Encryption of user queries & responses in transit & at rest Keeping it lightweight and low-cost as usage grows Best way to enable automated backups and scaling if traffic spikes Any architecture examples or “gotchas” people have seen? https://cekbansosonline.com/

Your "Ask Docs" AI got things way wrong. Please review and consider fixing where needed so the next poor person doesn't go down this incorrect rabbit hole. See attached.

After spending way too many hours troubleshooting a "simple" PeerTube installation, I decided to document everything for the community. What started as following the official docs turned into a 3-hour debugging session with Node.js compatibility issues, database authentication failures, and missing dependencies.

Ability to Bookmark Tutorials. I don't want to keep a track of comments and updates. But at times I just want to go back to the tutorial I read last week quickly. Yes I can use Browser bookmarks but it would be better if Digitalocean alows us to keep a list of tutorials to refer to again.

Problem: My ni-n8n.com domain was registered through Digital Ocean and I configured the DNS records several hours ago, but the domain doesn't resolve from any public DNS server. Technical details: Domain: ni-n8n.com Registered with: Digital Ocean Nameservers: ns1.digitalocean.com , ns2.digitalocean.com , ns3.digitalocean.com (automatically configured). Type: A Hostname: ni-n8n.com Value: 216.198.79.1 Type: A Hostname: n8n.ni-n8n.com Value: 167.172.31.249 Type: CNAME Hostname: www.ni-n8n.com Value: 2fde31b8702a86eb.vercel-dns-017.com Elapsed time: More than 6 hours since the last configuration Tests performed: nslookup ni-n8n.com 8.8.8.8 → NXDOMAIN nslookup ni-n8n.com 1.1.1.1 → NXDOMAIN nslookup ni-n8n.com 9.9.9.9 → NXDOMAIN Request: Please check if there are any problems with the DNS zone of my domain or if there are any unusual delays in your system. The records are properly configured in my control panel, but the domain doesn't resolve from external DNS servers. Additional Information: Control Panel shows logs as configured correctly This is a production domain and I need to resolve this issue urgently My associated droplet ID is: 167172349 (travel-n8n server) Thank you for your help.

In order to migrate seamlessly from HTTP/1.1 to HTTP/2 cleartext ( rationale ), I went through the following steps: I kept my HTTP/1.1 server on port 8080 and added a secondary h2c server on port 8081. The deployment was fine. I edited the app spec via the web frontend to change the service's port from 8080 to 8081 and add protocol: HTTP2 as outlined in the documentation . Unfortunately the deployment failed as it looks like the health check was never successful. Here's what I got from the deployment log: > Sep 12 10:26:59 ERROR failed health checks after 12 attempts with error Readiness probe failed: Get "http://<private-ip-address>:8081/v1/health-check": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x00\x00\f\x04\x00\x00\x00\x00\x00\x00\x03\x00\x00\x00d\x00\x06\x00\x00@\x00\x00\x00\b\a\x00\x00\x00\x00\x00\x7f\xff\xff\xff\x00\x00\x00\x01" Is it possible the health check feature doesn't support h2c yet?