cant write conversation TEXT messages when HPB is unreachable

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Today i ran into the problem that I couldn't write a text Message in nextcloud talk from a zone where the HPB of the Nextcloud instance wasn't reachable.

I can't imagine that this is intentional - probably hasn't been noticed so far, therefore i've choosen to report as a Bug.

The whole setup (audio/video/text etc.) works fine (unless the HPB is unreachable from the client Browser)

Steps to reproduce

1. make the HPB unreachable for the client webbrowser
2. try to write a text message

Expected behaviour

beeing able to use the text chat functionality without HPB

Actual behaviour

an error popup message "Failed to establish signaling connection. Retrying …" is displayed in the browser and the input box for text stays greyed out

Talk app

Talk app version: 22.0.7

Custom Signaling server configured: yes 2.0.4~docker

Custom TURN server configured: yes

Custom STUN server configured: yes

Browser

Operating system: Windows

Browser name: Firefox

Browser version: 140 ESR

Server configuration

Nextcloud Version: 32.0.3

Since everything (Text/Video/Audio) works when the HPB is reachable from the client I skip these details.
Of course I can add more details if needed.

Start by reproducing the issue in Nextcloud Talk with the HPB unreachable from the client browser, then trace the browser-side signaling failure and why the text input remains disabled. Done means text chat remains usable without the HPB and the signaling retry popup no longer blocks text entry.