Chat not refreshing

[FuNFooKaS]

UNIT3D Version

v9.1.5

PHP & Platform

8.4.10 ubuntu 22.04

Laravel verion

12.20.0

Have you done this?

• I am willing to share my stack trace and logs
• I can suggest a fix as a Pull Request

Expectation

when type a new message in chat i expect it to post right way, but i have to manually refresh the browser to see the new chats. here is output from sudo tail -100 /var/log/supervisor/supervisord.log

Description

sudo tail -100 /var/log/supervisor/supervisord.log
2025-08-03 21:16:19,550 INFO success: unit3d-queue_01 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:19,576 INFO exited: unit3d-queue_00 (exit status 1; not expected)
2025-08-03 21:16:20,580 INFO spawned: 'unit3d-queue_00' with pid 2413
2025-08-03 21:16:21,267 INFO success: unit3d-queue_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:21,267 INFO exited: unit3d-queue_03 (exit status 0; expected)
2025-08-03 21:16:21,302 INFO spawned: 'unit3d-queue_03' with pid 2423
2025-08-03 21:16:21,303 INFO exited: unit3d-queue_02 (exit status 0; expected)
2025-08-03 21:16:21,390 INFO spawned: 'unit3d-queue_02' with pid 2424
2025-08-03 21:16:21,391 INFO success: unit3d-queue_03 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:21,407 INFO success: unit3d-queue_02 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:22,861 INFO waiting for unit3d-chat-server_00, unit3d-queue_00, unit3d-queue_01, unit3d-queue_02, unit3d-queue_03 to die
2025-08-03 21:16:22,885 INFO stopped: unit3d-queue_03 (exit status 0)
2025-08-03 21:16:22,887 INFO stopped: unit3d-queue_01 (exit status 0)
2025-08-03 21:16:22,888 INFO stopped: unit3d-queue_00 (exit status 0)
2025-08-03 21:16:22,889 INFO stopped: unit3d-queue_02 (exit status 0)
2025-08-03 21:16:22,906 INFO stopped: unit3d-chat-server_00 (exit status 0)
2025-08-03 21:16:22,926 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-08-03 21:16:22,926 INFO Included extra file "/etc/supervisor/conf.d/unit3d-chat-server.conf" during parsing
2025-08-03 21:16:22,926 INFO Included extra file "/etc/supervisor/conf.d/unit3d.conf" during parsing
2025-08-03 21:16:22,928 INFO RPC interface 'supervisor' initialized
2025-08-03 21:16:22,928 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-08-03 21:16:22,929 INFO supervisord started with pid 773
2025-08-03 21:16:23,932 INFO spawned: 'unit3d-chat-server_00' with pid 2453
2025-08-03 21:16:23,938 INFO spawned: 'unit3d-queue_00' with pid 2454
2025-08-03 21:16:23,943 INFO spawned: 'unit3d-queue_01' with pid 2455
2025-08-03 21:16:23,948 INFO spawned: 'unit3d-queue_02' with pid 2456
2025-08-03 21:16:23,953 INFO spawned: 'unit3d-queue_03' with pid 2457
2025-08-03 21:16:24,660 INFO success: unit3d-queue_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:24,661 INFO success: unit3d-queue_01 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:24,662 INFO success: unit3d-queue_02 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:24,662 INFO success: unit3d-queue_03 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:16:25,459 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:16:41,113 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:16:42,117 INFO spawned: 'unit3d-chat-server_00' with pid 2543
2025-08-03 21:16:43,120 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:17:05,508 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:17:06,512 INFO spawned: 'unit3d-chat-server_00' with pid 2651
2025-08-03 21:17:07,514 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:18:13,207 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:18:14,211 INFO spawned: 'unit3d-chat-server_00' with pid 2906
2025-08-03 21:18:15,214 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:27:40,224 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:27:41,228 INFO spawned: 'unit3d-chat-server_00' with pid 5052
2025-08-03 21:27:42,230 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:28:18,624 INFO waiting for unit3d-chat-server_00, unit3d-queue_00, unit3d-queue_01, unit3d-queue_02, unit3d-queue_03 to die
2025-08-03 21:28:18,646 INFO stopped: unit3d-queue_00 (exit status 0)
2025-08-03 21:28:18,649 INFO stopped: unit3d-queue_01 (exit status 0)
2025-08-03 21:28:18,650 INFO stopped: unit3d-queue_02 (exit status 0)
2025-08-03 21:28:18,673 INFO stopped: unit3d-queue_03 (exit status 0)
2025-08-03 21:28:18,685 INFO stopped: unit3d-chat-server_00 (exit status 0)
2025-08-03 21:28:18,703 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-08-03 21:28:18,703 INFO Included extra file "/etc/supervisor/conf.d/unit3d-chat-server.conf" during parsing
2025-08-03 21:28:18,703 INFO Included extra file "/etc/supervisor/conf.d/unit3d.conf" during parsing
2025-08-03 21:28:18,705 INFO RPC interface 'supervisor' initialized
2025-08-03 21:28:18,706 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-08-03 21:28:18,706 INFO supervisord started with pid 773
2025-08-03 21:28:19,710 INFO spawned: 'unit3d-chat-server_00' with pid 5233
2025-08-03 21:28:19,714 INFO spawned: 'unit3d-queue_00' with pid 5234
2025-08-03 21:28:19,718 INFO spawned: 'unit3d-queue_01' with pid 5235
2025-08-03 21:28:19,723 INFO spawned: 'unit3d-queue_02' with pid 5236
2025-08-03 21:28:19,727 INFO spawned: 'unit3d-queue_03' with pid 5237
2025-08-03 21:28:20,730 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:28:20,730 INFO success: unit3d-queue_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:28:20,730 INFO success: unit3d-queue_01 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:28:20,730 INFO success: unit3d-queue_02 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:28:20,730 INFO success: unit3d-queue_03 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:28:27,147 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:28:28,151 INFO spawned: 'unit3d-chat-server_00' with pid 5299
2025-08-03 21:28:29,153 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:29:05,473 INFO exited: unit3d-queue_00 (exit status 0; expected)
2025-08-03 21:29:05,474 INFO exited: unit3d-queue_02 (exit status 0; expected)
2025-08-03 21:29:05,477 INFO spawned: 'unit3d-queue_00' with pid 5452
2025-08-03 21:29:05,481 INFO spawned: 'unit3d-queue_02' with pid 5453
2025-08-03 21:29:05,501 INFO success: unit3d-queue_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:05,502 INFO success: unit3d-queue_02 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:05,504 INFO waiting for unit3d-chat-server_00, unit3d-queue_00, unit3d-queue_01, unit3d-queue_02, unit3d-queue_03 to die
2025-08-03 21:29:05,506 INFO stopped: unit3d-queue_00 (terminated by SIGTERM)
2025-08-03 21:29:05,507 INFO stopped: unit3d-queue_02 (terminated by SIGTERM)
2025-08-03 21:29:05,510 INFO stopped: unit3d-queue_03 (terminated by SIGTERM)
2025-08-03 21:29:05,527 INFO stopped: unit3d-queue_01 (exit status 0)
2025-08-03 21:29:05,539 INFO stopped: unit3d-chat-server_00 (exit status 0)
2025-08-03 21:29:05,561 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-08-03 21:29:05,562 INFO Included extra file "/etc/supervisor/conf.d/unit3d-chat-server.conf" during parsing
2025-08-03 21:29:05,562 INFO Included extra file "/etc/supervisor/conf.d/unit3d.conf" during parsing
2025-08-03 21:29:05,564 INFO RPC interface 'supervisor' initialized
2025-08-03 21:29:05,564 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-08-03 21:29:05,564 INFO supervisord started with pid 773
2025-08-03 21:29:06,568 INFO spawned: 'unit3d-chat-server_00' with pid 5460
2025-08-03 21:29:06,572 INFO spawned: 'unit3d-queue_00' with pid 5461
2025-08-03 21:29:06,577 INFO spawned: 'unit3d-queue_01' with pid 5462
2025-08-03 21:29:06,581 INFO spawned: 'unit3d-queue_02' with pid 5463
2025-08-03 21:29:06,586 INFO spawned: 'unit3d-queue_03' with pid 5464
2025-08-03 21:29:07,589 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-08-03 21:29:07,590 INFO success: unit3d-queue_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:07,590 INFO success: unit3d-queue_01 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:07,590 INFO success: unit3d-queue_02 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:07,590 INFO success: unit3d-queue_03 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-08-03 21:29:09,257 INFO exited: unit3d-chat-server_00 (exit status 1; not expected)
2025-08-03 21:29:10,262 INFO spawned: 'unit3d-chat-server_00' with pid 5506
2025-08-03 21:29:11,264 INFO success: unit3d-chat-server_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Stack trace & logs

[FuNFooKaS]

i did notice that the time stamps in chat keep updating though

[AnabolicsAnonymous]

Check the supervisor unit3d chat error/info log in that same folder, will probably give more information.

[mesoller]

Try run this code, I have similar issue previously. Unless it is specific bug in v9.1.5

sudo chown www-data /etc/letsencrypt -R && sudo php artisan queue:restart && sudo supervisorctl reread && sudo supervisorctl update && sudo supervisorctl reload

[FuNFooKaS]

unit3d-chat-server_00-stderr---supervisor-b8yek5y9.log is empty and only error log there also that command had no effect,

unit3d-chat-server_00-stdout---supervisor-bglye5jd.log
L A R A V E L E C H O S E R V E R

version 1.6.3

Starting server...

✔ Running at localhost on port 8443
✔ Listening for http events...
✔ Listening for redis events...

Server ready!

[AnabolicsAnonymous]

Are you sure you have the domain setup correctly in your laravel echo server config? It's showing localhost which doesn't sound right.

[FuNFooKaS]

it was setup auto when installed site but i just looked "host": null, is correct?

[AnabolicsAnonymous]

Very unlikely, authHost should be the url the tracker is hosted on, so if you are hosting the tracker on https://unit3d.site/ that should be your authHost. there may be other issues but that should be the first thing to be fixed.

[FuNFooKaS]

"authHost": "https://mysite url", is correct

[AnabolicsAnonymous]

Right, my bad. Are you also running this on cloudflare?

[FuNFooKaS]

no i am not

[AnabolicsAnonymous]

Check the network tab for websocket requests when you load the home page, what error do you get?

[FuNFooKaS]

no websocket errors

[AnabolicsAnonymous]

Does the websocket connect at all?

[FuNFooKaS]

Request URL
wss://mysiteurl:8443/socket.io/?EIO=4&transport=websocket
Request Method
GET
Status Code
101 Switching Protocols