When a device has its Public Device URL enabled, the Balena VPN allows for port 80 to be exposed to the public internet.
This is a great feature, and I would like to be able to open up more ports. These could be configured in the fleet or device configuration, defaulting to the current behavior of port 80.
Yes, there are security implications for the fleet owner, but a warning message in the UI would be plenty.
Somewhat related - I would love to be able to expose port 443 instead of port 80. Forwarding insecure HTTP to the internet is somewhat risky compared to forwarding secure HTTPS. (FWIW it doesn’t work to serve HTTPS over port 80.)
Edwin Joassart set the status to No Status
For advanced use cases you we have a blog post showing how to use CloudFlare tunnels.
I believe it could solve your current issue by offering more flexibility than Balena’s Public URL (not just more port, but also custom domains, etc.)