The nvdaremoteserver from tech10

nvdaRemoteServer crashes and exits for unknown reasons

I suspect it is caused by some special characters;
There is no stable reproduction log for the time being.
I can provide the following logs of the server for your analysis；
If you need, I can provide complete server logs in private.
The last line of this log is the log before the last crash and exit.

2023/03/15 15:56:14 Client 1166 has connected from 112.53.150.141
2023/03/15 15:56:14 Client 1167 has connected from 112.53.150.141
2023/03/15 15:56:17 Client 1167 has set protocol version 2.
2023/03/15 15:56:17 Client 1167 has joined channel stz1121 as a slave. This client is authorized to control other computers.
2023/03/15 15:56:37 Client 1167 has left channel stz1121
2023/03/15 15:56:37 Client 1167 has disconnected.
2023/03/15 15:57:11 Client 1168 has connected from 112.53.150.141
2023/03/15 15:57:11 Error receiving message from client 1168.
local error: tls: bad record MAC
Closing connection.
2023/03/15 15:57:11 Client 1168 has disconnected.
2023/03/15 15:57:11 Client 1169 has connected from 112.53.150.141
2023/03/15 15:57:11 Error receiving message from client 1169.
read tcp 10.0.8.2:6837->112.53.150.141:55047: read: connection reset by peer
Closing connection.
2023/03/15 15:57:11 Client 1169 has disconnected.
2023/03/15 15:57:11 Client 1170 has connected from 112.53.150.141
2023/03/15 15:57:11 Client 1170 has set protocol version 2.
2023/03/15 15:57:11 Client 1170 has joined channel stz1121 as a master. This client is authorized to control other computers.
2023/03/15 16:01:00 Client 1171 has connected from 223.104.26.142
2023/03/15 16:01:00 Client 1171 has set protocol version 2.
2023/03/15 16:01:00 Client 1171 has joined channel 123654 as a slave. This client is authorized to control other computers.
2023/03/15 16:01:03 Client 1172 has connected from 223.104.26.142
2023/03/15 16:01:03 Client 1172 has set protocol version 2.
2023/03/15 16:01:03 Client 1172 has joined channel 123654 as a slave. This client is authorized to control other computers.
2023/03/15 16:02:31 Client 1173 has connected from 42.97.244.147
2023/03/15 16:02:31 Client 1173 has set protocol version 2.
2023/03/15 16:02:31 Channel 123 has been created.
2023/03/15 16:02:31 Client 1173 has joined channel 123 as a slave. This client is authorized to control other computers.
2023/03/15 16:03:07 Error sending message to client 1159.
write tcp 10.0.8.2:6837->223.104.26.142:8635: i/o timeout
Closing connection.
2023/03/15 16:03:12 Client 1159 has left channel 123654
2023/03/15 16:03:12 Client 1159 has disconnected.
2023/03/15 16:03:12 Error sending message to client 1164.
write tcp 10.0.8.2:6837->223.104.26.142:8641: i/o timeout
Closing connection.

Suggest that the author add a docker image

I recently deployed one and found that this NVDA remote server is quite good.
It would be nice to have a docker image.
We can use github's docker image feature for hosting.

Feature request: Add a parameter to limit large messages

TeleNVDA allows users to transfer files up to 10MB, but some servers have limited transfer capacity.
jmdaweb/NVDARemoteServer Added a parameter to allow server administrators to limit traffic transmission.
jmdaweb/NVDARemoteServer@75eed5d

@tech10 Do you have similar considerations, or have other ideas.

Thanks

tech10 / nvdaremoteserver Goto Github PK

nvdaremoteserver's People

Contributors

Stargazers

Watchers

Forkers

nvdaremoteserver's Issues

nvdaRemoteServer crashes and exits for unknown reasons

Suggest that the author add a docker image

Feature request: Add a parameter to limit large messages

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent