-
Notifications
You must be signed in to change notification settings - Fork 31
Still not working with 9.4 #36
Comments
it working fine... |
You must be joking. 9.4.4 glpi + this plugin = system errors |
working on 9.4.2 + telegrambot 2.0.0 |
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. |
There're some interactions with glpi api? No, nothing blocks glpiapi on my server-side. |
I am talking about network lock. I've had it, this could be it, I'm not saying that's it. |
click on date/hour, will show description of log |
your error is the return from telegram API, review it ! |
you need set the cron of your system to use CLI instead GLPI mode |
changed at plugin to use CLI instead of glpi - same error, still uses glpi according to error log. |
have a crontask running ? |
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 |
Is there any way i can force this plugin to use CLI mode? |
*/5 * * * * /usr/bin/php7.2 /var/www/glpi/front/cron.php --force messagelistener &> /dev/null |
thx |
you did it ? |
Changed, but no effect. In action logs i receive same error. |
reset api key for bot |
i need to add restapi key? or bot key? |
if bot key - checked twice. |
reset api key for bot in telegram. use botfather for that |
Did it for three or four times. No effect. |
So, I can't help you with that. Sorry |
Thank you any way |
hi, how is your plugin configuration? |
|
@jcrosasv send photos of the errors, please. |
Hello xpedroaugustox |
Guys, I resolved the problem upgrade PHP 5.6 to 7.2 and test messagelistener was successful. |
Come on! How long would it take you to upgrade to 9.4 support?
The text was updated successfully, but these errors were encountered: