Open fancycode opened 3 years ago
I'm not sure if my issue is related, but upon changing a signaling server domain on cloud 1, cloud 2 that used to be able to communicate with previous signaling server on cloud 1, can no longer, throwing error instead of being aware of new signaling server configured.
The error thrown is only in logs, and does not show up for the user at all.
Expected behavior -
The signaling server should be queried regularly? Updated if necessary? At the very least a method to modify the signaling server manually, and error message to user?
Actual behavior -
it seems that once a user is connected with a signaling server on a specific domain, that domain stays regardless of any change that may have occurred on the remote signaling server domain...
Not sure what you mean, but if the domain of your signaling server changes, you will need to update the configuration of all Nextcloud instances that are using it.
Anyway, this is not related to this issue which is about the hosted HPB service.
Steps to reproduce
sub1.domain.tld
and request a trial of the hosted signaling server.sub2.otherdomain.tld
.Expected behaviour
Actual behaviour
The cause of the failed requests is that for security reasons, the HPB service checks any requests against the hostname an account was registered for.