Talk error on fresh install #798
-
Talk service is not working at a fresh install on debian 11 amd64 arch. The container is created and in the admin settings dashboard everything seems to be fine, but I am unable to start any conversation. Here are the logs of the talk container. Apparently there are some errors during the installation
|
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 7 replies
-
Hi, did you open port 3478 udp and tcp? |
Beta Was this translation helpful? Give feedback.
-
Yes, here's the output of
I also do not have any firewall installed |
Beta Was this translation helpful? Give feedback.
-
What about port 3478/udp? Also, are you running it on a vps or in your home network? |
Beta Was this translation helpful? Give feedback.
-
I just updated the post, there's udp port also, but no |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
Office does not work in my environment also. When I load any document the icon spins for a bit and then says "Document loading failed. Failed to load nextcloud office - please try again later".
|
Beta Was this translation helpful? Give feedback.
-
I have a similar PC at home with about the same hardware (intel 4770) and exactly same debian (installed from the same usb stick). On my home pc reverse proxy is served by Caddy container and everything works fine. I do not own a domain so I use a custom Caddy build with duckdns https challenge |
Beta Was this translation helpful? Give feedback.
-
So I deployed a container with Caddy as reverse-proxy and Talk and Office work fine.
|
Beta Was this translation helpful? Give feedback.
-
Ok, so I've talked to IT department in our institution. They configured their reverse proxy according to the instruction in this repo. Talk app started working partially - users can chat with each other, but neither video nor audio conferencing work. And I do not have any errors in the Talk container. Users occasionally connect to the call and then disconnect after a short period. During the period when users seem to be connected to the call no audio or video is coming from them. Another thing is that we started to get errors from the Office container. When a user tries to open any document I get the following error in the container log:
Where I substituted real address with Can you look into that problem? |
Beta Was this translation helpful? Give feedback.
Hi, did you open port 3478 udp and tcp?