Can not access network port of a remote Flatpak app

Hello there,

this is a rather weird issue I have and I have not found a solution. Not even in existing posts regarding similar issues like this one: Can flatpak access host's network port? I even ask “The AI (Claude Sonnet 4.6)” which … well … did not helped either.

Here is the situation:

Today I wired up the aarch64 build of my OpenSeeFace Wrapper App Facetracker and tested it on my Pi 400.

The app builds, and runs, all good. However in order to fully test it I have also to run any type of VTubbing Software. But all of them are Windows only and of course x86_64. My Pi 400 is not powerful enough to run Fex-Emu + Steam + VTube Studio + Facetracker to test things locally.

So the only logical solution is to run the VTubbing App on my Desktop and connect to the Facetracker instance running on my Pi 400. This does not work. The port is claimed to be closed. According to netstat (running on the local device) and nmap from a remote device. No tracking data is received by VTube Studio on my Desktop.

I run the tracker on all network interfaces 0.0.0.0 with port 11573. Over on my Desktop I set VTube Stdio to access the IPv4 of my PI 400 at my home. Both devices running on the same network.

My app already uses `–share=network` but I am not sure if this also allows to open ports and let other apps access to it.

Same for the x86_64 build on my desktop. I can’t access the port form my Pi 400 either. However running VTube Studio + Facetracker on the same machine works fine. While you have to tell VTube Studio to access 0.0.0.0 11573 so it also talks to Facetracker using the network as well.

Am I missing something here?

Development Flatpak Manifest an be found here: ZRayEntertainment/Facetracker: Wrapper UI for OpenSeeFace's facetracker - Codeberg.org

Many thanks in advance,

Vortex.

Nevermind. All good. All working

I missed that my app wrapps a UDP application which means I have to SEND the data from my flatpak. They are not RECEIVED … geeeez I feel so silly rn … remote tracking works now. Sorry for bothering you.