I have a dev site that I started up using the php live server and using localhost:8000. The issue I'm having is that neither Chrome, Firefox, or Safari are able to establish a secure connection because the protocol gets reverted to HTTPS, thus rendering my site useless. I'm fully aware of the new implementations that chrome and other browsers are placing on .dev sites, but I don't think that applies to my issue, especially since the dev site doesn't use that domain. Also, I've been to chrome://net-internals/#hsts and tried deleting any security constraints on localhost, but that didn't work either. What am I missing here?
I think this post can help you: Google Chrome .dev not work over http.
So in according to this post you must only change your .dev local domain following this memorandum from Network Working Group(NWG).
Related
I have a problem accessing certain directories of my website (they get corrupted in the URL), but only with certain browsers and only addressing the server hostname instead of 'localhost'.
I have a PHP web application running on IIS Server. I tested the app on four Browsers: Firefox, Edge, Chrome and Internet Explorer.
When I use 'localhost' to address the website, everything works fine on all four browsers. But when I address the server hostname then it works only with Firefox and Microsoft Edge.
Using Internet Explorer or Chrome, addressing the hostname, I get either the correct page but with unproper CSS, or 404 error messages, or ERR_CONNECTION_RESET messages. In the newly loaded URLs I can see that the browsers are loading the wrong directories.
I am using the IIS Rewrite Module to rewrite the visible directories. But since everything works fine as long as I address 'localhost' and also, with these browsers addressing the hostname, the same problem appears using the original directories, I guess the problem lies somewhere else.
Inside the application I am using includes with relative paths. It seems as if these are combined in different ways by the different browsers. Am I now forced to use absolute paths throughout the entire application? Or can this problem be solved some other way?
Thanks a lot for your help!
Ok, it turned out that it was several different problems that just all appeared in one specific situation:
I cannot reproduce the 404 errors any more. Possibly they were caused by cached info and/or cookies that I have deleted in the meantime.
IE does now load all pages and just has trouble loading parts of the CSS. As I read, this can be caused by several other reasons that I am getting into now.
Chrome simply blocked the website because of certificate issues (they caused the ERR_CONNECTION_RESET message). Without them, Chrome is working completely smooth now.
So, fortunately it turned out that the relative paths used in the php code didn't have anything to do with the problem.
I have a laravel project which is installed with laragon and I was working for few days nicely. Now after a sudden stop of my pc (because of electricity unavailability) I can no longer access the local site in chrome and it is forcing me to an https location. I then opened the site in mozila and it's working there perfectly.
Here what chrome shows as error
This site can’t provide a secure connection
school.dev sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
What could be the reason and the solution for it?
Thanks in advance.
It has nothing to do with Laravel and everything to do with Chrome. They recently put a release that forces .dev, .app, and a few other TLDs to use HTTPS. The best fix is to use .local instead of another TLD.
src: Chromium transport_security_state_static.json changelog
I face similar issue yesterday, it took me lots of time to actually understand this issue but not to waste much of time, i decided to switch to other browser like Mozilla Firefox and use http instead of https to continue my work.
My magento website is not loading in chrome and firefox.It works fine in IE only. I cleared the chrome cache and history but it not display my website it shows like "This webpage is not available ERR_SSL_VERSION_OR_CIPHER_MISMATCH ". How to solve this error i am working on this issue for last 2 days.
That's nothing to do with your website as such, that's a server configuration issue.
Most likely your server is still trying to serve https requests using SSL3, which has been removed in Chrome 40 (and I guess firefox as well, but I don't have the changelogs to hand to check)
This is a good tool to check your SSL settings:
https://www.ssllabs.com/ssltest/
This will confirm any issues, and advise on fixes.
If you don't have full server access, then you'll need to speak to your host.
I have a web app that uses PHP session cookies. I have this app running on a cloud LAMP server and on my desktop with MAMP. I'm providing access to this app via an iframe on another website with a different domain. The app works fine on FF and Safari, but I'm getting an issue on chrome. If I set the iframe to point to my local MAMP environment, the iframe receives "cookie" in http request header, and works fine, but if I set it to my prod server, the request header is missing "cookie." Please help me fix this.
When you are running it from your production server you have a 3rd party cookie and I'm guessing you would have the same issue on IE.
You need a P3P policy in place:
http://www.w3.org/P3P/usep3p.html
Google found a way to cheat so check this out, it may help:
http://blogs.msdn.com/b/ie/archive/2012/02/20/google-bypassing-user-privacy-settings.aspx
I know this kind of thing cannot be adequately answered without a link to the live example. Unfortunately, I can't set one up right now as it's a back-end login and creating a safe public login would be too much to do at this point. Sorry. I'm hoping for ideas and input from people who may have experienced something similar in the past.
I am setting up a CMS for a client with a DSL connection in Spain.
The CMS is hosted on a straightforward standard, LAMP based, shared hosting package in a network center in Germany.
It comes with a .com domain.
When my client tries to log in to the CMS using Internet Explorer 7, everything works fine.
When she tries to log in using Firefox, she gets to the login form, submits it - and then the connection times out.
When she logs in using Firefox but using "domain.com" instead of "www.domain.com", everything works fine.
This happens on all computers that are hooked up to that line. One Windows XP, one Windows Vista.
The front-end part of the site, as well as a second, older CMS, work fine in all browsers.
I do not have access to the raw access logs.
I have not been able to reproduce this behaviour on any other connection.
Debugging ideas are welcome. Remote diagnosis is extremely difficult as the line is too slow to set up a proper remote connection.
If you are limited by how you can troubleshoot this, have the client install Fiddler - Web debugging proxy and then run the trace, and send you the logs, Fiddler will analyze the traffic (be it proxy or DNS timeout, etc)
Take a look if you have not used it before:
http://www.fiddler2.com/Fiddler2/version.asp
Check that Firefox and IE are using the same proxy settings.
DNS issues? can you put here your A records to check is everything is ok?