No internet connection
  1. Home
  2. Support

Soundflow appears as offline

By Haumann Thomas @Haumann_Thomas
    2024-10-20 09:02:22.941Z

    Soundflow appears as offline

    System Information

    SoundFlow 5.8.3

    OS: darwin 23.2.0

    ProductName: macOS
    ProductVersion: 14.2
    BuildVersion: 23C64

    Steps to Reproduce

    1)just start the computer and try to open sounflow with a working WLAN Connection
    2) Reinstalling and ReBooting did not help
    3)
    4)
    5)
    6)

    Expected Result

    Soundflow should appear not offline

    Actual Result

    Soundflow appears not offline

    Workaround

    no

    Other Notes

    no


    Links

    User UID: 4DPspA3SDzQHvsfMFKZERd8EMVd2

    Feedback Key: sffeedback:4DPspA3SDzQHvsfMFKZERd8EMVd2:-O9d9Rzf-lCue5yPumq3

    Feedback ZIP: ScxcdhYQLI8j5kC00ijUQVC0r5bNNMBDShphpt2oKigrfXKQhcVZgY6K3weZRbhawwoAMoRyqxx2Am6IIrC7QL6ramFpdaFvyrfpNzb3oJcgF++0nnqqwr/VrYNA+XHfgekKQguDNRzuRpcuo4vDjY6qoreg/e2f4exOntWqlI7fp/pNHxJlwFoUt8vyP70f/Be043oqH3YWmtxDmHmuNo0zvJBXnGU7QG9ZN/0Ffz5UYVndEUqTo/WbTwHGbXbZ07Y5wvEsX+6LaJgaxjTIt/cMlftert0ypeJted+rjkrNlLwvgFNZT8iZXscfM14SReHGHhS3SwtLNhm7Jr4+rFrrzVCdua+YfWURb7PNokI=

    • 10 replies
    1. Hi Thomas,

      I'm sorry to hear that you're having trouble connecting to SoundFlow. I can indeed see some errors in your log files that relate to not being able to connect.

      I could also see some attempts at partially restarting SoundFlow, which didn't appear to be successful (at least not before you sent the report).
      In a case like this, rather than clicking the "Restart SoundFlow" button it may be better to quit it completely, ie. click the SF icon, choose Quit, and then re-launch it from Applications.

      Since there's not been any downtime on the servers, the most likely reason for this is that something on your network blocked your access to the servers. Are you connecting from behind a firewall or VPN by any chance?
      And does it work again if you restart SoundFlow (and possibly the computer) completely?

      1. HHaumann Thomas @Haumann_Thomas
          2024-10-29 13:46:18.454Z

          Hey Christian,

          thanks for your reply!
          I tried quitting, launching and rebooting the computer but nothing seems to help.
          Also there is no vpn active and deactivating my firewall did not help either...
          Do you have any idea how to fix this?

          Thanks in advance

          1. deactivating my firewall did not help either

            Did you fully restart your computer after deactivating your firewall?

            The next step to troubleshoot is to isolate if this is a problem with your local network, your ISP, or your computer.

            The easiest way to do that is to connect via your phone's 4g/5g connection instead, and see if things work. If they do, you know it's not your computer, but your network or ISP.

            1. If you find out that it's your network or ISP, you should try to connect to the ISP using default network settings, ie. make sure your router doesn't have anything custom set up.

              If the problems continue (assuming it worked over your phone), then the problem lies with your ISP.

              You should then contact them to say that they have a network configuration error somewhere. You can let them know that soundflow-4533b.firebaseio.com is unreachable for your computer. In Terminal, you can run this command, which should give you a list of the routers the connection goes through on its way. In your case, it looks like this is timing out instead of allowing the traffic to go all the way to the Google servers.

              traceroute soundflow-4533b.firebaseio.com
              
              1. You can also do a ping, which should give you results such as this if the network is functional:

                ping soundflow-4533b.firebaseio.com
                PING soundflow-4533b.firebaseio.com (34.120.206.254): 56 data bytes
                64 bytes from 34.120.206.254: icmp_seq=0 ttl=53 time=7.039 ms
                64 bytes from 34.120.206.254: icmp_seq=1 ttl=53 time=7.077 ms
                64 bytes from 34.120.206.254: icmp_seq=2 ttl=53 time=7.017 ms
                
              2. In reply tochrscheuer:

                I have the same problem. I use Starlink and so far it has always worked flawlessly. Starlink has a clear view and performs great. As I said, it has always worked great.

                Even after restarting Starlink, the problem was still there.

                1. Hi Stefan,

                  Could you send us a separate report so we can take a look at your log files? We had someone else using Starlink a few days ago who had problems. This is likely a bad routing configuration on Starlink's behalf.

                  1. I exported the debug data from the Starlink app and sent the log to info@soundflow.org with the subject “101124_Starlink_Debug log”.
                    Maybe that will help.
                    Would a static IP address solve the problem?
                    Best regards

                    1. In reply tochrscheuer:

                      Aand the sound flow log files have just been sent to you by e-mail with the subject “101124_Starlink_soundflow log”

                      1. Hi again,

                        If possible, please follow the steps here to open up a new support ticket, where we get access to all log files and configuration - please don't send as email as we will lack important information that way:

                        https://soundflow.org/docs/help#help-issue