-
Notifications
You must be signed in to change notification settings - Fork 23
botbot-bot connecting to an non-ssl IRC server causes a channel double close #29
Comments
@nicholasdavidson interesting. I have not try this setup in a long time and it was working at some point. This is not very helpful for you :-( . I will try to setup something similar to see what is happening. Thank you for your report. |
I have "rediscover" that the default debian/ubuntu config for ircd-hybrid is very conservative:
So disabling the throttle_time will let the bot connect multiple times to find out whether or not we need to use a TLS connection. @nicholasdavidson could you please let me know if this is working for you ? I am not sure if we need to change anything on the bot side to make it work out of the box. I do not want to add a sleep between the connection attempts. We could eventually avoid the connection degradation from TLS to plain text by adding a BooleanField in botbot-web. |
I can certainly try, it may take a few days as I don't have admin rights to the box where ircd-hybrid is hosted. |
I'm having the same issue. Changing the irc server for this may not be allowed. Other options? |
I am deploying on ubuntu-14.04 attempting to target a pretty much default configuration debian hybrid7 irc server. I followed the instructions in botbot-webs Readme.md and created a bot and a channel for our internal IRC server then used honcho to start the various services - I get:
The entire log is at https://gist.github.com/nicholasdavidson/d75c385f19b0a4e365e3
The text was updated successfully, but these errors were encountered: