ng serve --disable-host-check no longer works

[buu700]

Versions

CLI: 1.6.7
node: 8.9.4
npm: 5.6.0
typescript: 2.6.2
OS: Debian 9.3

Repro steps

• ng serve --host '0.0.0.0' --port 42002 --public-host 'localhost:42002' --disable-host-check
• Open http://HostnameOfServer:42002 on a different device

Observed behavior

Request host is not whitelist enabled for this server. Please use the --host command-line flag to whitelist a specific host (recommended) or use --enable_host_checking to disable host checking. See the command-line flags help text for more information.

Desired behavior

Site should load successfully.

Mention any other details that might be useful (optional)

This used to work, but I'm not sure of the version at which it stopped working.

--host '0.0.0.0' is needed while running the CLI in Docker because otherwise it dies with:

getaddrinfo ENOTFOUND '0.0.0.0'
Error: getaddrinfo ENOTFOUND '0.0.0.0'
    at errnoException (dns.js:50:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

[clydin]

Can you provide the source of the quoted error message?

--enable_host_checking is an option for the AppEngine dev server not the Angular CLI.

[buu700]

Hmm, that's interesting. I thought it was odd that an Angular CLI error message would cite a command line flag that didn't actually exist.

I am running the App Engine dev server, but at a different port, and I just confirmed in my browser history that I was hitting the correct port when I saw this error message. Not really sure what's going on here, but I'll investigate later this week and try to isolate the source of the message.

[buu700]

We ran into this again and confirmed that it was from App Engine this time, so it was probably user error when I initially reported this. I'll reopen if it happens again and I confirm that it's coming from Angular.

[MichaRedM]

using double quotemarks worked for me:
--host "0.0.0.0"

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}