in the last days chrome and edge stopped working to access localhost domains o my windows machine. Firefox is still able to, so I guess it has something to do the browser engine.
My setup: I have a vm started with vagrant on hyper-v. Inside the vm is my apache webserver.
On my windows 11 operating system the hosts file points my local development websites to the ip of the vm. This was working for the last years without any problem.
DNS over https is not enable in Edge or Chrome.
I already have tried using different local domains like localhost or .local. without success
I have tried ipconfig /flushdns without success
I reinstalled Chrome without success
My host file is
172.28.148.95 workspace.localhost.de
127.0.0.1 workspace.localhost.de
What can I do, that Edge and Chrome can access local domains?
Related
In the past, It was always enough for me to start local development server on address localhost, running on port 8008 - Therefore in browser I could access my development server just by entering localhost:8008 into browser's address bar.
My Goal
I must start my local dev server under the address mysite, port 8008. No exceptions.
What I Tried
In order to do this, I added mysite into my /etc/host file like follows:
127.0.0.1 localhost mysite
Problem
Upon entering mysite:8008 into address bar of every browser I tried (Safari, Firefox) was my dev site is correctly displayed. However I cant get it work on Google Chrome. This is what Google Chrome displays upon entering mysite:8008 into address bar:
This site can’t be reached mysite refused to connect.
Search Google for mysite 8000
ERR_CONNECTION_REFUSED
However localhost:8008 works displays my website correctly. Any ideas?
It is totally wierd, but for some mysterious reason it looks like Chrome cares for ordering in the /etc/hosts file. Problem has been solved by switching order in localhost line of /etc/hosts file to following:
127.0.0.1 mysite localhost
As the title states, my iMac won't allow mobile devices to connect to the web server. I can access localhost via
localhost
192.168.1.187:1717
These both work on my iMac and also my MacBook however the funny/weird issue is that the mobile device won't load it. I mean the files are hosted on the iMac and are accessible completely (both on localhost and the IP address) and the site also works on my MacBook (On the IP address) however my mobile device won't load it. Why?
I've disabled my firewall, changed ports through XAMPP and messed around with Apache Config but no to avail.
(This is definitely not a duplicate as EVERY question I've read the IP address doesn't work on the local machine but for me it does)
For a while I have been running two different server environments on my Windows 7 OS. IIS runs on 127.0.0.1 and I have a Vagrant VM that uses 192.168.33.10. My hosts file looks something like:
vagrantsite1.localhost 192.168.33.10
vagrantsite2.localhost 192.168.33.10
iissite1.localhost 127.0.0.1
iissite2.localhost 127.0.0.1
Up until a week or so back, this setup worked perfectly fine, however something has changed recently with my Chrome browser. Now all of a sudden in Chrome when I access vagrantsite1.localhost it is referencing the IIS 127.0.0.1 IP address instead of 192.168.33.10. I checked this using chrome://net-internals/#dns and even cleared the host cache, which did not seem to resolve anything.
After some research I have found if I add localhost 192.168.33.10 to my hosts file, the vagrant sites work, however now my IIS sites try to access this IP instead of 127.0.0.1. It seems that Chrome does not let me use a different IP for somesite.localhost from localhost entry. This is not a problem in IE and Firefox, and up until recently it was not a problem in Chrome.
I was wondering if anyone else has this problem or a potential solution (rather than manually setting localhost IP each time I want to switch servers)? I realize I can use a different port number for one of the servers as a solution, however since everything works fine in IE and Firefox, and until recently worked fine in Chrome, I would like to know the cause.
This is a "feature" that was just added to chrome, all localhost domains will always resolve to loopback.
See the following links for more information:
https://code.google.com/p/chromium/issues/detail?id=455825
https://codereview.chromium.org/938093003
One workaround is to change your entries to not end in localhost, something like "vagrantsite1.local 192.168.33.10" instead should work.
I develop a few webpages on my local computer. My setup is one virtual server in nginx for each site and then an entry in /etc/hosts for each site pointing an domain name to 127.0.0.1.
However I switched computer to a chromebook and can't keep this way of working anymore.
I use nginx in a crouton created debian chroot and it works fine. However chrome os won't let me edit /etc/hosts. I still reach my nginx with 127.0.0.1 but I can't reach any of my virtual servers anymore.
What's your solution to this problem? (I know that I can force edit /etc/hosts on chrome os if I disable automatic updates, I would wish to avoid this.)
You can try a google chrome extension like this one to override dns settings: https://chrome.google.com/webstore/detail/dns-overrider/acmhaiiijfheggcaanjlgpampclpbnoh/
i have tsung setup in my remote linux server.(54.54.90.90) no browser here.
i have my windows machine (122.122.130.130) where i browse my web app through firefox. i have changed firefox settings to use SOCKS proxy on port 8090 (http://blog.ashurex.com/2012/03/15/creating-ssh-proxy-tunnel-putty/) to route all traffic from my windows laptop to linux box to the internet rather than from windows laptop to internet.
now i started tsung-recorder which runs by default in 8090, hoping whatever requests i make in my windows laptop will be recorded here. but no session is recorded.
I want to record a tsung-recorder session in my linux machine as i browse in my windows laptop. please help.
Just configure an HTTP proxy on Firefox and point it to the remote server where your tsung-recorder ran using port 8090.