chesslablab/spablab

Game crashing whilst in progress

Closed this issue ยท 12 comments

This error has appeared before as explained in #564, and does not seem to have been resolved.

20230918_202429.png

@programarivm The previous issue had been closed as completed, so I opened up a new one. Maybe something else has to be done as the previous solution seemed to be only temporary :(

anyone knows why this is happening?

No idea here but it seems to throw time out errors too

Hey,
if you are using Nginx server there is default timeout setting which timeout websocket connection after 60 secons so to solve this you need to reconfigure your nginx server proxy and change/add below things

  • proxy_connect_timeout โ€“ maximum time to connect to a proxied server (default 60, usually under 75)
  • proxy_read_timeout โ€“ maximum time (between reads) to read proxied server response (default 60)

It would be true but that's not the cause of the error. The problem I am facing is that I disconnect while still on the servers and playing a game.

Well, at this moment the chesslablab.com site is running on a staging server which may contain errors.

It'd be helpful if the bugs could be replicated.

See:

Also the testing issues will help.

Keep it up,

@CodeMaster7000 how many times out of 10 attempts would the error appear? If it is rather frequent but cannot be replicated, there's no problem, please attach the exact time when it happens. Let's inspect the sequence of commands in the log.

@programarivm Aren't these empty files?

For the sake of security, the storage/pchess.log file exists in the staging environment only not in the GitHub repo which is a shared environment.

You can create a .gitignore file in your repository's root directory to tell Git which files and directories to ignore when you make a commit. To share the ignore rules with other users who clone the repository, commit the .gitignore file in to your repository.

See:

Happy coding!

@programarivm The issue also occurred at a similar frequency to the reconnecting issue, at a few times out of 10.

@CodeMaster7000 may I ask what device are you using when the error occurs?

See #678

Yes it is indeed often on a mobile.