Website is not loading in chrome and firefox - php

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.

Related

Symfony local web server with domain proxy inconsistent behavior

I cannot seem to get consistent results with the Symfony local webserver using custom domains.
I initially set the proxy up according to the documentation here and it initially worked quite well. However on subsequent returns to working on the project it will most of the time fail to work, and I cannot seem to find the right sequence of steps to take in order to make the local server work with the proxy domains.
I understand that others have had issues with Chrome proxy settings and I've followed the steps to omit that to no avail.
I am running Symfony 5.3.7 for this project, locally on MacOS Big Sur 11.6. This morning returning to the project I have tried the following to no avail...
Stop and restart the proxy symfony proxy:stop & symfony proxy:start
Stop and restart the local server: symfony server:stop & symfony server:start -d
Flush the MacOS DNS cache
Clear the Chrome DNS cache
Remove bad proxies from Chrome
Reapply proxy settings in Chrome
Verified that the proxy PAC file is in place in the networks settings
Verified that automatic proxy configuration is checked in the network settings
Cleared all browsing data in Chrome
Restarted Chrome
I have tried various combinations of all these steps.
I've removed and reattached the proxy domains with the Symfony CLI.
I've tried other browsers including Safari and Firefox.
When I start the server, I can see that the domains are attached, or when I navigate to http://localhost:7080 I can see they are attached and 'running'.
When I visit the local domains I get the following error:
This site can’t be reached
Check if there is a typo in (domain).wip.
DNS_PROBE_FINISHED_NXDOMAIN
The only way I can visit the local site is thru the local host IP and the port that is assigned when I start the Symfony Server.
Try to open your website in incognito mode (so that all plugins get disabled). For me, I had a plugin for TunnelBear VPN. After I disabled the plugin, it started to work.

HTTP 404 Error on certain directories when addressing Server Hostname with Chrome and Explorer (PHP on IIS)

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.

Laravel project installed with laragon is forcing https in google chrome

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.

Cakephp and iOS 10.3.2

Since the new iOS update (10.3.2), we can't reach our website from an Apple device. Safari, Chrome or Firefox are returning a blank page or an error page saying there's a network problem.
We've tried from different places, different kind of iphones, on wifi or cell connection (3G,4G)
On mine it was working well, so I updated it to the 10.3.2 version, and I'm having the same error.
I tried contacting my web host but they told me they couldn't do anything. I tried to install Cakephp in a subdirectory, but even with a fresh install and an empty cakephp (2.9.8), it doesn't work.
I tried the same thing with a Cakephp 3 installation, and it works.
I tried installing Cakephp 2.9.8 on another web hosting (a personal one from the same web host) and .. it works.
So I'm getting a little confused as it seems to be an issue with :
iOS 10.3.2
Cakephp 2.9.2 to 2.9.8
my web hosting
Does anybody can give me any direction to look up ? I'm starting to be really depressed here ...
I found a temporary solution by changing my web hosting configuration.
My web host (OVH, French host) allows to use PHP-FPM (which is a PHP FastCGI implementation) to enhance the website performance.
When I disabled it yesterday, my website was available for iOS 10.3.2 users ! I don't know why, but for now I'm relieved.
I've just asked OVH if they have any idea why, but I'm not really optimistic about their reply ...

Bizarre timeout in Web CMS, ideas?

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?

Categories