-
Notifications
You must be signed in to change notification settings - Fork 92
Unable to authorize during set-up #62
Comments
I have exactly the same problem, unable to set up tweetnest because it doesn't want to sign in with twitter... There is nothing in the logs (either Apache nor in the debug comments in the HTML source) and seemingly nowhere else to look for errors... |
What do you have in your
If Tweet Nest is authorised on your Twitter account, you should be able to visit Twitter Developers and when you view your application's details you should be able to see the four random values mentioned above. |
Well there is nothing in I'm sure if I edited As told before, there is no available information in the logs about this. Moreover I didn't see any tentative from the app to contact Twitter before returning the error (checked with Somehow we reach this line https://github.com/graulund/tweetnest/blob/master/setup.php#L172 without actually trying to contact Twitter... Here some additional information: I am trying to install the app behind a SSL VirtualHost. PHP Version 5.4.4-14+deb7u5 Excerpt from |
Some more hints: Adding
Adding
What's striking me here is the absence of a variable This would explain quite a lot here... |
I believe this has to do with this line: https://github.com/graulund/tweetnest/blame/master/setup.php#L671
Even if the name of this input is It's just a guess... |
Using Firefox I've had this problem, too, but in Chromium I was able to complete the setup without errors. |
Fix issue #62 fix Twitter auth during setup for Firefox
(I'm sorry I can't say more about the problem I've got, but I don't really know what's going on.)
Every time I try click the 'sign in with twitter' button (after the other fields have been filled in of course), I get the message "You must authorize Tweet Nest to use your Twitter account before continuing." But I've already done that (and Tweet Nest appears in the list of authorized applications in Twitter).
Any ideas on what I should be looking for to fix this?
Thanks!
The text was updated successfully, but these errors were encountered: