I don’t think there is anything wrong. 0.0.0.0 and localhost are functionally equivalent here (they both resolve to the same place unless you’re using a container of some kind). The url formatter just prefers localhost because there are less issues with it across different environments.
This is the formatter:
Would it be better if it said something like internal: https://localhost:3000 (0.0.0.0, ssl enabled)?
Thanks for pointing out the issue with the docs. I updated them to reflect the actual available options.
Just to be clear – your dev server is still working – the concern is just that the dashboard says https://localhost:3000 instead of https://0.0.0.0:3000?
If 0.0.0.0 is secure but localhost isn’t, I’d recommend generating the certificate with an actual hostname (this is a good idea, generally). At the very least, specify all the interfaces the site might be resolved from:
Just in case, I have generated a new certificate, but the old one was also valid for both domains localhost and 0.0.0.0.
$ mkcert nomanisanisland.test localhost 0.0.0.0 ::1
Note: the local CA is not installed in the Firefox trust store.
Run "mkcert -install" for certificates to be trusted automatically ⚠️
Created a new certificate valid for the following names 📜
- "nomanisanisland.test"
- "localhost"
- "0.0.0.0"
- "::1"
The certificate is at "./nomanisanisland.test+3.pem" and the key at "./nomanisanisland.test+3-key.pem" ✅
ℹ server
╷
├─ internal: https://localhost:3000 (https://localhost:3000)
├─ external: https://192.168.1.128:3000 (https://192.168.1.128:3000)
… watching project sources (and 55 other files)
EDIT: Note that there is no proxy like this:
ℹ server
╷
├─ proxying: https://nomanisanisland.test (https://nomanisanisland.test)
I tried to replace
.proxy('https://nomanisanisland.test')
with
.proxy(new URL('https://nomanisanisland.test'))
Then, when I try to acces to https://localhost:3000 or https://0.0.0.0:3000 with browser, it keep waiting until timeout.
ERR_EMPTY_RESPONSE
It’s not a problem with certificates, because that kind of problem is reported in the browser and I can access with no problems to https://nomanisanisland.test. It has to be something else.