Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

os-crowdsec: LAPI listen address validation broken #4541

Open
3 tasks done
BPplays opened this issue Feb 10, 2025 · 0 comments
Open
3 tasks done

os-crowdsec: LAPI listen address validation broken #4541

BPplays opened this issue Feb 10, 2025 · 0 comments

Comments

@BPplays
Copy link

BPplays commented Feb 10, 2025

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug
using ::1 produces error:
time="2025-02-09T19:58:21-08:00" level=fatal msg="local API server stopped with error: listening on ::1:8080: listen tcp: address ::1:8080: too many colons in address" in /var/log/crowdsec/crowdsec.log

but [::1] says Text does not validate.

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)

To Reproduce
Steps to reproduce the behavior:

  1. go to services > crowdsec > settings > settings > LAPI listen address
  2. set to ::1 or [::1]

Expected behavior
::1 shouldn't validate, and [::1] should assuming it would work. or ::1 should be translated to [::1] for crowdsec but stay the same in the ui

Environment
OPNsense 25.1 (amd64).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant