Chatify - 500 Server Error

Hi,
I getting suddenly the server error 500 for extension chatify.
This was working good yesterday.
Is there any change?
I can not find any mesages by pusher.

mpol_ch

Your information is too limited. 500 Server Error is triggered by the web server, you better enable error log of your web server (not PHPMaker) and check the log. If you use Apache, you may google “apache enable error log”.

Hallo
I am still having the same server 500 error.
Below is the result from log file:

[2023-10-01T20:58:28.906320+02:00] log.DEBUG: SELECT t0.ID AS ID_1, t0.Name AS Name_2, t0.First_name AS First_name_3, t0.Last_name AS Last_name_4, t0.Email AS Email_5, t0.Avatar AS Avatar_6, t0.Active_status AS Active_status_7, t0.Messenger_color AS Messenger_color_8, t0.Created_at AS Created_at_9, t0.benutzername AS benutzername_10, t0.kennwort AS kennwort_11, t0.Activated AS Activated_12, t0.Profil AS Profil_13 FROM user t0 WHERE t0.benutzername = ? LIMIT 1 {"params":["alice"],"types":["string"],"executionMS":0.0011210441589355469} []
[2023-10-01T20:58:28.911326+02:00] log.DEBUG: SELECT COUNT(*) FROM user {"params":[],"types":[],"executionMS":0.00022912025451660156} []
[2023-10-01T20:58:28.911656+02:00] log.DEBUG: SELECT * FROM user LIMIT 20 {"params":[],"types":[],"executionMS":0.00022101402282714844} []
[2023-10-01T20:59:08.036488+02:00] log.DEBUG: SHOW TABLE STATUS WHERE Engine = 'MyISAM' AND Name = 'user' {"params":[],"types":[],"executionMS":0.0010120868682861328} []
[2023-10-01T20:59:16.203250+02:00] log.DEBUG: SELECT t0.ID AS ID_1, t0.Name AS Name_2, t0.First_name AS First_name_3, t0.Last_name AS Last_name_4, t0.Email AS Email_5, t0.Avatar AS Avatar_6, t0.Active_status AS Active_status_7, t0.Messenger_color AS Messenger_color_8, t0.Created_at AS Created_at_9, t0.benutzername AS benutzername_10, t0.kennwort AS kennwort_11, t0.Activated AS Activated_12, t0.Profil AS Profil_13 FROM user t0 WHERE t0.benutzername = ? LIMIT 1 {"params":["john"],"types":["string"],"executionMS":0.0014030933380126953} []
[2023-10-01T20:59:16.207423+02:00] log.DEBUG: SELECT t0.ID AS ID_1, t0.Name AS Name_2, t0.First_name AS First_name_3, t0.Last_name AS Last_name_4, t0.Email AS Email_5, t0.Avatar AS Avatar_6, t0.Active_status AS Active_status_7, t0.Messenger_color AS Messenger_color_8, t0.Created_at AS Created_at_9, t0.benutzername AS benutzername_10, t0.kennwort AS kennwort_11, t0.Activated AS Activated_12, t0.Profil AS Profil_13 FROM user t0 WHERE t0.benutzername = ? LIMIT 1 {"params":["john"],"types":["string"],"executionMS":0.00026917457580566406} []
[2023-10-01T20:59:16.591234+02:00] log.DEBUG: SHOW TABLE STATUS WHERE Engine = 'MyISAM' AND Name = 'favorites' {"params":[],"types":[],"executionMS":0.0008380413055419922} []
[2023-10-01T20:59:16.624399+02:00] log.DEBUG: SELECT t0.ID AS ID_1, t0.Name AS Name_2, t0.First_name AS First_name_3, t0.Last_name AS Last_name_4, t0.Email AS Email_5, t0.Avatar AS Avatar_6, t0.Active_status AS Active_status_7, t0.Messenger_color AS Messenger_color_8, t0.Created_at AS Created_at_9, t0.benutzername AS benutzername_10, t0.kennwort AS kennwort_11, t0.Activated AS Activated_12, t0.Profil AS Profil_13 FROM user t0 WHERE t0.benutzername = ? LIMIT 1 {"params":["John"],"types":["string"],"executionMS":0.0006668567657470703} []
[2023-10-01T20:59:16.628254+02:00] log.DEBUG: SELECT COUNT(*) FROM favorites {"params":[],"types":[],"executionMS":0.0002219676971435547} []
[2023-10-01T20:59:16.628634+02:00] log.DEBUG: SELECT * FROM favorites LIMIT 20 {"params":[],"types":[],"executionMS":0.00021791458129882812} []

mpol_ch

arbei wrote:

you better enable error log of your > web server (not PHPMaker) > and check the log. If you use Apache, you may google “apache enable error log”.

What you posted is from the PHPMaker log file and there is no error in the log file. As said, you should enable and check the web server log file for 500 error.

