Quantcast
Channel: Nginx 400 errors due to random encoded string starting with "\x" from random IP addresses - Server Fault
Browsing all 5 articles
Browse latest View live

Answer by José Montiel for Nginx 400 errors due to random encoded string...

I had the same issue, checked the source IPs and some where from Google, which make me doubt some sort attack. Then I realized I had a default_server listening on 443, but no SSL certificate...

View Article



Answer by Yevgeniy Brikman for Nginx 400 errors due to random encoded string...

You are most likely seeing this because you are making an HTTPS request to an HTTP endpoint. For example, you're sending an HTTPS request to port 80 of your web server instead of 443. As a result, the...

View Article

Answer by Vadim for Nginx 400 errors due to random encoded string starting...

Similar behavior is observed when a BitTorrent client uses port 80 to connect to their peers.

View Article

Answer by Piotr Kieszczyński for Nginx 400 errors due to random encoded...

First of all I would try to decode this hex. As far as I noticed those are random chars. Are you familiar with this ip adress? Is it only one or plenty adresses? You tried to look it up? And probably -...

View Article

Nginx 400 errors due to random encoded string starting with "\x" from random...

I assume these are some sort of bots, but would like to know what are they trying to do to my server. The logs in questions are below and the IP address has been changed from the original. 12.34.56.78...

View Article

Browsing all 5 articles
Browse latest View live




Latest Images