I’m trying to connect to balenaSound using a normal snapclient. For context, my Pi 3b+ has an internal IP of 192.168.1.67. I tried connecting to it using my Windows PC which was able to connect to a normal snapserver, but it wasn’t able to connect to this. Looking at multiroom-server’s logs, it did receive a connection from my PC, but it just kept repeatedly saying “New connection from 192.168.1.115” without actually connecting to it. This repeated about 5 times before it just stopped. There were no errors.
Doing some more investigating, I found that multiroom-client is connecting to multiroom-server using the ip 192.168.1.67. At first glance this seems normal, but the device shouldn’t typically be able to refer to itself by its internal ip address. It should either communicate over docker bridge mode using the ip multiroom-server or use host.docker.internal to resolve the Host OS ip. There’s some networking thing you guys have in place that’s doing this, but I don’t know how to disable it and get outside connections.
My end goal is to connect my docker container for LedFx to balenaSound so I can control my sound reactive LEDs too. Here’s the dockerfile (built for ARM): https://hub.docker.com/repository/docker/shirom/ledfx. I merged the two projects following: https://www.balena.io/blog/two-projects-one-device-turn-your-raspberry-pi-into-a-multitool/. However, it wasn’t able to connect.
How do I connect to this using a normal snapclient? It seems a bit weird that this would be so complex.