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
I have searched the existing issues, open and closed, and I'm convinced that mine is new.
The title contains the plugin to which this issue belongs
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
go to services > crowdsec > settings > settings > LAPI listen address
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).
The text was updated successfully, but these errors were encountered:
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
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 uiEnvironment
OPNsense 25.1 (amd64).
The text was updated successfully, but these errors were encountered: