-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL connection abruptly cut in certain countries #553
Comments
What operating system are you using and what country are you connecting from? It is working fine for me using Windows 10 in the UK, but #554 reports someone having trouble connecting on Windows 11 due to a certificate error. |
Please run Syncplay with the --debug command line switch and let me know of anything potentially relevant which gets put into the syncplay.log or .Syncplay.log file in %APPDATA%. |
Also do you get any errors when you visit the https://syncplay.pl/ website in your browser? |
no no I can simply visit syncplay.pl website without any error I mean I don't need to change my IP or something , and that --debug command which you said didn't do anything , by the way , I'm from Iran |
This might be the same issue as #554 and so might have the same solution. Could you please try again with the build from https://github.com/Syncplay/syncplay/actions/runs/3235129755 and let me know if that fixes it. |
I tried it and it didn't work , these are the notifications that are shown: [17:30:02] Attempting to connect to syncplay.pl:8995 I don't know why it doesn't work ☹ by the way, I have windows 10 maybe it is because of the internet problems that we have in Iran these days , but I don't think so because my friends can use syncplay , they can connect |
@Someone7un7: With #565 I've made it give more explicit error messages when the connection is lost. Please try it out and let me know what error it gives: https://github.com/Syncplay/syncplay/actions/runs/3402038853 (scroll to the artifacts at the bottom and choose Syncplay-1.7.0-Setup.exe or Syncplay_1.7.0_Portable). |
Nothing worked , I'm using VPN |
Thanks for that clarification. There is some discussion of how to modify Syncplay code to run through a proxy at #346 but generally speaking Syncplay was only ever designed/intended to connect directly to the server. As such this seems less like a bug and more like a feature request. |
Is the connection working fine without VPN? Syncplay does use somewhat less typical port, so it's hard to tell whether VPN would interfere with it or not. |
When I use the app without VPN it doesn't work so I have to use VPN to connect to the servers . It works only with VPN and when I use VPN it works perfectly |
@Someone7un7 Can you try again with the build included here https://github.com/Syncplay/syncplay/actions/runs/3402038853 ? Please start Syncplay with the |
I've just seen your comment and did what you asked me to do and it is just like before , it only works with VPN |
Problem is solved , now everything is ok and I can use Syncplay without vpn |
It's good to hear that the problem is solved, although I'm not sure quite sure what changed. |
Hi, I also got the same problem while using Syncplay. Windows 11, Syncplay v1.7.0 development, no VPN |
@Talkbullet A few questions:
If you are able to run your own server then please do so and see if you have the same issues. |
Don't know how to start my own server, so i can't check it |
@Talkbullet When it disconnects does it successfully reconnect quickly and without issue? Syncplay's client and server both talk regularly to stay in sync and both use a timeout threshold of 12.5 seconds. This means that if 12.5 seconds has passed since the last relevant update they assume that the connection has failed and reconnect. What I don't know is what the timeout is from the TCP/TLS protocol which Syncplay servers and clients use - I assume it is whatever the default is for Endpoints (or is it something set at an OS level?). Syncplay's timeouts might be more strict than some systems, but it prevents situations where you can be disconnected for a long time and nobody realises it because the server and clients think the connection is still alive when it is not (which I seem to recall being an issue with Mumble, at least in the past). It might also be the case that other systems do reconnecting silently so you don't even know you were disconnected and reconnected. Disconnection could potentially happen more frequently if you either have a flakey connection to your ISP, or if the connection between the ISP and Syncplay's public servers (which are hosted in France) is flakey. A separate issue is if the server has been on too long and needs to be restarted to work reliably again. In my understanding it has not been long since the server was last restarted, and it'd start effecting a lot more people. However, you can always try a different port (I think syncplay.pl:8996) to see if it helps. Something else you could try is to use a third-party client such as https://syncplay.net/ and see if the issue still occurs. Finally, you could try running you own server (or getting a friend to do so) following the instructions at https://syncplay.pl/guide/server/ |
Thanks for reporting this issue. The port 8999 instance on the Syncplay server has been restarted and so should be working fine now. As far as I can tell the other instances were unaffected. |
@Et0h can you make servers auto-restart after some time? This will probably help with this issue. |
8999 / 8998 both unusable for me without vpn, again, this issue needs a solution. |
The server has been restarted and has now been set to automatically restart on the first and third Monday of the month at 9am France time. We have also adjusted the power profile to more performance oriented one. Let us know if you have any future issues. |
The problem is therefore probably not with Syncplay but somewhere else on the route from your PC to the Syncplay public servers, e.g. your ISP. Your best option might be to run your own Syncplay server. |
It happens to me and two of my friends, we all live in different countries. This also happens on another server https://syncplay.343.re/
I'll try this. |
My self-hosted syncplay instance started giving similar ( |
I can't connect to any of syncplay servers
What do I do?????
The text was updated successfully, but these errors were encountered: