This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

Birdy (OAuth, Twitter, Tweets&MegaHAL v6.01d) Jun12,2013

Support & discussion of released scripts, and announcements of new releases.
Post Reply
d
daigo
Voice
Posts: 37
Joined: Fri Jun 27, 2014 8:02 pm

Post by daigo »

Also getting this error:

Code: Select all

09:44:05 <@daigo> !tweet test
09:44:07 < daigobot>  You are not able to tweet in #daigo. You must have (n|n flags), or be (op voice) in #daigo. Both of which you aren't. :P
Here is my script setting:

Code: Select all

set twitter(flags) "n|n"
And my eggdrop flags:

Code: Select all

[09:44:54] #daigo# (#daigo) chattr daigo
Global flags for daigo are now +ghjlmnoptvx.
Channel flags for daigo on #daigo are now +glmnov.
I even tried setting: set twitter(flags) "-|-"
But I still get the same error.
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

OAUTH errors since Twitter disabled SSL 3.0

Post by Nocty »

I seem to be getting an oauth error that started around when Twitter disabled SSL 3.0 due to the POODLE vulnerability.

Anyone else getting OAUTH Errors starting around 6-7PM CST starting OCT-14-2014?
S
SignZ
Voice
Posts: 18
Joined: Thu Jun 17, 2010 3:52 pm

Re: OAUTH errors since Twitter disabled SSL 3.0

Post by SignZ »

Nocty wrote:I seem to be getting an oauth error that started around when Twitter disabled SSL 3.0 due to the POODLE vulnerability.

Anyone else getting OAUTH Errors starting around 6-7PM CST starting OCT-14-2014?
Yup, been getting
OAuth failed: (???) error reading "sock10": software caused connection abort ( internal error )
since last night. Strangely, it sometimes is sock9, then sock10 and began at 1:15am CEST (Berlin time) with sock7.
At first I thought it's either me or the host but it looks like it's something else. :/
User avatar
NewzNZ
Halfop
Posts: 68
Joined: Thu Mar 05, 2009 5:15 am
Contact:

Post by NewzNZ »

I've been getting this error for about the last 48 hrs:
OAuth failed: (???) Unknown problem... No reason given...( ok )
S
SignZ
Voice
Posts: 18
Joined: Thu Jun 17, 2010 3:52 pm

Post by SignZ »

NewzNZ wrote:I've been getting this error for about the last 48 hrs:
OAuth failed: (???) Unknown problem... No reason given...( ok )
heh, I've seen that one in my logs for months now.
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

OAUTH errors since Twitter disabled SSL 3.0

Post by Nocty »

Is anyone not getting these errors currently?
j
johne
Voice
Posts: 29
Joined: Tue Jul 19, 2005 2:24 am

Post by johne »

per speechles himself

in twitter.tcl on mine
::http::register https 443 [list ::tls::socket -request 1 -require 0]
change that to
::http::register https 443 [list ::tls::socket -tls1 1]
make sure twitter.tcl is the last script sourced
otherwise it might break the http::register if another script does that last

I can confirm that this fixes the issue.
S
SignZ
Voice
Posts: 18
Joined: Thu Jun 17, 2010 3:52 pm

Post by SignZ »

johne wrote:per speechles himself

in twitter.tcl on mine
::http::register https 443 [list ::tls::socket -request 1 -require 0]
change that to
::http::register https 443 [list ::tls::socket -tls1 1]
make sure twitter.tcl is the last script sourced
otherwise it might break the http::register if another script does that last

I can confirm that this fixes the issue.
Sweet, thank you very much (also thank you, speechy!). :D
I also can confirm this works.
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

Works

Post by Nocty »

Thanks for the quick response! Confirmed working.
User avatar
NewzNZ
Halfop
Posts: 68
Joined: Thu Mar 05, 2009 5:15 am
Contact:

Post by NewzNZ »

Working here also - thanks guys!
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

May have spoken too soon

Post by Nocty »

That fix seemed to work for a while, but within 24 hours the errors return until I restart the bot. Anyone else?
User avatar
NewzNZ
Halfop
Posts: 68
Joined: Thu Mar 05, 2009 5:15 am
Contact:

Post by NewzNZ »

That fix seemed to work for a while, but within 24 hours the errors return until I restart the bot. Anyone else?
still working here...though I had restarted the bot directly after adding the fix for other reasons.
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

Still having trouble

Post by Nocty »

make sure twitter.tcl is the last script sourced
otherwise it might break the http::register if another script does that last
If I have another script that uses http::register, do I need to change anything in that? I'm still getting errors having changed the lines noted.
s
shadrach
Halfop
Posts: 74
Joined: Fri Dec 14, 2007 6:29 pm

Post by shadrach »

I have two eggdrops (1.8 ) both loaded with twitter script and they functioned fine before the ssl issue. I made the alteration in the code as advised and one works correctly again while the other exhibited this habit of needing to be rehashed to gain functionality again. Inspecting the config I noticed that http.tcl had been sourced twice by mistake. On removing the duplicate and ensuring the titter.tcl was sourced last and http.tcl first the problem seems to have been resolved. So check your config again and maybe remove any recently added tcls which might possibly be conflicting.
N
Nocty
Voice
Posts: 15
Joined: Tue Jun 17, 2014 3:18 pm

Troubleshooting

Post by Nocty »

On removing the duplicate and ensuring the titter.tcl was sourced last and http.tcl first the problem seems to have been resolved. So check your config again and maybe remove any recently added tcls which might possibly be conflicting.
I am not sourcing http.tcl directly in my bot configs; as far as I know this is correct practice, can anyone confirm?
Post Reply