DigitalOcean www server

It doesn't look like we have a tracking issue for this, although much has been discussed spread out over several Slack discussion threads. See also https://github.com/nodejs/TSC/issues/1416.

Summary

Our DigitalOcean hosted droplet for our www server (one of two servers behind a Cloudflare load balancer) has become very unreliable this year, seemingly getting worse to the extent that over the last few weeks it "works" for about a day (or less) and then runs out of file descriptors (error messages visible in the nginx error logs) and Cloudflare believes the server to be unhealthy (=cannot reach the /traffic-manager endpoint?) and switches over to the other server (called Joyent but now resides on Equinix Metal).

Prior to the last few weeks the "unhealthy" state was temporary -- eventually CF would decide the server was healthy again and switch back to the DO server but now it appears that the DO server remains unhealthy in CF until we restart nginx.

Start by reviewing the linked TSC issue and the Slack discussions referenced in the report, then inspect the DigitalOcean server's nginx error logs and the Cloudflare /traffic-manager health behavior. Done means identifying why the server exhausts file descriptors and remains unhealthy, and confirming reliable operation behind the load balancer.