egghelp.org community Forum Index
[ egghelp.org home | forum home ]		 egghelp.org community
Discussion of eggdrop bots, shell accounts and tcl scripts.
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Birdy (OAuth, Twitter, Tweets&MegaHAL v6.01d) Jun12,2013
Goto page Previous  1, 2, 3 ... 18, 19, 20, 21  Next
 
Post new topic   Reply to topic    egghelp.org community Forum Index -> Script Support & Releases
View previous topic :: View next topic  
Author Message
daigo
Voice


Joined: 27 Jun 2014
Posts: 37
PostPosted: Sun Jul 27, 2014 9:46 am    Post subject: Reply with quote
Also getting this error:

Code:
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:
set twitter(flags) "n|n"


And my eggdrop flags:

Code:

[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.
Back to top
View user's profile Send private message
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Wed Oct 15, 2014 10:58 am    Post subject: OAUTH errors since Twitter disabled SSL 3.0 Reply with quote
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?
Back to top
View user's profile Send private message
SignZ
Voice


Joined: 17 Jun 2010
Posts: 18
PostPosted: Wed Oct 15, 2014 12:57 pm    Post subject: Re: OAUTH errors since Twitter disabled SSL 3.0 Reply with quote
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
Quote:
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. :/
Back to top
View user's profile Send private message
NewzNZ
Halfop


Joined: 05 Mar 2009
Posts: 60
PostPosted: Wed Oct 15, 2014 8:42 pm    Post subject: Reply with quote
I've been getting this error for about the last 48 hrs:

Quote:
OAuth failed: (???) Unknown problem... No reason given...( ok )
Back to top
View user's profile Send private message Visit poster's website
SignZ
Voice


Joined: 17 Jun 2010
Posts: 18
PostPosted: Thu Oct 16, 2014 3:42 am    Post subject: Reply with quote
NewzNZ wrote:
I've been getting this error for about the last 48 hrs:

Quote:
OAuth failed: (???) Unknown problem... No reason given...( ok )

heh, I've seen that one in my logs for months now.
Back to top
View user's profile Send private message
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Thu Oct 16, 2014 8:38 am    Post subject: OAUTH errors since Twitter disabled SSL 3.0 Reply with quote
Is anyone not getting these errors currently?
Back to top
View user's profile Send private message
johne
Voice


Joined: 19 Jul 2005
Posts: 29
PostPosted: Thu Oct 16, 2014 3:05 pm    Post subject: Reply with quote
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.
Back to top
View user's profile Send private message
SignZ
Voice


Joined: 17 Jun 2010
Posts: 18
PostPosted: Thu Oct 16, 2014 4:25 pm    Post subject: Reply with quote
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!). Very Happy
I also can confirm this works.
Back to top
View user's profile Send private message
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Thu Oct 16, 2014 8:03 pm    Post subject: Works Reply with quote
Thanks for the quick response! Confirmed working.
Back to top
View user's profile Send private message
NewzNZ
Halfop


Joined: 05 Mar 2009
Posts: 60
PostPosted: Thu Oct 16, 2014 8:43 pm    Post subject: Reply with quote
Working here also - thanks guys!
Back to top
View user's profile Send private message Visit poster's website
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Fri Oct 17, 2014 12:42 pm    Post subject: May have spoken too soon Reply with quote
That fix seemed to work for a while, but within 24 hours the errors return until I restart the bot. Anyone else?
Back to top
View user's profile Send private message
NewzNZ
Halfop


Joined: 05 Mar 2009
Posts: 60
PostPosted: Sat Oct 18, 2014 5:55 pm    Post subject: Reply with quote
Quote:
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.
Back to top
View user's profile Send private message Visit poster's website
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Mon Oct 20, 2014 9:11 am    Post subject: Still having trouble Reply with quote
Quote:
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.
Back to top
View user's profile Send private message
shadrach
Halfop


Joined: 14 Dec 2007
Posts: 74
PostPosted: Tue Oct 21, 2014 8:16 am    Post subject: Reply with quote
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.
Back to top
View user's profile Send private message MSN Messenger
Nocty
Voice


Joined: 17 Jun 2014
Posts: 15
PostPosted: Tue Oct 21, 2014 9:24 am    Post subject: Troubleshooting Reply with quote
Quote:
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?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    egghelp.org community Forum Index -> Script Support & Releases All times are GMT - 4 Hours
Goto page Previous  1, 2, 3 ... 18, 19, 20, 21  Next
Page 19 of 21

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Forum hosting provided by Reverse.net

Powered by phpBB © 2001, 2005 phpBB Group
subGreen style by ktauber