Mike Bosschaert

OK, thanks. I'll discuss it with my ISP and report back the results

Ok, that's good to know, the limit of servers. However with the open firewall our server is registered and listed in https://explorer.jamulus.io, so I assume the primary problem was the port settigns. However good to keep in mind. Just to confirm, you mean 2212?

Ok, that's good to know, the limit of servers. However with the open firewall our server is registered and listed in https://explorer.jamulus.io, so I assume the primary problem was the port settigns. However good to keep in mind. Just to confirm, you mean 2212? O

I've tried to solve this with the company which hosts the server. Fiinally it was necessary to completely turn of the firewall of the hoster to get it to work. It would be interesting to know which ports are being (besides 22123-22125 and 22524) so we can activate the firewall again with only the required ports available. Could anyone tell which firewall and port-settings are required? Thanks, Mike

Hi, I've recently installed Jamulus 3.6.2 on a Debian 8.11 server which is hosted by an internet service provider. It has a fixed IP address. I've created a systemd startscript and the server is running. I've opened ports 22123-22125 for udp and tcp with UFW. When I configure it as public server, registration fails: sudo systemctl status jamulus ● jamulus.service - Jamulus-Server Loaded: loaded (/etc/systemd/system/jamulus.service; enabled) Active: active (running) since do 2021-02-11 10:10:24 CET;...