Still not working with 9.4

pluginsGLPI / telegrambot

Telegram Bot for GLPI

https://pluginsglpi.github.io/telegrambot/

GNU General Public License v3.0

39 stars 32 forks source link

Still not working with 9.4 #36

Open reinethernal opened 4 years ago

reinethernal commented 4 years ago

Come on! How long would it take you to upgrade to 9.4 support?

mecmav commented 4 years ago

it working fine...

reinethernal commented 4 years ago

You must be joking. 9.4.4 glpi + this plugin = system errors

mecmav commented 4 years ago

working on 9.4.2 + telegrambot 2.0.0

reinethernal commented 4 years ago

And you say it is working? Than happens when i try to create new ticket, add followup, etc.

mecmav commented 4 years ago

there's can be a lot of error of server-side, or some blocks in your ethernet, or some of returns from API... I already had many problems with error 500, from the most varied possible causes.

reinethernal commented 4 years ago

There're some interactions with glpi api? No, nothing blocks glpiapi on my server-side.

mecmav commented 4 years ago

I am talking about network lock. I've had it, this could be it, I'm not saying that's it. what status shows in messagelistener at run manually the task?

reinethernal commented 4 years ago

That what i have at status when run it manually

mecmav commented 4 years ago

click on date/hour, will show description of log

reinethernal commented 4 years ago

mecmav commented 4 years ago

your error is the return from telegram API, review it !

mecmav commented 4 years ago

you need set the cron of your system to use CLI instead GLPI mode

reinethernal commented 4 years ago

changed at plugin to use CLI instead of glpi - same error, still uses glpi according to error log.

mecmav commented 4 years ago

have a crontask running ? I believe you having troubles to implement the plugin.

reinethernal commented 4 years ago

crontask is enabled

mecmav commented 4 years ago

set /5 * ...... that way, every 5 minutes cron will run , the logs of messagelistener in GLPI should be "CLI mode". With that do some tests remember of review your API key on telegram, if necessary reset the API token for bot.

reinethernal commented 4 years ago

Is there any way i can force this plugin to use CLI mode?

mecmav commented 4 years ago

/5 * /usr/bin/php7.2 /var/www/glpi/front/cron.php --force messagelistener &> /dev/null

reinethernal commented 4 years ago

thx

mecmav commented 4 years ago

you did it ?

reinethernal commented 4 years ago

Changed, but no effect. In action logs i receive same error.

mecmav commented 4 years ago

reset api key for bot

reinethernal commented 4 years ago

i need to add restapi key? or bot key?

reinethernal commented 4 years ago

if bot key - checked twice.

mecmav commented 4 years ago

reset api key for bot in telegram. use botfather for that after reset api key, change bot token in glpi Notifications>Telegram Followups Config. with that, the log of messagelistener can't have any error

reinethernal commented 4 years ago

Did it for three or four times. No effect.

mecmav commented 4 years ago

So, I can't help you with that. Sorry

reinethernal commented 4 years ago

Thank you any way

xpedroaugustox commented 4 years ago

hi, how is your plugin configuration?

jcrosasv commented 4 years ago

working on 9.4.2 + telegrambot 2.0.0 How did you do?, I get error Error. Telegram returned an invalid response! Please review your bot name and API key.

xpedroaugustox commented 4 years ago

@jcrosasv send photos of the errors, please.

jcrosasv commented 4 years ago

@jcrosasv send photos of the errors, please.

Hello xpedroaugustox

jcrosasv commented 4 years ago

Guys, I resolved the problem upgrade PHP 5.6 to 7.2 and test messagelistener was successful.