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

Still not working with 9.4 #36

Open
reinethernal opened this issue Nov 8, 2019 · 33 comments
Open

Still not working with 9.4 #36

reinethernal opened this issue Nov 8, 2019 · 33 comments

Comments

@reinethernal
Copy link

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

it working fine...

@reinethernal
Copy link
Author

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

working on 9.4.2 + telegrambot 2.0.0

@reinethernal
Copy link
Author

reinethernal commented Nov 11, 2019

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

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
Copy link
Author

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

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
Copy link
Author

image
That what i have at status when run it manually

@mecmav
Copy link

mecmav commented Nov 11, 2019

click on date/hour, will show description of log

@reinethernal
Copy link
Author

image

@mecmav
Copy link

mecmav commented Nov 11, 2019

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

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

@reinethernal
Copy link
Author

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

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

@reinethernal
Copy link
Author

crontask is enabled
image

@mecmav
Copy link

mecmav commented Nov 11, 2019

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
Copy link
Author

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

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

@reinethernal
Copy link
Author

thx

@mecmav
Copy link

mecmav commented Nov 11, 2019

you did it ?

@reinethernal
Copy link
Author

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

@mecmav
Copy link

mecmav commented Nov 11, 2019

reset api key for bot

@reinethernal
Copy link
Author

i need to add restapi key? or bot key?

@reinethernal
Copy link
Author

if bot key - checked twice.

@mecmav
Copy link

mecmav commented Nov 11, 2019

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
Copy link
Author

Did it for three or four times. No effect.

@mecmav
Copy link

mecmav commented Nov 11, 2019

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

@reinethernal
Copy link
Author

Thank you any way

@xpedroaugustox
Copy link

hi, how is your plugin configuration?

@jcrosasv
Copy link

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
Copy link

@jcrosasv send photos of the errors, please.

@jcrosasv
Copy link

@jcrosasv send photos of the errors, please.

Hello xpedroaugustox

image

@jcrosasv
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants