Our IIS server on Win server 2012 started to return random errors like this:
2016-09-06 10:24:03 192.168.169.253 GET /3dModels/Webgl/bfd414ba72b84478/thumbnail.png - 80 - 256.256.256.256 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/53.0.2785.89+Safari/537.36 http://server.example.com/WebModels 404 502 0 46
2016-09-06 10:24:03 192.168.169.253 GET /3dModels/Webgl/b05e8a3f5b634244/thumbnail.png - 80 - 256.256.256.256 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/53.0.2785.89+Safari/537.36 http://server.example.com/WebModels 404 502 0 62
2016-09-06 10:24:03 192.168.169.253 GET /3dModels/Webgl/adb7ebeeb4554dd8/thumbnail.png - 80 - 256.256.256.256 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/53.0.2785.89+Safari/537.36 http://server.example.com/WebModels 404 502 0 78
2016-09-06 10:24:03 192.168.169.253 GET /3dModels/Webgl/92fada3f39254a7a/thumbnail.png - 80 - 256.256.256.256 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/53.0.2785.89+Safari/537.36 http://server.example.com/WebModels 404 502 0 78
I didn't find any documentation for error 404.502. In browser it is just common 404 with returned error html page from IIS. Thumbnails are 100% accessible through browser (tried to open it with direct url) and count of 404 are random. Every reload generates few of them on various PNGs. Funny think is when I disable cache in developer tools, all images are loaded correctly.
Do you have any idea what causes this problem? Thanks!
Hmm, It works now, but I don't know why. Here is some talk about it...
http://forums.iis.net/t/1233477.aspx?HTTP+Error+404+502+Not+Found
Related
Having followed the guide to setup django, postgres and nginx in digitalocean, am get different results for different urls.
Am using ubuntu 20 and python 3.10
<IP>:8000 => is working perfectly well
<IP> => 404 Not Found
<https://DomainName> => Showing the html page but Not showing the static files
<https://www.DomainName> => 404 Not Found
Where am I messing up??
Well unless you use web standards which ports are 443 for https and 80 for http you need to manually specify the port your service is located.
When creating a default react project or a default nextjs project I get 404's I've tried on different machines and there it worked without any issue, so I am wondering what is wrong with my mac's configuration.
What Id did:
Create a new nextjs project using "npx create-next-app"
Everything got installed correctly (I am using node v16.9.1, but had the same issue with 14.6.x)
when I now run: npm run dev in the newly created folder the server starts correctly on port 3000
when navigating to 0.0.0.0:3000 the page doesn't load and remains white however the console shows:
GET http://localhost:3000/_next/static/chunks/webpack.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/chunks/main.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/chunks/react-refresh.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/chunks/pages/_app.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/development/_buildManifest.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/chunks/pages/index.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
localhost/:1
GET http://localhost:3000/_next/static/development/_ssgManifest.js?ts=1632035639230 net::ERR_ABORTED 404 (Not Found)
when trying a "naked" react app:
npx create-react-app react1
cd react1
npm starty
I get the following errors:
GET http://localhost:3001/%PUBLIC_URL%/manifest.json 400 (Bad Request)
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
favicon.ico:1
GET http://localhost:3001/%PUBLIC_URL%/favicon.ico 400 (Bad Request)
The attempt to bind "/%PUBLIC_URL%/manifest.json" in the workspace failed as this URI is malformed.
Probably both are not related, just wanted to add it in case they are.
I faced a similar issue with an existing project when I cloned the git repository to a Windows machine. I got the same error messages on browser console after running the app. It took me hours to figure out the cause of the problem.
It was that the project folder had a special character. Lets say it was Hello%20World. Renaming the folder to Hello-World fixed the problem. The "%" character was causing that issue.
I have a little problem with CUPS 2.2.7
This is my /etc/hosts file:
127.0.0.1 example.com
127.0.0.1 localhost
in http://localhost:631/ CUPS is working right
but in http://example.com:631/ it doesn't work on the same pc.
The message error in View error log is that one:
E [21/Feb/2019:11:54:18 +0100] [Client 33] Request from "localhost" using invalid Host: field "example.com:631".
The web page on Firefox print an error message Invalid request and give me an Error (error code: 400) but seems point on CUPS.
How to solve this problem so that example.com:631 points to localhost and CUPS answers it successfully instead of Error 400: Access Denied.
By default cups servers HTTP requests only with HTTP Host header equal to "localhost". To allow it servicing requests for additional HTTP host headers use ServerAlias directive as described in the man cupsd.conf documentation. It's common to do the most unsafe thing and add
ServerAlias *
to /etc/cupsd.conf to allow all possible HTTP host headers to be serviced.
I know this is old, but I too was experiencing the same issue recently and I resolved it by updating the following line in cupsd.conf from:
Listen 0.0.0.0:631
changed to:
Listen *:631
For those that maybe care to know, I'm running CUPS within a docker container, and this change corrects the "Bad Request" response.
Im using GAE for my nodejs express backend. It worked earlier, but suddenly I keep getting
Error: Server error.
The server encountered an error and could not complete your request.
Please try again in 30 seconds.
My error logs is like this :
default[20181129t203637] "GET / HTTP/1.1" 500
default[20181129t203637] "GET /favicon.ico HTTP/1.1" 500
default[20181129t203637] "GET /favicon.ico HTTP/1.1" 500
default[20181129t203637] "GET /favicon.ico HTTP/1.1" 500
I tried adding favicon.ico to my public folder and install npm serve-favicon for the favicon.ico but same error still persist. I thought it was a limit but I tried changing accounts, changing different express project, the same error still comes out.
my app.yaml file :
runtime :nodejs8
instance_class: F4_1G
Also have cron.yaml file but I haven't run the cron job yet.
There is nothing wrong with my project when it s run locally.
Is there any way to fix this?
This is probably because you don't have active instances ready to handle requests, which causes them to time out while App Engine loads your code into a fresh instance. You can mitigate this by reducing the time it takes to load your code or by implementing warmup requests to keep your instances alive when there isn't any traffic.
I know people are scanning my server to use it as an open proxy. I am running nodejs through an express framework on an amazon cloud machine. I am using iptables to port forward port 80 to 8080 so I can avoid running it as a root user.
GET http://www.baidu.com/ 200 1.484 ms - 6482
GET http://yahoo.com/ 200 1.557 ms - 6482
GET /css/index.css 304 1.310 ms - -
Obviously yahoo and baidu are not part of my domain so shouldn't they return 404?
When I use
curl --proxy <<mywebsite>> http://yahoo.com
I get the html for my root page instead of yahoo. Why is this not 404ing?