I just tried with the latest version.
But the result is the same.
I am getting the 500 Server Error.

[Mon Oct 02 21:14:33.937279 2023] [core:warn] [pid 5656:tid 364] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten – Unclean shutdown of previous Apache run?
[Mon Oct 02 21:14:33.966319 2023] [mpm_winnt:notice] [pid 5656:tid 364] AH00455: Apache/2.4.56 (Win64) OpenSSL/1.1.1t PHP/8.2.4 configured – resuming normal operations
[Mon Oct 02 21:14:33.966319 2023] [mpm_winnt:notice] [pid 5656:tid 364] AH00456: Apache Lounge VS16 Server built: Mar 7 2023 13:21:03
[Mon Oct 02 21:14:33.966319 2023] [core:notice] [pid 5656:tid 364] AH00094: Command line: ‘c:\xampp\apache\bin\httpd.exe -d C:/xampp/apache’
[Mon Oct 02 21:14:33.966319 2023] [mpm_winnt:notice] [pid 5656:tid 364] AH00418: Parent: Created child process 13428
[Mon Oct 02 21:14:34.296856 2023] [mpm_winnt:notice] [pid 13428:tid 360] AH00354: Child: Starting 150 worker threads.
[Mon Oct 02 21:38:41.904878 2023] [cgi:error] [pid 13428:tid 1920] [client 121.41.52.28:57688] AH02811: script not found or unable to stat: C:/xampp/cgi-bin/ViewLog.asp[Wed Oct 04 10:56:11.761017 2023] [core:warn] [pid 9680:tid 368] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten – Unclean shutdown of previous Apache run?
[Wed Oct 04 10:56:12.020067 2023] [mpm_winnt:notice] [pid 9680:tid 368] AH00455: Apache/2.4.56 (Win64) OpenSSL/1.1.1t PHP/8.2.4 configured – resuming normal operations
[Wed Oct 04 10:56:12.020067 2023] [mpm_winnt:notice] [pid 9680:tid 368] AH00456: Apache Lounge VS16 Server built: Mar 7 2023 13:21:03
[Wed Oct 04 10:56:12.020067 2023] [core:notice] [pid 9680:tid 368] AH00094: Command line: ‘c:\xampp\apache\bin\httpd.exe -d C:/xampp/apache’
[Wed Oct 04 10:56:12.020067 2023] [mpm_winnt:notice] [pid 9680:tid 368] AH00418: Parent: Created child process 3524
[Wed Oct 04 10:56:12.365176 2023] [mpm_winnt:notice] [pid 3524:tid 360] AH00354: Child: Starting 150 worker threads.

Your Apache log does not show any error. You better configure it to log more info (see ErrorLog and LogLevel) and check Apache’s error.log.Also check the access.log file and make sure the web server received the request for the chat site.Make sure you enable Debug and follow Check HTTP response, check the response body the the 500 response.Enable error settings in your php.ini as said in Debug.Then generate and run your project again, check the Apache error log and the project log file.

Hi,

I am seeing now in chat section the following error message after enabling the dedug option:

Symfony Exception
Non-static method Carbon\Carbon::setTimezone() cannot be called statically (View: C:\xampp\htdocs\2024\chatbox\laravel\resources\views\vendor\Chatify\layouts\modals.blade.php) (View: C:\xampp\htdocs\2024\chatbox\laravel\resources\views\vendor\Chatify\layouts\modals.blade.php)

...
C:\xampp\htdocs\2024\chatbox\src\ChatifyMessenger.php:29
...
        Carbon::setTimeZone(env('app.timezone.' . $_COOKIE[env('PHP_SESSION_NAME')])); //***
...

mpol_ch

Click Tools → Update Template to update the extension and try again.

Perfect, thank you.

Chating is now working.

The only issue is with the time. It shows me 2h behind the real time of chatting.
I entred “Europe/Berlin” into Tools/Local Setting" but no impact onto table messages…

Any hints for this?mpol_ch

mpol_ch wrote:

It shows me 2h behind the real time of chatting.
I entred “Europe/Berlin” into Tools/Local Setting" but no impact onto table messages… >

Where did you see the wrong time? In the chat widget? In the List/View page of the “Messages” table?

In the List/View page of the “Messages” table.

Click Tools → Update Template to update the extension and try again.

Perfect, thank you.
All works good now.

mpol_ch

Hi,Can attach only .zip files into chat as attachment?
Right now I can not not add .pdf or .docx files.
It seems not to allow these file types.
Is it possible to allow the .pdf and .docx?mpol_ch

The config file is \laravel\config\chatify.php.

Hi,

sometimes are the chat messages not submitting. There is a “clock” at end of message.
But the messages after it are submitted again.

mpol_ch

When you have errors, you should always enable debug and refer to the log files for server side errors and F12 → Console panel to client side errors.