search

typicode / hotel

🏩 A simple process manager for developers. Start apps from your browser and access them using local domains
MIT License
9.98k stars 424 forks source link

hotel.localhost no longer works with Chrome & Chromium latest version on Ubuntu #294

Closed zimgodo closed 5 years ago

zimgodo commented 6 years ago

Hi,

Today after I've updated my Chrome and Chromium browser to the latest stable version, visiting hotel.localhost (including https) gives me the error

ERR_CONNECTION_REFUSED

Only works when I visited via http(s)://localhost:2000

Checking the chrome proxy chrome://net-internals/#proxy shows:

Use DIRECT connections.
Source: SYSTEM FAILED

Firefox and all other browsers works when I visited https://hotel.localhost and http://hotel.localhost

I've also tried removing all extensions, still no dice.

Both Chrome and Chromium browser on same version: Version 65.0.3325.181 (Official Build) (64-bit)

Let me know if you need more info from me regarding this issue.

Thanks

zimgodo commented 6 years ago

Additional info: Using Chrome/Chromium on Ubuntu 17.10

rolfkleef commented 6 years ago

Same for me with Chrome 66.0.3359.170 (Official Build) (64-bit) on Ubuntu 16.04

typicode commented 6 years ago

Hi @subdroid,

Hmm I can't reproduce, but I'm on Ubuntu 18.10 and Chromium Version 66.0.3359.181 (Official Build) (64-bit) with system proxy

wizbit commented 5 years ago

Chrome 71 on Windows 10 shows this behavior, Chrome 70 was fine.

townsymush commented 5 years ago

Chrome 71 is showing this behaviour on both Ubuntu 18.04 and Windows 10

wizbit commented 5 years ago

If you change the port in conf.json from 2000 to 80, it work in Chrome 71 Windows 10

townsymush commented 5 years ago

Great thanks

rtablada commented 5 years ago

This is happening in Chrome 71 for Mac OS as well.

Changing to port 80 doesn't work since other services are already running in Mac OS.

djeglin commented 5 years ago

Chrome now forces all requests to *.localhost to the loopback ip, apparently, completely ignoring any other interface or configuration, which makes this unusable. I might be tempted to use "localmachine" instead

zimgodo commented 5 years ago

Chrome now forces all requests to *.localhost to the loopback ip, apparently, completely ignoring any other interface or configuration, which makes this unusable. I might be tempted to use "localmachine" instead

Yup, .localmachine works for me as well. I think I will use it as replacement to .localhost

j-f1 commented 5 years ago

IMO this should just use *.hotel.xyz and have @typicode own hotel.xyz.

j-f1 commented 5 years ago

hotel.tw is also available. Anything with a 3 letter TLD is the same length as .localhost.

zimgodo commented 5 years ago

hotel.tw is also available. Anything with a 3 letter TLD is the same length as .localhost.

.tw is reserved tld for Taiwan https://en.wikipedia.org/wiki/.tw

IMO this should just use *.hotel.xyz and have @typicode own hotel.xyz.

same goes to .xyz e.g https://gen.xyz/

I retract my previous comments as I didn't realize what you were actually meant to say, my apologies.

Although both domains are available, but something tells me we shouldn't.