Chat and Video in v...
 
Notifications
Clear all

[Solved] Chat and Video in version 25.3, does not work

10 Posts
7 Users
1 Reactions
777 Views
(@alexmanafan)
Active Member
Joined: 2 years ago
Posts: 21
Topic starter  

I updated to version 25.3 and the Chat has disappeared from Webmail. When I run 

curl -v  http://127.78.0.4:10000/health  | jq

I can see that everything is correct and enabled, but it doesn't appear in Webmail.

I performed a fresh, clean install of 25.3, and the result is the same: there's no Chat.
I noticed that when I run:

systemctl list-units "carbonio*"

I see that carbonio.service isn't running:

carbonio.service loaded failed failed LSB: Carbonio Services

But all services are working correctly: mail, tasks, files.
Any help? Is this something general?


   
Quote
(@m-sistem)
Active Member
Joined: 13 years ago
Posts: 15
 

I have the exact same problem after upgrade prom previous version to 25.3 ...


   
NETWORLD reacted
ReplyQuote
(@sharif)
Reputable Member Admin
Joined: 3 years ago
Posts: 769
 

@alexmanafan @m-sistem

Could you please check followings:

su - zextras -c "carbonio prov gc default carbonioFeatureWscEnabled"

 


   
ReplyQuote
(@alexmanafan)
Active Member
Joined: 2 years ago
Posts: 21
Topic starter  

@sharif 

This is the result of the previous command:

# name default
carbonioFeatureWscEnabled: FALSE

I also have a Carbonio CE 24.x with the Chat working without problems, the command shows the same result.

The problem is that it does not appear in the web client


   
ReplyQuote
(@alexmanafan)
Active Member
Joined: 2 years ago
Posts: 21
Topic starter  

@sharif @m-sistem

I executed:

su - zextras -c "carbonio prov mc default carbonioFeatureWscEnabled TRUE"

I restarted the services:

su - zextras -c 'zmcontrol restart'
systemctl restart carbonio-tasks
systemctl restart carbonio-message-broker
systemctl restart carbonio-message-dispatcher
systemctl restart carbonio-ws-collaboration
systemctl restart carbonio-videoserver

and I already have the Chat working without any problem, my question is the following since I did not know this command, su - zextras -c "carbonio prov mc default carbonioFeatureWscEnabled TRUE" is something new in this version?

I ask because as I mentioned before, in my Carbonio version 24 this also returns FALSE and I still have the Chat working.

@sharif Thanks for the help


   
ReplyQuote
(@hidigoudi)
New Member
Joined: 5 months ago
Posts: 4
 

Hello,

I have a similar issue with chat and video server features. Chat isn't working. When I try to send a message to someone the message stays as "Pending" state and I got this error in logs :

25-03-2025 15:56:38.126 ERROR c.z.c.c.c.logging.ChatsLogger  : An error occurred on /rooms 
 at com.zextras.carbonio.chats.core.infrastructure.messaging.impl.xmpp.MessageDispatcherMongooseImpl.createRoom [line 83] 
 Error while creating a room: [{"path":["muc_light","createRoom"],"message":"Unexpected MUCLightAdminMutation resolver crash","extensions":{"code":"resolver_crash"}}]

Same issue when I try to create a virtual room.

When I reboot the server, I also have a service error "carbonio.service" in failed state. I need to restart the service to make it working.

:~# su - zextras -c "zmcontrol -v"
Carbonio Release 25.3.0

Could you please help me ?

Thanks.


   
ReplyQuote
(@kunaljavare)
New Member
Joined: 3 months ago
Posts: 4
 

@sharif I got same error.

Unexpected MUCLightAdminMutation resolver crash

 

Please help to resolve it.


   
ReplyQuote
(@itguy)
Active Member
Joined: 11 years ago
Posts: 37
 

Add me to the list. Chat not working.

/var/log/carbonio/ws-collaboration# ws-collaboration.log

Same error as user: hidigoudi

I am on Carbonio CE 25.3.1


   
ReplyQuote
(@itguy)
Active Member
Joined: 11 years ago
Posts: 37
 

I made some progress.

Completely shutdown Carbonio and Start again.

Chat not working as per above message.

Stop and start the following services:

carbonio-message-dispatcher.service
carbonio-ws-collaboration.service
carbonio-tasks.service

Not so sure but, I think stop/start all three services made it work.

Will I have to do restart of all three services again and again? Don't know, time will tell.

PS. That is a fresh installation of 25.3.1


   
ReplyQuote
(@lucaslive974)
New Member
Joined: 3 days ago
Posts: 1
 

Fresh Installation of Carbonio – Migration Notes

I did a fresh installation of Carbonio today. After a lot of trial and error, I identified the main issue.

Key Issue

The following command:

PGPASSWORD=$DB_ADM_PWD carbonio-message-dispatcher-migration carbonio_adm 127.0.0.1

is related to the migration of the old chat UI. It updates the version column in the database that Carbonio uses to track updates.

⚠️ Important:
The migration services — ws, tasks, docs, message-dispatcher — do not actually perform any changes on PostgreSQL. Everything else seems up-to-date because the system reads the version column and assumes the updates were applied.

Verifying PostgreSQL Users and Databases

Connect to your PostgreSQL instance:

psql -h 127.0.0.1 -U carbonio_adm

Check users:

\du

Check databases:

\l

Verify the users and tables for each database:

  • carbonio-ws-collaboration-db

  • carbonio-tasks-db

  • carbonio-message-dispatcher-db

  • carbonio-docs-db

Each service has its own user and database, following the pattern:

carbonio-xxxxx-db

⚠️ Note: If anything is missing, it indicates a problem. In my case, it was a fresh install — I deleted everything and restarted the installation.

Recommended workflow (in a fresh install; adapt for previous installations):

  1. Run all pending setups except carbonio-message-dispatcher.

  2. After these, populate the databases:

 
PGPASSWORD=$DB_ADM_PWD carbonio-message-dispatcher-db-bootstrap carbonio_adm 127.0.0.1
PGPASSWORD=$DB_ADM_PWD carbonio-docs-connector-db-bootstrap carbonio_adm 127.0.0.1
PGPASSWORD=$DB_ADM_PWD carbonio-tasks-db-bootstrap carbonio_adm 127.0.0.1
PGPASSWORD=$DB_ADM_PWD carbonio-ws-collaboration-db-bootstrap carbonio_adm 127.0.0.1
  1. After these runs, execute the PostgreSQL verification commands (\du and \l) to ensure all users and databases exist.

  2. Then return to pending setups and run carbonio-message-dispatcher.

  3. Finally, run the infamous last migration:

 
PGPASSWORD=$DB_ADM_PWD carbonio-message-dispatcher-migration carbonio_adm 127.0.0.1

⚠️ Warning: Running the last migration too early will break PostgreSQL. Always follow this sequence.

This post was modified 3 days ago by lucaslive974

   
ReplyQuote