We got here a couple of levels of cache to check then. This should solve the problem for some users, but assuming up to now you still have not yet solved the problem, we can test out what could it be. Somehow pressing Enter like crazy won't do. They both point to the same place and the So it would look like this: 127.0.0.1 localhostġ27.0.0.1 OR just the same 127.0.0.1 localhost NOTE: Remember that you HAVE TO press F5 to refresh the site/Firefox tab or close the tab and open it again to test. In the case of Firefox and resolving the name, Firefox adds the the prefix but on Chrome it looks like this "". This means it is a cache problem or a problem resolving the correct name. But then you went with Firefox, it might have worked the first time, but after changing hosts file back and forth it somehow stop working. You changed /etc/hosts between having and not having the entry for and it worked every time you changed it. In this case it should respond with 127.0.0.1. Type ping and it should respond from the IP assign to it. You first test this out to see if it is working correctly from the terminal.
gksu which provides gksudo is discontinued in the official 18.04 and later repositories.)
Gedit - gksudo gedit /etc/hosts (You now have a GUI friendly way of editing the file.Assuming you already edited /etc/hosts file to which I recommend the following 2 ways to edit the file: Follow this steps to have this working correctly. This is an answer for users that are affected by the same problem and if they are affected by both/all browsers. I can confirm your problem that it appears to affect, between both, Chrome and Firefox, only Firefox.
0 kommentar(er)
