This is a possible fix (worked for me). It took me ages to figure out (AI had no clue) what this could be as everything worked flawlessly (nextcloud, remote hpb server etc.) I kept getting this error (room ID redacted) every morning (after a middle of a night nextcloud maintenance routine): ClientException Client error: \`POST https://hpb.m-pr.tv/api/v1/room/ajr85fp7\` resulted in a \`403 Forbidden\` response: Authentication check failedTo save your time - check your nextcloud config.php:
IF YOU HAVE THIS: ‘overwrite.cli.url’ => ‘http://localhost’,
CHANGE IT TO ‘overwrite.cli.url’ => ‘https://YourActualPublicAddress’,
And voila! It all works.
This error/solution is probably relevant only if you have nextcloud and talk hpb servers on different machines.
Hi @Kirill_Nersesyan ,
thanks for your note about this issue! I have the same problem.
Since I´m not an expert on this toppic I asked AI too and Clause Sonet came up whit this explanation:
Cause: The [backend] section in /etc/nextcloud-spreed-signaling/server.conf had an empty secret field, while Nextcloud had a shared secret correctly configured on its end. This mismatch caused all backend requests from Nextcloud to be rejected by the signaling server.
Fix: Populated the secret field in the [backend] section of server.conf on the signaling server VPS to match the secret configured in Nextcloud Talk settings, then restarted the nextcloud-spreed-signaling service.
BUT just in the next section called [nextcloud-backend-0] there was the correct secret key defined:
So this fix and including your suggestion led to no error for me. I will investigate it further.
