My website, sarkelliancreed.comule.com, is not loading . I have tried it in Firefox, Chrome, Opera, and IE, and none of them display it. It isn't a 404 error. Any ideas?
Your server seems to be online as I can load Javascript files from it, but it raises several errors related to requests to https://nikkomsgchannel
https://nikkomsgchannel/e?00690027005a00210036003600190026005d0054005900500…230058002b003700630020002a00470058000a0059002f002a005e002d002d002c002a0029
Related
As of about a week ago, my website was working fine. Since Chrome version 54, I can't get it to load. The HTTPS request doesn't get any response and shows a status of "(canceled)". It loads just fine in Chromium, Firefox, Safari, and even Chrome 53. Chrome's developer tools don't give any helpful information - see the image.
Here is what it looks like in Chromium:
(You'll note that the second image shows the subdomain www. That's because, when the naked domain loads properly, it redirects to the subdomain.)
I tried modifying my server code (Node, Express) to print a message upon receipt of each request, and it doesn't even print when I visit the site in Chrome (54.0.2840.71 (64-bit)). It does print when I visit in Chromium (53.0.2785.143 (64-bit)).
I even tried using a different computer. Same thing - fails in Chrome, succeeds in Safari.
What could make it behave like this? I don't know where to begin troubleshooting this.
I don't really understand the behaviour, but I found a way to fix it in my app. I was using the NPM module spdy in place of Node's built-in https module to serve my app over https. Switching back to the built-in module solved the problem. (It's a simple change - the APIs are compatible.) I don't know whether spdy consistently has this issue in Chrome 54, but I've wasted too much time on this issue, so I will leave further investigation as an exercise for the archaeologist who next digs up this answer.
So, I have a selfhosted Ghost blog and there are a couple of odd behaviors
URL: https : //prusik.io/jubbaonjeans/
The cover image loads just fine in IE, but refuses to load in Chrome (for Windows and Android) or Firefox. Here's the code from the source:
<header class="main-header " style="background-image: url(/jubbaonjeans/content/images/2015/01/CoverForBlog-7.jpg)">
In addition, I have a script for Disqus comments. Similar behavior where it works in IE, but not Chrome or Firefox
URL: https://prusik.io/jubbaonjeans/mnrega-and-welfare/
I am using the instructions here (https :// help.disqus.com/customer/portal/articles/1454924-ghost-installation-instructions) to enable Disqus on my blog. (odd URL as I am only allowed 2 links in this post)
Finally, the Ghost image uploader (For cover image and post images) throws a weird error. I am still able to upload images, but the error remains. Again, works just fine in IE
Error: https://prusik.io/jubbaonjeans/content/images/2015/01/UploaderIssue.JPG
Also, I was a programmer at one point and now into InfoSec. My knowledge of CSS and HTML5 programming is basic.
Thanks in advance!
I have a large webproject that in IE9 doesnt display some of the pages elements since the browser deems them "unsecure" in some way. We can ask our users to enable "display mixed content" in IE9 but would of course prefer to solve this on the server side.
Ive used firebug to track the webtraffic and cant see any http:// requests beeing made via the net-tab. I thought this was what caused the error. Is there any other possible way to troubleshoot this.. I just dont know what elements or settings could cause this problem (since all our traffic seems to go through https it has to be something else IE is reacting to?).
Weve done some more searching and the error occured because document.write isnt allowed to print at all to our page in IE9. Its perceived as insecure.
My website is accessible without www in the front of it in Firefox and Safari however for some reason it is not in Chrome. Is there anything that I need to change on my website host or in the html to make it accessible?
If your website is not already set up to do so, you'll need to update your web host to respect requests for http://your-website.com as well as http://www.your-website.com.
Firefox (and apparently Safari) will make a second request to a URL using or removing the www. in front of it if they receive a 404 error before displaying any resulting errors to the user. (And if the alternate URL works they will display the results of the second request and silently drop the results of the first [the 404 error].) Most, if not all other browsers will just display the first 404 error page.
What web server are you running on?
One of my friend's site's users getting this error.
Oops! This link appears to be broken in Google Chrome
http://www.labnol.org/software/webpages-not-opening-in-google-chrome/13041/
Can he do something with their hosting to ensure users of his site will not get this error.
As it is a browser bug, you cannot change this behaviour.
well: as the bug only occurs if prefetching links from your page fails, you could of course remove all 'href' attributes from your html-source and add them on page load using javascript. this would end in chrome not fetching up anything: no fetching => no fetching error. but this 'solution' is not practical.
Are you using redirects? Cause chrome wants a status header with that.