I tried to follow the instructions to enable twitter notifications but when I get to the point of allowing Sonarr access to my twitter app, it goes to a 404 page. The instructions say that the callback address doesn’t need to exist but it just needs to be set.
So I made a twitter app, put in my client token and client secret token, but when I click Connect To Twitter it opens a tab to authorize the app. Then it goes to 404 and never authorizes the app.
Am I doing something wrong? Well obviously I am but dont know what it is.
I had the callback URL set to mydomain/twitter. That is not actually a site I serve but even when I set it to an actually available site it did the same thing…What should I set it to? I will post a debug log here shortly
Yes I did. When I get to the next screen and click “Authorize App” inside the twitter page that sonarr takes me to, is when I get the 404 error. You should try it. Its the Oauth part that isn’t working right. http://imgur.com/raI5YiX
I am getting the 404 on what I assume is the callbackURL. The page after I click on Authorize App. I am not sure what is going on. It’s almost like it’s not saving the tokens when I send it. So it is requesting access or something with no tokens.
I don’t know. May try something else.
Should I be using the client token and client secret? Or the other one that I had to create? Inside the twitter app dev I’m talking about.
Just so I can make sure I am doing it right. Make the Twitter app, using the connect feature of Sonarr, add Twitter as a notification option, fill in the name of the connection, consumer key and consumer secret key, the mention field, and whether or not I want it to be a DM or a public tweet. After it is all filled out I click on Connect to Twitter.
The new tab opens up to my app in twitter and I click on authorize app. After this point is where I get the 404. No matter what callbackURL I put in.
Did I miss anything? I think I am going to delete my app on twitter and try and make another one. Thanks for your help.
This is the same error that keeps coming up everytime I try to do what I outlined above. Those fields are def not empty.
Invalid request Validation failed:
– ‘Consumer Key’ should not be empty.
– ‘Consumer Secret’ should not be empty.
Yes I use a url base for Sonarr with nginx. mydomain/sonarr is my URL base. Ill have to look into this some more.
I think I am going to give up, for now. If I go to mydomain/sonarr/oauth.html it works and I get the “shouldnt see this” screen.
I was just trying to work something out between IFTTT and twitter but I may have to go another route.
Thanks again for trying.
This is my current info. I installed the new update from the develop branch. It looks like it is still trying to use mydomain/oauth.html At least that is what the url is after I click authorize app on Twitter.
Well I got it to work by setting the callbackURL to mydomain.com/sonarr/oauth.html and locking the callbackURL inside of my Twitter app settings.
