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.
Related
I've developed a small chat application with Socket.io and Express, currently deployed on my droplet at digital ocean. You can see it live at https://keleheart.com/chatapp. It currently doesn't work because the server is giving back a 404 for the chatapp/socket.io/socket.io.js script I have at the bottom of my html file, should be able to see that when you visit the site and hit f12
I've been through a few fixes already that were popular on here such as This one and this one and I've even tried changing the script from local to a CDN as depicted here , and the CDN seems to work better,(still gives the 404 but it then no longer says io isn't defined??) but it still doesn't produce the output I need.
You are able to review my repo on my Github Page for this as well, there's just the index.html file for the client and then the chatApp.js for the server. The error is coming from my html file but all the fixes have told me to manipulate my package.json, server variables, and nothing has worked so far. My server still cannot find chatapp/socket.io/socket.io.js
Have you tried creating the /socket.io folder next to index.html, and putting a copy of socket.io.js inside of that? That has always worked for me, but you might have to hunt through the node_modules folder to get the file. This always fixed it for me.
And of course, be sure to actually serve the file using express's static method.
Your browser is giving you the correct error message. Since /socket.io/socket.io.js does not exist on the server, the browser displays the server's 404 message.
I am working on some php files on a shared hosting. I am constantly making changes to the files and then running them in a browser to see the changes.
After a few hours of work, I repeatedly start getting 403 errors and have to wait a few hours to "get back in".
I can open the files in a browser on my mobile phone on the same wifi connection, so it's the same IP, but I cannot open them in a different browser on my computer.
I am assuming the hosting company is blocking me because of the frequent loads. Some of the files I am working on also send out emails via PHPmailer and soon after I start getting the 403 errors, if I continue loading the pages in my mobile browser, PHPmailer stops working. Probably the hosting company blocking me again. Changing to my mobile browser doesn't help with the PHPmailer error.
What I am wondering is if there is some way to bypass the 403 error without using a different device. The PHPmailer error doesn't bother me as much, but a solution to that would also be helpful.
Additional information that may be useful... or not:
I use .htaccess to prevent all IPs except mine from accessing the files.
I tried deleting cookies and changing the DNS.
Tried ipconfig /flushdns and ipconfig/all
Have no idea if those experiments were good ideas or not though... :/
I have read a few answers to try and find a solution to a ridiculous problem.
I dont have access to a server that I can log on to access phpmyadmin,
What is supposed to happen is that the web url is supposed to be viewed via https, and in most cases this happens.
Except for a particular PC I have at home and it never seems to open in https. Why this is happening on this given machine is completely unknown.
Is there a way I can set up a rule on my local machine that will ALWAYS convert http://pathtomysite.com to https://pathtomysecuresite.com, (possibly via the 'hosts' entry (and yes it is a windows machine running win10).
I could do this on the web server itself, I know how to do this, but the problem is, I don't have, nor am I allowed to have, access to the database server to update the .htaccess or webconfig.xml on the server. (I am 99% sure its Apache, not nginx or IIS).
Any help is allows gratefully received.
I'm having a weird issue with a website I have installed on IIS. I can access it if I go to (ip address)/defaultdoc, but not if I go to (ip address):(port). I'm running a debugger on my browser, and the only thing it's doing when I try to access the site with the port is pulling a 404 error. This is really weird to me because the default document for the site is definitely the page that I go to when I pull up the site otherwise. Does anybody have any ideas why this might be happening?
Edit: I'm suddenly not so sure that the default document is working right. In IIS, it says that the default document is what I want, but when I run a list config command, I get something entirely different.
I have moved an Orchard CMS site from one host and server to another host and server. The IP address is obviously different.
All the files have been correctly copied and the correct html is rendered.
However, all the styles sheets produce a 404 error. I repeat that the files are where they should be.
Indeed, any other resource, such as images or stylesheets produce the same problem. Again, the files are all in place.
Can anyone think what could be causing this. Nothing has changed other than the server and IP.
I have another orchard site on the same IP and server that is working fine. However, it was not moved from a different server.
I ping for the site and it comes up with the correct IP address for the new server
EDIT:
Not sure that this is Orchard specific, although something related to Orchard's themes and how they work could be to blame... But I really can't see what.
It sounds much more like an IIS issue.
Can you get the CSS files, by entering their URLs into the browser address-bar directly?
Try "Copy image location" or from the Image Properties, of one of the failed images. Again, can you get this if you enter it direct into the browser?
Check the URL of failed resources, against the URL of working HTML resources or dynamic pages. make sure there are no differences in webapp path or context..
You'll also need to try Ctrl-R reloading.
There could also possibly be some caching in the way.. that might be holding the "404" or "not found" results, even after the content has moved. Try & shutdown/ or force refresh all server & proxy caches.
The server people got back to me. They changed the "website to 4.0 Integrated Pipeline mode." and all now works. Go figure.
I am sure I had checked that it was in Integrated Pipeline mode, but hey ho.