JamTaba icon indicating copy to clipboard operation
JamTaba copied to clipboard
verified publisher icon elieserdejesus

Unable to connect to my own private server, other people also unable to connect due to timeout

Open peberhart opened this issue 6 years ago • 4 comments

Hello,

I am writing because I recently installed the newest version (2.1.11) and I am having trouble hosting a private server. When I host the server, I am prompted that the server has been started, and the port has been opened. When I try to connect to my own server, I see in the Ninjam Private Server window that there is an incoming connection, I also see this when others try to connect. Anyone who attempts to connect cannot join due to timeout. What solution may there be for this?

I will also mention that I was able to host and connect to my own private server in the past version before Jamtaba v2. My ports on the router had been forwarded for that purpose, and I had allowed Jamtaba and Cubase connections in my firewall.

Thank you, Philip

peberhart avatar Apr 26 '20 01:04 peberhart

No ideas here @peberhart , the private server code was not changed in the last versions.

elieserdejesus avatar Apr 26 '20 01:04 elieserdejesus

No ideas here @peberhart , the private server code was not changed in the last versions.

Thank you for your reply. Would you propose any ideas as to how I could troubleshoot this? I'm somewhat at a loss as to how to proceed. I really enjoy the software, so thank you for providing it and I hope that I can keep using it to connect with distant friends and family.

peberhart avatar Apr 26 '20 05:04 peberhart

  • To reduce networking problems I suggest test with JamTaba standalone

  • Double check if JamTaba standalone is allowed in your firewall for both public and private connections.

  • Version 2.1.11 has a bug when connecting in your own server. It`s fixed for the next release. As workaround you must choose NO when prompted to connect in your own server, go to ninjam menu, connect in private server and use localhost as server name.

  • Double check if you are port forwarding the port 2049 for TCP (JamTaba is not UDP).

  • Verify if your port is really opened using this tool https://www.yougetsignal.com/tools/open-ports/

elieserdejesus avatar Apr 26 '20 11:04 elieserdejesus

@peberhart latest versions of jamtaba (2.1.11 and 2.1.12) had connection issues on some systems. Try lastest one 2.1.13 probably it's fixed now.

jonjamcam avatar Apr 30 '20 00:04 jonjamcam