Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Authorized... EOF... die #358

Closed
alexander171294 opened this issue Nov 24, 2020 · 5 comments
Closed

Authorized... EOF... die #358

alexander171294 opened this issue Nov 24, 2020 · 5 comments
Labels
needs triage Metadata needs to be triaged and updated

Comments

@alexander171294
Copy link

Hi! i recently installed Teleirc as binary on Debian 9, I try to run the bot and show me this:

admin@Empireo:/usr/local/bin$ sudo /usr/local/bin/teleirc -conf /etc/teleirc/env
INFO: 2020/11/24 22:31:53 Current TeleIRC version: v2.0
INFO: 2020/11/24 22:31:53 Creating new Telegram bot client...
INFO: 2020/11/24 22:31:53 Creating new IRC bot client...
INFO: 2020/11/24 22:31:53 Starting up Telegram bot...
INFO: 2020/11/24 22:31:53 Starting up IRC bot...
INFO: 2020/11/24 22:31:54 Authorized on account HiranaBot
ERROR: 2020/11/24 22:31:54 EOF
ERROR: 2020/11/24 22:31:54 EOF
admin@Empireo:/usr/local/bin$

In the env configuration I paste the bot ID and channel ID.

Why doesn't work?

Thanks!
@alexander171294 alexander171294 added the needs triage Metadata needs to be triaged and updated label Nov 24, 2020
@alexander171294
Copy link
Author

In debug mode:

alex@Empireo:/usr/local/bin$ sudo /usr/local/bin/teleirc -conf /etc/teleirc/env -debug=true
INFO: 2020/11/24 22:41:05 Current TeleIRC version: v2.0
DEBUG: 2020/11/24 22:41:05 Debug mode enabled!
INFO: 2020/11/24 22:41:05 Creating new Telegram bot client...
INFO: 2020/11/24 22:41:05 Creating new IRC bot client...
INFO: 2020/11/24 22:41:05 Starting up Telegram bot...
INFO: 2020/11/24 22:41:05 Starting up IRC bot...
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: CLIENT_CONNECTED
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: JOIN
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: KICK
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: PRIVMSG
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: PART
DEBUG: 2020/11/24 22:41:05 Adding IRC event handler: QUIT
ERROR: 2020/11/24 22:41:05 EOF
ERROR: 2020/11/24 22:41:05 EOF
alex@Empireo:/usr/local/bin$

@fgaz
Copy link
Contributor

fgaz commented Dec 9, 2020

I'm also seeing the same since yesterday. I didn't touch anything on the server, so this is a surprise. I'm still on 2.0.1, so I'll try upgrading and see if that fixes it

@alexander171294
Copy link
Author

alexander171294 commented Dec 9, 2020 •
edited
Loading

In my case, y change the TLS port to unsecure port and just works, I think this is a problem with ssl for example expired or malformed. I can't do work with TLS.

@fgaz fgaz mentioned this issue Dec 9, 2020
Closed
@fgaz
Copy link
Contributor

fgaz commented Dec 9, 2020

That's weird, I can connect to freenode just fine via other clients

@fgaz
Copy link
Contributor

fgaz commented Dec 9, 2020

Upgrading to 2.1 (and setting the new IRC_BOT_IDENT config) fixed it for me, even with tls enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs triage Metadata needs to be triaged and updated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexander171294 @fgaz