-
Notifications
You must be signed in to change notification settings - Fork 7
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
Not Posting to ListenBrainz #194
Comments
Can you search your |
This error keeps popping up. Jan 05, 2023 09:06:15.154 [19592] WARN - [Req#db54da] Webhook: Error delivering payload to https://eavesdrop.fm/?id=TOKEN&user=USERID: 502 |
I'm having the same issue. I just realized that eavesdrop stopped reporting since March 20th of last year. Same message in my logs for every song. |
I've just set up eavesdrop. Nothing is being sent to ListenBrainz from what I can see. I've turned on debugging in Plex, and I can see that it is sending events to the webhook, but nothing is happening from there. |
Just an update, I'm not longer seeing this issue. |
Chiming in here that I've set up the connection today and made sure token, username and webhook (delivery) are all set up. Yet, no activity is being transfered to LB (tested with Plexamp for Windows and directly in browser on Plex so far). Can anybody comment whether it's working at all for them before I dig into debugging? |
@iophobia, I can confirm that it's working as expected for me (and has been for the last 6 months or so that I've been using it). 👍🏻 I use PlexAmp, but it also works from Plex via the browser for me. (Apologies for notifying subscribers to this) |
Oddly enough, I just checked back after your comment with my Plexamp instance and it's working now despite no settings changed. I'll keep an eye out but consider it closed for now on my end. |
Hi. Just noticed today that this stopped listening for my plex plays back in March 2022.
I removed the webhook and started fresh but no luck. I even re generated a token from listenbrainz. Anything I should try differently, I followed each step and did the ones on the FAQ also.
The text was updated successfully, but these errors were encountered: