M
M
Maxim Grechushnikov2015-10-01 11:08:36
JavaScript
Maxim Grechushnikov, 2015-10-01 11:08:36

Socket.io: Constantly disconnecting. How to catch the cause and has anyone had something similar?

There is a chat on Socket.io I turn on
the websocket with the command
./yii ws/start > /dev/null &
it starts the standard socket server from the documentation on port 8090.
Apache set up proxying from ws.site.ru:80 to localhost:8090. all ports are closed on the server except 80 and 22
when I start the socket server, everything works. chat connects. After some time, the connection stops working. htop shows that the script is hanging in memory and running. but the chat page can't connect.
What can be seen, how to track the causes? I tried to connect from a working computer, the same problem. As if the port is being closed.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
V
Vladislav Skillz, 2015-12-20
@maxyc_webber

There was a problem, I decided to reconfigure the connection times from scratch! Akubintsev is correct.

G
Gregory, 2015-10-01
@grigruss

Apache logs

A
Alexander Kubintsev, 2015-10-01
@akubintsev

Why apache and not nginx for proxying? Have you configured connection timeouts?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question