Hi everyone I need help. I have installed Jamulus for a few days. I managed to create a "room" as you see in the photo, I see it, but other people don't see it, why? do I have to configure something somewhere? I await your help, thank you very much.
Andrew
Hi Gronaz - the info on those pages at http://llcon.sourceforge.net/ aren't being maintainined any more. I don't think there's anything actually wrong on the page you link to, but best refer to the Github wiki from now on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just had the same question! I finally got my private server setup and had a devil of a time with the internal Windows firewall when testing it offline. Not a firewall expert, but know how to set up a port. Used 22124 and it never worked.
I had to open ALL UDP ports to get it to work. Thought it was a Windows "thing."
However, I just now connected to my server, all working fine and decided to start the GUI. Guess what? I shows my port as 22134!! This seems to me to be reporting the port that my client is using. Right?
The EXE was from the download area here. No recompiling. No command line switches. Nothing done except install and run.
Is the port really 22134?!? Have all the server docs I've been trying to find (still looking for that How To and command line switches (but figured that one out using command line and --help) that allude to the port = 22124 been wrong, or am I missing something here?
I will next reset my firewall in the server to 22134 and see if it magically works or not. More in about an hour or so. - SJPbass.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The official Jamulus docs are now on the Github wiki. Please let us know if you don't understand anything there or if there's missing info. https://github.com/corrados/jamulus/wiki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Back to the 22124 vs 22134 port issue. I created a public server on my network, have forwarded both those ports to it in the router, and all appears to be fine since I and others have connected to it via the public server links. My client runs on a separate computer on that network.
At times, I'd like to make the server private while I'm jamming with my band and don't want interruptions. But if I try to enter the public ip of my router and click CONNECT, my client says "trying to connect" but never does. And my server shows my PRIVATE ip with the port 22134 (just like when I connect via the public link). Like this:
192.168.1.109:22134
Why 22134 appears? Why my local ip? Why does it work from the public server list but not when I enter my public ip to connect?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At the server-side the right port is 22124, the client side is using port 22134 .
If you want to run a private server, you have to activate portforwarding in your router ( in your case 192.168.1.109 - 22124.
I assume that 192.168.1.109 is the jamulus server's Ip-adres??!!
P.S. portforwarding is not necessary using a PUBLIC server.
Last edit: Luuk 2020-06-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
192.168.1.109 is my client computer address ( the server is ..1.105 and I forward ports to that IP). I can connect to the server with no problem from the public link, and the server displays 192.168.1.109:22134 as well as my name and the jitter buffer size.
BUT, when I enter my server's public IP number, the server displays the 192.168.1.109:22134 but NOT my name. And on a second line, it shows my router's address 192.168.1.1:22134 for about 20 seconds . The connection never completes though.
Even more weird, if I enter a url like remote.mydomain.com (which uses DDNS to translate to the same public IP used above), the server acts like as if I entered the IP number, but doesn't show that second line with my router's IP number on it!
Last edit: wysocki 2020-06-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi wysocki - just so I'm clear, do you mean you can connect to your server locally (by pointing your client to 192.168.1.109) but cannot if you connect to your public address (or dyndns entry)?
If so, it's best not to connect over a public IP to a server on your own network becuase many home routers/ISPs will have problems with that, and you will be introducing more network latency in any case.
The question is, can other people connect to your public IP/dns address?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone I need help. I have installed Jamulus for a few days. I managed to create a "room" as you see in the photo, I see it, but other people don't see it, why? do I have to configure something somewhere? I await your help, thank you very much.
Andrew
If you are behind a NAT router, did you forward the port 22124 to the inner IP address of the server machine ?
the port is 22134 or 22124?
22124
Last edit: Gronaz 2020-03-23
Hi Gronaz - the info on those pages at http://llcon.sourceforge.net/ aren't being maintainined any more. I don't think there's anything actually wrong on the page you link to, but best refer to the Github wiki from now on.
I just had the same question! I finally got my private server setup and had a devil of a time with the internal Windows firewall when testing it offline. Not a firewall expert, but know how to set up a port. Used 22124 and it never worked.
I had to open ALL UDP ports to get it to work. Thought it was a Windows "thing."
However, I just now connected to my server, all working fine and decided to start the GUI. Guess what? I shows my port as 22134!! This seems to me to be reporting the port that my client is using. Right?
The EXE was from the download area here. No recompiling. No command line switches. Nothing done except install and run.
Is the port really 22134?!? Have all the server docs I've been trying to find (still looking for that How To and command line switches (but figured that one out using command line and --help) that allude to the port = 22124 been wrong, or am I missing something here?
I will next reset my firewall in the server to 22134 and see if it magically works or not. More in about an hour or so. - SJPbass.
The official Jamulus docs are now on the Github wiki. Please let us know if you don't understand anything there or if there's missing info. https://github.com/corrados/jamulus/wiki
Gilgongo - Thanks for posting the server manual!
No problem. It's new (adapted and extended from various resources that were around), so if you have any suggestions to improve it, let us know!
Back to the 22124 vs 22134 port issue. I created a public server on my network, have forwarded both those ports to it in the router, and all appears to be fine since I and others have connected to it via the public server links. My client runs on a separate computer on that network.
At times, I'd like to make the server private while I'm jamming with my band and don't want interruptions. But if I try to enter the public ip of my router and click CONNECT, my client says "trying to connect" but never does. And my server shows my PRIVATE ip with the port 22134 (just like when I connect via the public link). Like this:
Why 22134 appears? Why my local ip? Why does it work from the public server list but not when I enter my public ip to connect?
At the server-side the right port is 22124, the client side is using port 22134 .
If you want to run a private server, you have to activate portforwarding in your router ( in your case 192.168.1.109 - 22124.
I assume that 192.168.1.109 is the jamulus server's Ip-adres??!!
P.S. portforwarding is not necessary using a PUBLIC server.
Last edit: Luuk 2020-06-05
192.168.1.109 is my client computer address ( the server is ..1.105 and I forward ports to that IP). I can connect to the server with no problem from the public link, and the server displays 192.168.1.109:22134 as well as my name and the jitter buffer size.
BUT, when I enter my server's public IP number, the server displays the 192.168.1.109:22134 but NOT my name. And on a second line, it shows my router's address 192.168.1.1:22134 for about 20 seconds . The connection never completes though.
Even more weird, if I enter a url like remote.mydomain.com (which uses DDNS to translate to the same public IP used above), the server acts like as if I entered the IP number, but doesn't show that second line with my router's IP number on it!
Last edit: wysocki 2020-06-05
Hi wysocki - just so I'm clear, do you mean you can connect to your server locally (by pointing your client to 192.168.1.109) but cannot if you connect to your public address (or dyndns entry)?
If so, it's best not to connect over a public IP to a server on your own network becuase many home routers/ISPs will have problems with that, and you will be introducing more network latency in any case.
The question is, can other people connect to your public IP/dns address?