Hot answers tagged

3

If ntpd is exiting regularly, it means that it's having problems keeping your clock in sync. You probably want to be notified if this happens, so getting your process monitor to send an email or alert whenever it restarts ntpd might be a good idea. However, if you have an extremely poor quality local clock, this might happen a lot, so combining the -g flag ...


2

For anybody who stumbles on a similar issue. The problem is in this line: /home/ubuntu/.pm2/logs/* { In particular, the catch-all * should be swapped with *.log, or else, the rotated files (with extension .1, etc.) shall also be rotated upon the next rotation cycle. This fixes the issue: /home/ubuntu/.pm2/logs/*.log {


1

From comments There is problem with quotation in proxy_pass. It should looks like: location / { proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $http_host; proxy_pass http://127.0.0.1:5000; } location /api { proxy_pass http://127.0.0.1:9000; }


1

According to TFM, you need to add a key entry.


1

Looks like someone is attempting XXE vulnerability exploit https://portswigger.net/web-security/xxe Edit:IP on the 8th line, 45.147.77.236, is from Iran. IP on last line is from Netherlands with a bad reputation https://www.abuseipdb.com/check/203.159.80.188 You should definitely look into GeoIP blocking if you don't deal with those countries, as well as ...


1

You are mixing serving Javascript files to the browser and serving node.js app as a backend application. It seems that your node.js app (npx http-server) is an HTTP server itself and it serves your static files to the browser. You don't need to run npx http-server behind nginx if you only need to serve static files to a client browser. But if you need to run ...


1

When you are requesting https://creatorbrandedsite.tk/, the following events happen: Browser queries DNS information for creatorbrandedsite.tk It receives CNAME response, and proceeds to look up subdomain.learnbot.tk A record. It connects to IP address for subdomain.learnbot.tk. It requests domain creatorbrandedsite.tk from your nginx server. Your server's ...


1

With EC2 you don’t have to make it right from the start because it’s easy to change the instance size later. For start make a guess - e.g. new project may be ok with t3.small, moderately busy site may do for example with m5.large, etc. Once it’s up and running monitor the CPU and memory utilisation in CloudWatch and if the chosen instance type was too big ...


1

Try to add proxy_set_header X-Forwarded-Proto $scheme; inside location block


Only top voted, non community-wiki answers of a minimum length are eligible