Crowdsec Widget

[KonVei82]

Description

Not sure what i am doing wrong but i am getting:
[2024-04-08T21:35:12.898Z] error: Failed to login to Crowdsec API, status: 401
[2024-04-08T21:35:12.899Z] error: undefined

I did copy the credentials from local_api_credentials.yaml, both crowdsec and homepage are running on docker.
cscli machines list does indeed report a "localhost"
My services.yaml looks as following:

widget:
type: crowdsec
url: http://crowdsec:8080/
username: localhost
passowrd: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Any ideas?

homepage version

v0.8.11

Installation method

Docker

Configuration

- Crowdsec:
        icon: si-springsecurity-#5CDD8B
        widget:
          type: crowdsec
          url: http://crowdsec:8080
          username: localhost 
          passowrd: xxxxxxredactedxxxxxx

Container Logs

[2024-04-08T21:52:00.511Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:52:00.512Z] error: undefined

[2024-04-08T21:52:00.522Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:52:00.523Z] error: undefined

[2024-04-08T21:52:06.258Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:52:06.259Z] error: undefined

[2024-04-08T21:52:11.385Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:52:11.386Z] error: undefined

[2024-04-08T21:55:52.703Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:55:52.704Z] error: undefined

[2024-04-08T21:55:52.705Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:55:52.706Z] error: undefined

[2024-04-08T21:55:58.458Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:55:58.459Z] error: undefined

[2024-04-08T21:56:03.466Z] error: Failed to login to Crowdsec API, status: 401

[2024-04-08T21:56:03.466Z] error: undefined

Browser Logs

API Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Troubleshooting

sudo docker exec homepage ping crowdsec
PING crowdsec (172.18.0.8): 56 data bytes
64 bytes from 172.18.0.8: seq=0 ttl=64 time=0.466 ms
64 bytes from 172.18.0.8: seq=1 ttl=64 time=0.204 ms
64 bytes from 172.18.0.8: seq=2 ttl=64 time=0.154 ms

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it appears that there is a typo in your services.yaml configuration for the Crowdsec widget. The field for the password is misspelled as passowrd instead of password. This could be the reason why you are receiving a 401 Unauthorized error, as the incorrect field name would prevent the correct password from being used in the API request.

Please update your services.yaml configuration to correct the spelling of the password field:

widget:
  type: crowdsec
  url: http://crowdsec:8080
  username: localhost
  password: xxxxxxredactedxxxxxx

After making this change, restart your homepage container and check if the issue is resolved. If you continue to experience issues, ensure that the password you are using is indeed correct and that the Crowdsec API is configured to accept connections from your homepage container.

Remember to never share your actual passwords in public forums or support requests.

Let me know if you need further assistance!

This comment was generated by Glime.

[KonVei82]

Damn the AI bot is good :)
There is a typo in the documentation example for the Crowdsec Widget.

widget:
type: crowdsec
url: http://crowdsechostorip:port
username: localhost # machine_id in crowdsec
passowrd: password

I copied it without paying attention.

[shamoon]

Good bot. I’ll fix the docs

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.