Hot answers tagged

5

This is perfectly normal internet background noise. As long as you keep your applications updated and endpoints known, there is no need to worry. If you want to filter the traffic from entering your server at all, then you can use CloudFlare for example. They have a Web Application Firewall, which filters most common web scans.


3

Here is an example NGINX configuration block for webscokets. Notice how the connection is upgraded if a valid websocket connection is made to the end point http://127.0.0.1:8080/wsapp More at NGINX as a WebSocket Proxy location /wsapp { proxy_pass http://127.0.0.1:8080; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; ...


2

Since you can't control your clients then the safest way would be to start using some other CA issued certificates. One possible CA would be ZeroSSL (https://zerossl.com). They offer also certificates via ACME protocol without any fee like Let's Encrypt (https://zerossl.com/letsencrypt-alternative/) and have a pretty good compatibility with older devices (...


1

Your EBS disk is full. The easiest way to deal with this is to delete files from the disk. If that's not practical: In the AWS console increase the size of your EBS disk (link) In Linux extend the size of your file system so it uses the space available on the EBS disk (link)


1

I found the image, it is right there. If you don't specify the version (or rather a :tag), the common approach is that the :latest is used implicitly, which (in theory) should correspond to the latest available dockerized version of the software you are running. Thus this leaves you with options to either use the latest or go through available tags and ...


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

In your second picture, the socket.io lib is using polling. This may come because you didn't set the nginx config properly. location /socket.io/ { proxy_pass http://localhost:5003/socket.io/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; } ...


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

Bit of an old thread, but changing the following worked for me: In /usr/local/lsws/fcgi-bin/lsnode.js (or wherever your lsws installation lives), find the function startApplication() and then change the line: var consoleLog = process.env.LSNODE_CONSOLE_LOG || '/dev/null'; to var consoleLog = '/path/to/your/logFile.log' || '/dev/null'; Ensure the file ...


1

In my case the issue was that the ownership of /var/lib/nginx was wrong. All other directories that nginx writes to were owned by www-data, whereas the 'nginx dir was owned by root. In this case the best solution is to change the directory ownership to match that of the other dirs that nginx writes to.


1

https://forum.nginx.org/read.php?2,254918,254918#msg-254918 mention RFC2616, 8.2.2 also is related: According to RFC2616, 8.2.2 1 if the request contained a Content-Length and the client (nginx in this case) ceases to transmit the body (due to an error response) the client (nginx) would have to close the connection


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