We couldn't join the call because the connection timed out. Please check your network connection and try again. Check the troubleshooting section if the problem persists.

[sycshk]

I've tried many things and followed the document to configure as best as I can but I still get this error.
We couldn't join the call because the connection timed out. Please check your network connection and try again. Check the troubleshooting section if the problem persists.

Can someone shed some light on how I can fix this?

[streamer45]

@sycshk We'll need to see some logs (server and client), your current plugin config, and any other detail that may help, such as how you are running Mattermost (systems service, docker, etc.) and how your infrastructure looks like (e.g., load balancers, NAT gateways).

[sycshk]

@sycshk We'll need to see some logs (server and client), your current plugin config, and any other detail that may help, such as how you are running Mattermost (systems service, docker, etc.) and how your infrastructure looks like (e.g., load balancers, NAT gateways).

Before going through the log, which I'm not sure which are the ones I should get. I'll give out some background info.
I have Opnsense firewall router, Adguard as DNS, Caddy as reverse proxy to a proxmox hosted turnkey mattermost which is upgraded to 10.5.1. Port 443 to 8065 upstream which I think is the default. All other communication and plugin seems to be working fine. MM's webserver configuration says the site URL isn't live which I don't know how to fix as well as to me, I don't see an issues arising from it. As for calls, host can make calls, joiners can receive calls but the calls never really join up. I suspect it's UDP not connecting. However, I'm not sure how the UDP even though I tried following documentation, it seems at a very low level without explaining the underlying reasons. Are there anything I should check ? As I'm not very techy with networks, it'd be great if you can elaborate a bit on what I should do as well.

[sycshk]

Opps, didn't plan to close.

[streamer45]

Before going through the log, which I'm not sure which are the ones I should get.

There's only one for MM called mattermost.log. As for the client, check https://docs.mattermost.com/collaborate/make-calls.html#js-console-logs.

Simply put, you need to ensure data can be exchanged from the client (e.g., your local system) to the MM host on the configured UDP port (default is 8443). This usually means ensuring firewall rules are allowing that. You may also need to tweak the config (e.g. ICE Host Override) with the address (usually a public IP) of the MM host.

There are some troubleshooting info at https://docs.mattermost.com/configure/calls-deployment.html#troubleshooting

[sycshk]

Before going through the log, which I'm not sure which are the ones I should get.

There's only one for MM called mattermost.log. As for the client, check https://docs.mattermost.com/collaborate/make-calls.html#js-console-logs.

Simply put, you need to ensure data can be exchanged from the client (e.g., your local system) to the MM host on the configured UDP port (default is 8443). This usually means ensuring firewall rules are allowing that. You may also need to tweak the config (e.g. ICE Host Override) with the address (usually a public IP) of the MM host.

There are some troubleshooting info at https://docs.mattermost.com/configure/calls-deployment.html#troubleshooting

Thanks for helping out. I only had time today to try out. Your suggestion actually works well, I setup ICE to use the URL and calls are connected now. However, screen sharing displays nothing at the moment. Not sure if there are specific configurations I need to set for that.