Port forwarding 443, 80 and 8123

[belukrin]

Any ideas on how to open port 443,8123 and 80 on bell U4000

[ZaneP · Accepted solution]

Hi @belukrin 

I assume you're using the Bell Home Hub 4000.

To port-forward:

• log into the Home Hub with your admin password
• click on Advanced Tools and Settings
• click on Port Forwarding

Enter your rules for the ports you want to manage. The screen will look like this:

[belukrin]

But are these ports are open at Bell: 443,8123 and 80

[ZaneP]

If you want to open a port on the Home Hub you need to use the dashboard.

Whether or not Bell will allow you to have these specific ports open is another issue. 80 and 443 may be problematic. 

[everwisher]

Nginx web server set up well and can be accessed within LAN by IP address.

With internal port 80 being forwarded to external port 80, my web server cannot be accessed;

However, with internal port 80 being forwarded to external port 81, my web server can be accessed once again! 

This is ridiculous! Bell is forcing its users to buy VPS in order to set up their own website while claiming it's not blocking any ports!

[BellPatricia · Accepted solution]

Hey there @everwisher. Thanks for reaching out to the Bell Community.

We've tested on our end, and have no issues with port 80. 

To test a bit further we recommend you try a PPPoE connection straight from your webserver. This will allow your server to pick up a public IP address so you can bypass the need for port forwarding. 

Let us know if port 80 works for you using that method.
- Patricia

[everwisher]

Let's be candid and straightforward.

After communicating with Bell technician over phone and a lot of test from my own side, I can confirm that Bell does NOT block 80 and 443 from their side. That's why when you set up port forwarding on port 80 and 443, and then test the port from external terminals, yes, they are open. However, external access to web server listening on 80 and 443 stays unresponsive still.

But when I set up an alternative router, put it in the DMZ zone and dial PPPOE directly from it, everything turned out to be working perfectly. That being said, the restrictive policies was imposed on the Home Hub 4000 router. This also explains what the Bell technician said: "things have a limit, and I'm not authorized to say it."

Nevertheless, imposing restrictions on users without explicit disclosure doesn't prove your integrity as a giant cooperation. Period.

[ZaneP]

Hi @everwisher 

Your web server setup knowledge is obviously far greater than mine. Just wondering if self-hosted servers may be problematic for Bell customers like us: personal/family "retail" users. 

What gear are you using to connect to the WAN: a Bell HomeHub standalone?; a Bell HH with your own router?

Did you set up port-forwarding for 80 and 443 on the Home Hub or on your own router? 

A number of people on this forum and elsewhere have reported hit-or-miss results with port-forwarding. 

Perhaps a VPS would be the better solution if the web server is a must-have for you?

[ZaneP]

So your web server is functioning properly? That was the goal, and it's good news. 

The Home Hub 4000 is a Sagemcom gateway modem and its firmware has been customized heavily for Bell, afaik. It's aimed at the "average customer", whose needs are straightforward. Others add their own router into the mix, as their needs are more complex. What Bell chooses to disclosure to retail subscribers like us may not be satisfactory but it's beyond our control.

(I don't work for Bell, I'm just a customer)

[pooll]

Hello,

I would like to know if UDP port 443 is open on Bell Internet.

I use a VPN for work, and the company's network administrator says that UDP port 443 needs to be used.

I would like to know if it is possible to open UDP port 443 if it is blocked.

I look forward to your helpful response.

Thank you.

[Vanadiel]

Port 443 is default port for HTTPS. As long as you initiate a VPN connection it will be open for communication.

[RogueAgent]

I have a Ubuntu server running some personal and association websites (non-profits). The websites are managed by Plesk. The server was working perfectly through another ISP yesterday. I now have Bell 1.5 fibe service, on a GigaHub 4000.

I finally got ADMZ on the GigaHub working properly. Time will tell if it is stable.

ISSUE: Port checkers confirm that all necessary ports are open, EXCEPT 25, 80, 443, and 2525. Bell says they do not block ports. The server was working perfectly — websites accessible and able to send email — yesterday. 

For example, I can access the Plesk control page on port 8443, and can RDP into the server on port 3389. 

Why are ports 25, 80, 443, and 2525 blocked? How do I get them unblocked? How do I get around these blocks?

This isn't a commercial endeavor, so I didn't think we needed a business internet service. This is also my home internet service.

I would prefer to run my own SMTP server, but if I have to use Bell's, how do I configure it to still be from my domains?

SIDE ISSUE: I tried to set up a PPPoE connection, but kept getting "connection failed". I am using the user ID and password from the letter enclosed with the GigaHub. Any hints on how to fix this?

[dks]

Thank you for your questions. Unfortunately the information you seek is beyond the scope of this forum. I encourage you to ask your questions on DSL Reports or r/bell on Reddit, where you will find more appropriate assistance. 

[dks]

This thread may have useful information for you, as well. If you want fully unblocked ports, that is available through a business account. A static IP from Bell is an additional charge, if that is what you need. 

[RogueAgent]

The short answer is, "THOSE PORTS ARE BLOCKED BY BELL CANADA".

Bell will not open them on residential service. Period.

• you need a business account to use those ports: +30 $/mo
• you need a static IP if you want to easily run a webserver: +35 $/mo

Thanks. I'll go elsewhere.