Menu

Connectivity difference between public (success) vs private (fail) server

Jeff Pera
2021-01-08
2021-01-08
  • Jeff Pera

    Jeff Pera - 2021-01-08

    I set up a VM for Jamulus on Google Cloud Platform with the help of the YouTube video "Jamulus server on GCP quick start video" (https://www.youtube.com/watch?v=9anNmobd5aY).

    I’m able to connect a client when I run a public server but not a private one (both server status's look fine). The only difference is the ExecStart statement in the unit file.

    headless private

    ExecStart=/usr/local/bin/Jamulus -s -n -w "Welcome to Francesca’s Jamulus server."

    headless public

    ExecStart=/usr/local/bin/Jamulus -s -n -e jamulusjazz.fischvolk.de:22324 -o “FP_server;San Francisco;225” -w "Welcome to Francesca’s Jamulus server."

    I'm not a tech wiz but was able to get this far; networking not a strength. I haven't found any articles that suggest what to look at. Why would connectivity be different in these two cases? Any ideas?

     
    • Gilgongo

      Gilgongo - 2021-01-08

      Hi Jeff,

      It sounds like a firewall issue. To run a private servers you will need to have incoming UDP (not TCP) port 22124 open to the outside (both source and destination I think).

       
      👍
      1
      • Jeff Pera

        Jeff Pera - 2021-01-08

        I followed the steps in the quick start video (https://www.youtube.com/watch?v=9anNmobd5aY) that run from 3:00 to 5:20 to open that UDP port. How can I test whether the port is open or not (from MacOS)? My searches for something suggest this may be a bit tricky. To confirm: connecting to a public server doesn't use UDP 22124?

         

        Last edit: Jeff Pera 2021-01-08
        • Vincenzo

          Vincenzo - 2021-01-08

          Try with this service: https://www.ipvoid.com/udp-port-scan/
          A public server does not need the same opening.