I have a website written in HTML5 and have already added it to iis7. I checked to make sure that the path was correct, and both the path and the authentication are reported as being correct by iis. I have a personal DNS that I am using to host the site, and I have the website in IIS being hosted by that DNS. Whenever I go to browse to the site, internet explorer kicks back a page saying it could not connect to the page. It will not let me diagnose any connection problems. Any idea what could be going wrong and how I can fix it?
Related
I am trying to host my own web page on an Ubuntu server. I can access the webpage if I type the IP address in my web browser, but I can't if I type the domain name (a free one from Freenom).
But if I use the command curl my.domain.name then I get the index.html contents. So, why can't I access the page via my web browser (Firefox/Chromium)?
Note that the ping command also works fine (no packet loss). Finally, I am not hosting the web page on the same computer as the one trying to access it. So far, my best guess is that the problem comes from the web browsers or Freenom, do not hesitate to ask for more info, I will edit my post.
I'm using Windows 10 and try to access to the localhost of the IIS Manager, but neither the web site I create or the default web page can be accessed
I tried activating .NET extensibility 3.5 and 4.6 and also activated Static Content to see if that solved the problems, but it appears that it doesn't.
On Microsoft Edge Browser I get this:
"HTTP 404 error
That’s odd ... Microsoft Edge can’t find this page"
And on Google Chrome I get a blank page.
EDIT : I had Skype using the ports 80 and 443, and now on Microsoft Edge I get this "Hmm, we can't reach this page. Try this •Make sure you’ve got the right web address: localhost "
And I also changed the port of IIS to 8080.
Is there a page iistart.html in C:intetpub\wwroot? You may want to troubleshoot a few settings. Guide can be found here that might be some assistance to you.
I was facing the same issue, just went "uninstall" ISS and restart the PC, then go back and install it again, now it's working.
I am receiving the following error when trying to load a PNG (over https) into an iframe on Amazon's mechanical turk:
SEC7117: Network request to https://toucan.cs.colostate.edu/pp/images/125.png did not succeed. This Internet Explorer instance does not have the following capabilities: privateNetworkClientServer
You can view the page here https://workersandbox.mturk.com/mturk/preview?groupId=36TBNKR908TLAX7SKNTTRWW7TFYEDT It works fine in all other browsers.
I can't for the life of me figure out why Edge would be blocking PNG files (JS I can understand) and how to remedy it. Any ideas would be greatly appreciated.
More Info
Windows 10 64bit
Edge 20.10240.16384.0
Have tested on several machines and been able to replicate the problem
Have admin rights on all machines and they are not part of a domain.
Update
It seems to be an issue with the web server that is hosting the image which is running Apache. I placed the image on another apache server and everything worked fine. so then I tried to send the CORS header for all images as explained on https://github.com/h5bp/server-configs-apache/blob/fc379c45f52a09dd41279dbf4e60ae281110a5b0/src/.htaccess#L36-L53
but that still didn't solve the problem. For some reason Edge blocks the request.
The issue is Edge detecting the file server to be part of the local intranet, which is being referred to from a public website.
Related: SEC7117 Error when trying to load a javascript file in MS Edge
The solution is to host the files on a different subnet from what the computer you're accessing it from.
I have asked a similar question before here I sort of fixed it but im still facing a similar issue. Every time I try to load localhost, port 8095, I receive this error message in Google Chrome:
Google Chrome's connection attempt to localhost was rejected. The
website may be down, or your network may not be properly configured.
If there is a way to fix it, please tell me,
If not, please could someone inform me how to reset IIS to its original settings. Or if I can reset Windows Features so I can re-install ISS from scratch.
My website uses ASP with a connection to a SQL Server database (2012). Basic HTML pages also don't load under the URL, localhost:8095/
The servers were stopped because 2 services within administrative tools had stopped. World Wide Web Publishing Service and Web Management Service
I'm having a strange problem with a separately hosted subdomain I have. I'm running an application on Engine Yard, let's call it mysite.com. I have a wildcard SSL certificate installed there which covers all the subdomains (things like api.mysite.com). We recently decided to migrate our blog to be hosted independently (right now it lives on wordpress.com). Because I can't run the blog alongside our Rails app with ease on Engine Yard, I decided to grab some cheap hosting space from Dreamhost to host our Wordpress blog there. I set up the server there to fully host our subdomain (let's call it blog.mysite.com), and updated the DNS A record on Hover (our DNS provider) to point blog.mysite.com to the Dreamhost server. So here's the issue:
If I go to blog.mysite.com via Firefox or Safari on my Mac I see the basic Wordpress install which I set up. However, if I try to view things with Chrome I get the following error:
This webpage is not available
Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out.
This happens on all Macs running Chrome I could get my hands on. I tried both clearing the cache and flushing the DNS but nothing. The weirdest part is Chrome keeps looking for https://blog.mysite.com instead of http://blog.mysite.com. There is no SSL cert installed on the subdomain for the blog on Dreamhost because it's not necessary.
Has anyone ever come across this before? And in case anyone wants to try the actual address is http://blog.frestyl.com.
sounds like you have a 301 permanent redirect that Chrome registered http://blog.frestyl.com -> https://blog.frestyl.com. Besides clearing the cache I'm not sure what else can be done.