Hello. I installed Signaling server as it described here . Everything is OK, but at the end of step 5 when I try curl -i http://127.0.0.1:8080/standalone-signaling/api/v1/welcome I recieve an answer: HTTP/1.1 404 Not Found Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff …

HI @uan Did you mean to use?: curl -L http://127.0.0.1:8080/standalone-signaling/api/v1/welcome

I copied a command here : [image] And there’s no difference in result

Hi @uan , Have you followed this post? [image] Talk High Performance Backend/Signaling Server Breaks Connectivity 💬 Talk (spreed) Before the HPB was open-sourced, there were few attempts to make Nextcloud work with established open source video-conferencing systems. Of pr…

Sorry, but I don’t undestand, what I need to follow. I read the post and as I see, there’s some another trouble than mine. In that theme user has 200 OK answer from signalling server. Or may be you mean something else?

Hi @uan , Maybe read again. The OP refers to a number of resources that resulted in an ‘almost there’ outcome. Maybe you’d want to see how those implementations differ from the one you followed to deliver a better outcome.

Signaling answers "404 page not found"

ℹ️ Support 💬 Talk (spreed)

NeptuneUK January 20, 2021, 10:35am 4

Hi @uan,

Have you followed this post?