You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I’d like to ask whether it’s really necessary to enforce the new check introduced in version 4.0.9, which causes Dkron to fail startup with the following message:
Error: failed to parse advertise address (, 127.0.0.1:8946, 8946, false): defaulting advertise to localhost is unsafe, please set advertise manually
From my perspective, this behavior is too strict. I don’t think binding to localhost should be treated as unsafe — especially for a standalone setup, where listening on localhost is actually the desired and secure configuration.
This mainly causes issues on Debian/Ubuntu installations from the repository, where Dkron runs as a systemd service and defaults to a localhost bind. If I want Dkron to listen only on localhost, I must now modify the systemd unit file to bypass this check, which complicates otherwise simple deployments.
Would it be possible to either:
downgrade this message from error to a warning, or
remove the restriction entirely?
That would make local and single-node deployments work again without manual systemd modifications.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I’d like to ask whether it’s really necessary to enforce the new check introduced in version 4.0.9, which causes Dkron to fail startup with the following message:
From my perspective, this behavior is too strict. I don’t think binding to localhost should be treated as unsafe — especially for a standalone setup, where listening on localhost is actually the desired and secure configuration.
This mainly causes issues on Debian/Ubuntu installations from the repository, where Dkron runs as a systemd service and defaults to a localhost bind. If I want Dkron to listen only on localhost, I must now modify the systemd unit file to bypass this check, which complicates otherwise simple deployments.
Would it be possible to either:
That would make local and single-node deployments work again without manual systemd modifications.
Thank you!
To Reproduce
Steps to reproduce the behavior:
All reactions