Signaling answers "404 page not found"

uan · January 19, 2021, 11:08am

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
Date: Tue, 19 Jan 2021 10:48:25 GMT
Content-Length: 19
What could be the reason?

NeptuneUK · January 19, 2021, 7:47pm

HI @uan

Did you mean to use?:

curl -L http://127.0.0.1:8080/standalone-signaling/api/v1/welcome

uan · January 20, 2021, 8:53am

I copied a command here:

And there’s no difference in result

NeptuneUK · January 20, 2021, 10:35am

Hi @uan,

Have you followed this post?

uan · January 20, 2021, 1:00pm

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?

NeptuneUK · January 20, 2021, 1:07pm

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.

uan · January 27, 2021, 11:40am

The answer is received here.