Question
Ghost installed into Droplet via Marketplace - working, but throwing errors
Hi all, I am running ghost on a droplet - installed via the marketplace - and all seems to be well. However - curiosity led me to look in /var/logs/nginx, which is slowly filling with errors.
The errors look like this (redacted with xxx):
2020/01/28 12:44:00 [error] 11444#11444: *11635 open() “/var/www/ghost/.well-known/nodeinfo” failed (2: No such file or directory), client: xxx.xxx.xxx.xxx, server: xxxxxxxx.com, request: “GET /.well-known/nodeinfo HTTP/1.1”, host: “xxxxxxx.com”
I’m wondering if somebody else has stopped these errors from occurring, and where is the best place to do it / best method to do it. I’m guessing it’s something to do with certbot and/or the nginx configuration, but don’t want to go tinkering if somebody else has already solved it.
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.
Just had time for another look. The errors are being thrown following requests from spiders that are hitting the site, looking for both status.net installation paths, and the default “well-known” folder structures.
I guess the only thing that doesn’t make sense is why nginx is throwing errors instead of 404s when the paths are requested.
I had a few minutes this afternoon, so started digging. It’s interesting - the IP addresses doing GETs that cause the errors to appear in the logs are always from two locations in Germany, and seem to happen every few hours. Thinking about it - whoever is doing it, is specifically doing a get of the /.well-known/nodeinfo path - which doesn’t exist…