HPB Talk won't work for unknown reasons

Thank you to give me your informations but, I tried to set date manually on my NC server, reverse proxy server and signaling server and I changed backend signaling secret key but I always have the same error in the browser console and in the reverse proxy log…

@B0r1sBack see NPM config High Performance Backend for Talk on Nextcloud with Docker have you enabled WSS in NPM?

Hi @scubamuc
Yes, I have this config :

        location /standalone-signaling/ {
                proxy_pass http://signaling/;
                proxy_http_version 1.1;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_read_timeout 36000s;
        }

        location /standalone-signaling/spreed {
                proxy_pass http://signaling/spreed;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "Upgrade";
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_read_timeout 36000s;
        }

I look for a solution again and again but I don’t know where is my problem …
I tried to test my hpb server with this kind of website :

I fill wss://MyHPB_URL/standalone-signaling/spreed
and I have this message :

Connection Established
▼ {“type”:“welcome”,“welcome”:{“version”:“unknown”,“features”:[“audio-video-permissions”,“dialout”,“federation”,“hello-v2”,“incall-all”,“join-features”,“mcu”,“offer-codecs”,“recipient-call”,“simulcast”,“switchto”,“transient-data”,“update-sdp”,“virtual-sessions”,“welcome”]}}
{“type”:“bye”,“bye”:{“reason”:“hello_timeout”}}

I think my HPB works fine …
someone want try his nextcloud instance with my HPB server ?

I have just tried to subscribe to 30 days trial HPB server (in talk settings) and I have exactly the same problem …
I precise you my nextcloud instance is behind the same nginx reverse proxy than HPB server

I opened an issue on the project github page and there is the solution :

It was the old public key which generated an invalid token … I don’t know why …

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.