My localwp was working great (both in Edge browser and Chrome browser) with several websites installed. Updating to the latest version has stopped all websites from working in Edge browser.
When I try to load any of them, Edge browser returns the following error message:
Oops… this page cannot be accessed. It seems that the web page at http://tda.local/ might be having issues or has permanently moved to a new web address.
ERR_TUNNEL_CONNECTION_FAILED
To load websites I have to copy and paste the URL into Chrome, but that is a pain and slows down my productivity. How can I fix Edge?
Yes, I have tried a complete shutdown of the machine. And I am not using VPN.
In the following image you can see, on Bing on the left, and on Chrome on the right.
Before the last update, localwp worked perfectly on both.
All that was done, my friend. Anyway, Now I did it again (just in case) but, definitely, updating the app was screwed up when updating. In Edge it stopped working. In Chrome, some websites work normally, others work slowly, and others don’t work at all (neither in Edge nor in Chrome). A complete disaster.
Yes, MS Edge is my default browser. When any application “bounces” a browser, it is always Edge. As you can see, none of the extensions of that browser are for firewall or antivirus.
For pages that LocalWP tries to open in Edge, I get this message:
Oops… this page cannot be accessedIt seems that the web page at http://test1.local/ might be having issues or has been permanently moved to a new web address.
ERR_TUNNEL_CONNECTION_FAILED
As I’ve said in previous posts, Chrome and Opera don’t get this error.
You could try checking your proxy settings. Open Edge Settings > System and Performance > Open your computer’s proxy settings and ensure that the proxy settings match those in Chrome/Opera or disable any proxies if you’re not using one.
Otherwise you might have to try checking your network, hosts file etc. See if you can spot anything that’s different between the three browsers. This isn’t a widespread issue so it seems to be something local to your machine, but it’s tough for us to say what. For now you may just have to rely on the other browsers if you’re unable to narrow down a culprit.
I can follow your advice and ignore my Edge browser, and continue using Chrome. But I’m worried that, just as a LocalWP update sent its compatibility with my Edge to hell, a new update will do the same with Chrome, and I’ll lose access to the websites I installed there for testing and research.
We’ve done some testing but aren’t able to replicate the issue in Edge, and we don’t have any widespread issues noted with Edge or Chrome so it seems like something specific within your machine but I’m not sure what else to try as far as troubleshooting goes.
If Local was working for you previously you could try downgrading to an older version and see if that helps:
If you create a new, blank site in Local and try to open that in the browser do you get the same type of issues? Or is it only for sites you’ve already been working with previously?
As a test you might try reimporting one of your sites, and then see if that has any change on the problems you’ve been seeing:
The steps would look like this:
Locate the site files on your machine, and save a copy of them to your desktop. If you click Go to Site Folder under your site name it should take you right to where they are located.
Once you have those copied, completely delete the site from Local
It looks like you’re currently using Site Domains as your Router Mode, which supports HTTPS, but in your initial screenshot, your site isn’t secure. Can you try trusting your SSL in Local?
If that doesn’t work if you change your Router Mode to Localhost, will the site load in Edge then? (Preferences>Advanced>Router Mode)
