Skip to content
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

Unable to connect to a private server #101

Closed
MayQueen33 opened this issue Jun 17, 2024 · 4 comments
Closed

Unable to connect to a private server #101

MayQueen33 opened this issue Jun 17, 2024 · 4 comments
Labels
already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out

Comments

@MayQueen33
Copy link

MayQueen33 commented Jun 17, 2024

Screenshot_2024-06-18-00-00-14-089_com reddnek syncplay
Always connecting........
It connects to official servers successfully. And my private server is accessible to Syncplay on PC.

@yuroyami
Copy link
Owner

@MayQueen33 If you're using a password for the private server, it may be related to this issue: Password preventing connection #91, I haven't looked into why it's happening as of yet

It might otherwise be caused by the TLS connection so try turning off TLS and let me know if it connects or not. You can also try using another network engine (you can find two Netty and Ktor, although Netty is pretty stable)

Let me know about your findings

@MayQueen33
Copy link
Author

MayQueen33 commented Jun 17, 2024

Netty without TLS
Screenshot_2024-06-18-00-00-14-089_com reddnek syncplay

Netty with TLS
Screenshot_2024-06-18-00-19-22-035-edit_com reddnek syncplay

Ktor with or without TLS
Screenshot_2024-06-18-00-20-08-447-edit_com reddnek syncplay

@MayQueen33
Copy link
Author

Maybe I can try turning off the password protection later.

@yuroyami yuroyami added the already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out label Jul 23, 2024
@yuroyami
Copy link
Owner

yuroyami commented Jul 23, 2024

The fix for this issue will be shipped in version 0.15.0

EDIT: 0.15.0 is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
already resolved - awaiting release Already resolved in source code, however the release containing the fix is still not out
Projects
None yet
Development

No branches or pull requests

2 participants