Skip to content
This repository has been archived by the owner on Mar 31, 2022. It is now read-only.

Error in messagelistener #10

Open
jeffersantoss opened this issue Oct 25, 2017 · 13 comments
Open

Error in messagelistener #10

jeffersantoss opened this issue Oct 25, 2017 · 13 comments
Assignees
Projects
Milestone

Comments

@jeffersantoss
Copy link

Description in log: Action completed, no processing required
Details inside item log Running status: Error. Telegram returned an invalid response! Please review your bot name and API key.

I tried with two different bot names and I'm totally sure that token and username are correct but I still the error.

erro_glpi

@marcelofares
Copy link

I have this same problem.
Did you solve it in what way?

@matrixsupport
Copy link

Me too has this Issue !

@newtonnh
Copy link

newtonnh commented Nov 9, 2017

Me too, I already reinstalled my server about six times, but the problem is not solved.

But I do not know if this will help anyone in any way, but there it goes:
If you followed GLPi setup guide probably you put as database password something like that something@something. I found on Internet a tip to edit manually the file config_db.php, verify the password, I don't know why, into file config_db.php the "at" appears something like that "%40", I've changed the "%40" for "@", to me the error on GLPi is solved, in my case I've configured to receive a message as a new ticket is open, but this function isn't work yet. I'm still looking for any tip to solve this problem.

Regards

@mays1509
Copy link

I also have that problem, I'm new to the tool, and this is solved?

@Drumhazzard
Copy link

Hi All!

I have the same error that @jeffersantoss
I try with some differents bots, usernames and tokens, but the issue persits

:(

@Drumhazzard
Copy link

¡Solved!

In Windows clients, you need to modify
...\plugins\telegrambot\vendor\longman\telegram-bot\src\Request.php

You must add 'verify' ==> false, at line 215

Like this: self::setClient(new Client(['base_uri' => self::$api_base_uri,'verify' => false,]));

@LordBat
Copy link

LordBat commented Jan 17, 2018

Hi, any advance about this? i still have the same issue "Error. Telegram returned an invalid response! Please review your bot name and API key."
I put the correct API key, and bot name.
i try to modify the "Request.php" but the problem continue.

This is my enviroment:

Ubuntu Server 16.04
php 7.0
mariaDB 10

any suggestion will be great.

Thanks and Regards!

@yustas84
Copy link

Hello. We have same problem. tried all the above, the problem remains

@ajsb85 ajsb85 added this to To do in Plugin Apr 20, 2018
@ajsb85 ajsb85 added this to the 1.0 milestone Apr 23, 2018
@sazanof
Copy link

sazanof commented Jul 2, 2018

+++ Please help us!

@sazanof
Copy link

sazanof commented Jul 2, 2018

try this! its solved for me

....
'base_uri' => 'https://api.telegram.org',
'proxy' => 'socks5://218.248.73.193:1080',
'verify' => false,

@marcelofares
Copy link

The tip of our friend Drumhazzard solved it for me.

In Windows clients, you need to modify
... \ plugins \ telegrambot \ vendor \ longman \ telegram-bot \ src \ Request.php

You must add 'verify' ==> false, at line 215

Like this: self :: setClient (new Client (['base_uri' => self :: $ api_base_uri, 'verify' => false,]));

@yustas84
Copy link

yustas84 commented Jul 3, 2018

This doesn't help too
self::setClient(new Client(['base_uri' => ' https://api.telegram.org ', 'proxy' => 'socks5: //218.248.73.193: 1080', 'verify' => false]));
image

image

@sazanof
Copy link

sazanof commented Jul 3, 2018

Try this. Its worked for me

self::setClient(new Client(['base_uri' => self::$api_base_uri,'proxy'=>'socks5://yahaha.us:yahaha.us@socks5-a.yahaha.win:2019']));

if no ssl, then add 'verify' => false

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Plugin
  
To do
Development

No branches or pull requests