Recently I started getting The connection was reset. error message (error code is ERR_CONNECTION_RESET) when I open one of my websites. This has nothing to do with application(node.js) level afaik as no changes or deploys were made in the application. To add to this, there were no error logs so I am assuming the request did not even receive the node app. The website is hosted on godaddy and its backend is a elastic beanstalk application. How do I fix this? On the web browser, in the second attempt it automatically loads correctly. But in a iframe which embeds my website, this has become a nasty issue as the browser does not even retry. I did the DNS analysis using dig command and all that but could not find anything relevant. Interesting part is this only happens after some interval (it does not happen continuously). On reload it works without fail.
Related
HTTPS conflicts with HTTP
I make my first full-stack project on React and NODEjs and deployed it on netlify.
My backend server runs on HTTP localhost.
And here is a problem:
My app works on my Mac in Chrome but doesn't work properly on other browsers and computers.
Other computers can download index.js (display sign-up and sign-in pages) and it seems there is no problem with CORS but authentication doesn't work.
Safari logs mistakes:
[blocked] The page at https://MYAPP.netlify.appwas not allowed to display insecure content from http://localhost:3500/register.
Not allowed to request resource
XMLHttpRequest cannot load http://localhost:3500/register due to access control checks.
I don't understand why the app works on my MAC but
doesn't on other computers and can't find an answer on how to solve this HTTPS - HTTP conflict
I have tried to find a problem in CORS but it looks like CORS is ok. Also, I tried rewriting the server with HTPPS but it didn't work.
I've never worked with Netlify, so I could be wrong, but I suspect your problem isn't directly related to Netlify.
The Safari error message indicates that your frontend is trying to talk directly to localhost. localhost is an alias for "the computer that is making the connection attempt" under normal circumstances. This means that when someone runs your frontend, the browser tries to talk to the backend running on the same computer that the browser is running on.
This works on your computer in Chrome because you probably have the backend running on your computer for testing. Safari is only complaining that the frontend was loaded via HTTPS but is trying to talk to non-HTTPS servers. It is not stating that it can't talk to the backend, it's stating that it won't even try.
If I'm right and you shut down the back end on your computer, it will start to fail on your computer as well, even on Chrome.
If this is the problem, the solution can be one of two things: You can either run the backend somewhere where it has a domain name/ip address that everyone can connect to, or you need to run a proxy for your backend somewhere where it also meets those conditions, and has a way to pass the request on to where your full backend does run.
You need to find a way to run your backend somewhere other than your own computer or have something somewhere else proxy requests to your computer which then gets relayed to the localhost address. How you go about that will depend on things you didn't specify in the original question.
I am hosting my website on azure and using cloudflare for dns and proxy.
Recently I started experiencing a problem where if I refresh a page a number of times, eventually I get the cloudflare 502 page. Refreshing the page again and it loads fine.
If I refresh the page without using cloudflare, i.e. I go straight to {mydomain}.azurewebsites.net I don't get the issue.
So obviously the problem is server/cloudflare side config. Any ideas on what could be causing this?
I think it is related to this issue: https://community.cloudflare.com/t/random-502-errors-for-last-3-days-caused-by-illegal-request-header-injected-by-cf-reverse-proxy/202061
The 502 Bad Gateway error is an HTTP status code that means that one server on the internet received an invalid response from another server... so as it stands you don't have enough information to figure out what is going on here.
You will need to find a way to get the web server logs from your server on Azure and possibly also the logs from Cloudflare.
As the title says, when the application is supposed to be built and good, (at least during deployment, the log files etc always state that the build was successfull) when everything should be set to go, I open the site and encounter 2 console errors:
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
Failed to load resource: the server responded with a status of 503 (Service Unavailable) favicon.ico:1
Tried looking up those errors and finding solutions but none of them seemed to work, Even though, the application works perfectly on local heroku (where you can test your app, in the heroku enviroment).
Not sure what I could do to fix my problem, as many forums suggest that you can't really do anything about it if it works fine on local heroku, it's must likely a server fault.
Thanks
edit: kinda fixed it myself after long days of struggling. Changed up file locations, moved server.js etc out from backend, into the main folder, and created a client folder, which now contains all the frontend stuff. Exact opposite what I used to have, since I used to have frontend out in the 'wild' and only had a backend folder for... well, backend files/folders/scripts.
Problem solved... kind of, still not sure why the first version i tried to use didn't work, but at the end of the day, I'm fine with it
I have been working with IIS 7 for a while and it has worked fine until it just suddenly started throwing 404 errors for my multiple websites even though they actually exist. All of the configurations seems fine (path, default document) but not a single file, no matter the format or location will be loaded.
Another strange thing is that everything works when I try to access the websites via localhost or 127.0.0.1 but not through my external IP.
Does anyone know why this could happen and how I can fix it?
Edit:
It appears this 404 page is not the built in IIS error page. It is associated with nginx but I'm not sure where the file is located on my server or why my pages are being intercepted.
It turns at the server was hijacked by Morfeus F***ing Scanner, which I was not aware was even a thing until this happened. It's activity showed up in the server access logs. I basically had to reset the entire server. It was quite a chore.
We're running ASP.Net (1.1) on a server with Windows Server 2003 R2 (Service Pack 2). We have an application (http://newserver.yourdomain.com/someapp) that performs a relatively basic process of taking the user-entered input and populates the data into the database. If there is a problem with the INSERT/UPDATE, a TRY...CATCH block will trap the error and redirect the user to a centralized "Error Handler" application (http://newserver.yourdomain.com/ErrorHandler) that displays a more user-friendly error screen and log all the relevant information. The Error Handler resides on the same server and runs ASP.Net (1.1) as well.
This has been working for years, but we're upgrading the servers and replicating all the same applications from the old server (http://oldserver.yourdomain.com) to the new server. For some reason, now when the application is attempting to redirect the user to the Error handler (via Response.Redirect), we're running into a "The page cannot be displayed" error (aka "Action Cancelled" error). I assume it's a configuration setting, but I can't think of what it might be.
To make things stranger, this happens in IE6 and IE7, but not in Chrome 12. Also, we can avigate directly the Error Handler URL without a problem. The issue seems to center around the need to redirect to that location.
Also, if I set up the old server (http://oldserver.yourdomain.com) to point to the new Error Handler (http://newserver.yourdomain.com/ErrorHandler), it works fine. The redirection seems to only be an issue on this new server.
Can you think of what the issue(s) might be?