Challenge at the port entrance...
Challenge at the port entrance...
This issue occurs in Canada using Videotron's Helix 2 modem/router. I've configured the Helix in Bridge mode so all routing goes through my TP-Link Deco M4 mesh network. I'm attempting to run BubbleUPnP, which allows secure access from outside for music and video streaming. The router is set to open necessary ports, but BubbleUPnP and its developer say that if ports are open and Windows firewall also permits them, access should work. Something still prevents me from connecting. Any suggestions or details I can provide would help.
Questions:
- Have you checked the router's logs for errors?
- Are there any recent firmware updates or changes to the network settings?
- Is the firewall on Windows blocking specific ports despite the router configuration?
- Have you tried using a different port or port range?
- Can you confirm that BubbleUPnP is running and accessible from outside?
Thanks!
It could be that your ISP is restricting access. They might close certain ports to safeguard customers unfamiliar with networking or to block non-commercial hosting. You may also be using a shared public IP address (CGNAT). Verify your router's external IP address. Is it publicly accessible, or does it fall within a private range? (192.168.x.x, 172.16-31.x.x, 10.x.x.x)
Refers to public network range. It would be private if it matched 192.168.x.x, 172.16-31.x.x or 10.x.x.x, preventing external access. A public IPv4 address is beneficial, yet your ISP might block ports 58050/58051. How did you configure port forwarding on the router? It should look like 173.178.x.x:5805x -> <machine-ip>:5805x. You can verify open ports using a scanner such as https://www.whatismyip.com/port-scanner/, and ensure BubbleUPnP is active.
It seems the setup is typical. The focus is on identifying the values you shared. The internal IP should match the machine running BubbleUPnP. Both internal and external ports need to align with ports it uses, like 58050 or 58051. You likely want to add separate rules for each port—just click the question mark next to "Need to forward multiple ports" for guidance. From a security standpoint, limiting access to only 58051 makes sense if it handles HTTPS.
Initially, it's possible your ISP is restricting these ports. If you have another computer, first verify those ports are accessible from that machine using the internal IP of the Bubble device. If that fails, the Windows firewall might be blocking them and needs fixing. If everything works locally, ensure Bubble displays the correct public IP address—this should match the router's external IP.
You can check the public IP address through your router settings or using an online service. To verify Bubble's information, look up the associated public IP in your network configuration.
The site shows the same IP address you see on your router's WAN connection.