Re: reg: websocket simple test

583 views
Skip to first unread message

Peter Thorson

unread,
Jul 10, 2020, 7:25:24 AM7/10/20
to Rambabu Yerajana, WebSocket++
Hi Rambabu,

This error indicates that the server that you are trying to connect to (running on localhost, port 9002) is refusing the connection. This happens most often when there is no server running on that port at all, but can also happen for a number of other reasons (such as if a firewall is blocking the connection).

I would double check your server software. Is it actually running? Is it running on port 9002? Is there a firewall in the way that would block the connection? Is a web browser client able to connect to this server?

Best,

Peter

> On 2020-07-08, at 09:15, Rambabu Yerajana <ramba...@gmail.com> wrote:
>
> Hi Team,
> Please help me in this.
>
> boost version: 1.54
> websocketpp version : 0.8.2
>
> I am getting an error from the client side.
> @client side
>
> $ ./echo_client ws://localhost:9002
> [2020-07-08 19:26:19] [info] asio async_connect error: system:111 (Connection refused)
> [2020-07-08 19:26:19] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
> [2020-07-08 19:26:19] [fail] WebSocket Connection Unknown - "" / 0 websocketpp.transport:2 Underlying Transport Error
> [2020-07-08 19:26:19] [error] handle_connect error: Underlying Transport Error
>
>
> @netstat -anp |grep tcp
>
> tcp6 0 0 :::9012 :::* LISTEN 18399/debug_server
>
> Thanks
> Rambabu
>

Reply all
Reply to author
Forward
0 new messages