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
Describe the bug
I have the indexer and IRC set up properly for SpeedApp. IRC is showing healthy and showing messages. However the 'last announce' always says N/A and none of the releases show up in the releases page. I also have a filter with this indexer enabled. In the logs, nothing shows up for this indexer except the IRC successful joining and monitoring messages.
To Reproduce
Steps to reproduce the behavior:
Add new indexer for SpeedApp.
Add relevant details such as passkey etc.
Login to IRC and register nick.
Add details to IRC section of autobrr.
Create new filter with test action.
Monitor releases and logs.
Expected behavior
Announcements from SpeedApp IRC show up in releases and get filtered.
Screenshots
Desktop (please complete the following information):
OS: Windows 11
Browser Firefox
Version 122
The text was updated successfully, but these errors were encountered:
Hi there. This isn't technically a bug. If you look at the announcer name it has a 9 at the end. Autobrr looks for messages from speedapp-announcer, not speedapp-announcer9. This happens because they're failing to identify their bot with nickserv.
We're in the process of possibly making a solution for that on our end, but for now I'd tell their staff to fix it on their end.
Version
1.36.0
Describe the bug
I have the indexer and IRC set up properly for SpeedApp. IRC is showing healthy and showing messages. However the 'last announce' always says N/A and none of the releases show up in the releases page. I also have a filter with this indexer enabled. In the logs, nothing shows up for this indexer except the IRC successful joining and monitoring messages.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Announcements from SpeedApp IRC show up in releases and get filtered.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: