yaml config not respecting dns-proxy-port value about cloudflared HOT 8 CLOSED

Just confirmed it, thanks! It seems like the argument parsing library has trouble with unsigned integers. I'll add a workaround for the next release (should come out later today).

from cloudflared.

Can confirm, version 2018.4.3 (Debian package).

from cloudflared.

Any update on this?

I was able to work around it by using the TUNNEL_DNS_PORT environment variable instead of --port but that has, uh, spontaneously stopped working and I can't get it working again short of manually running cloudflared from a terminal.

[EDIT] Carry on, the environment variable not being picked up was launchctl being weird. :) Setting the environment variable does indeed work around the option in the config file being ignored.

from cloudflared.

I'll add a workaround for the next release (should come out later today).

Did you get that release out?

from cloudflared.

Yes, it reads the port from configuration properly.

from cloudflared.

I'm still having this issue as of April 2020.

from cloudflared.

I got the version cloudflared version 2020.3.2 (built 2020-03-31-1706 UTC)
It can works properly now. thx.

from cloudflared.

I can confirm the config DNS settings are working with the yaml config as of the current release of 2020.7.3. Since the original issue is resolved, please open a new issue and we can take a look at that directly. Thanks!

from cloudflared.