Dynamic DNS Giga Hub 2 NOIP stopped working

[I-Vlad]

Hi All,

Anyone experience the same issue with NOIP? Tested with CURL and all worked ok giving nocng response. Submitting from the setting giving an error "Cannot be saved. Try again later.

My modem was recently reset, could that cause that issue?

Thanks

[Vanadiel]

If it was reset, you could have been assigned a new public IP as they are not static.

[I-Vlad]

Yes it was likely updated, but when I try to set it up I get an error.

[BellPatricia]

Hi there @I-Vlad 

Thank you for reaching out to the Bell community 🙂 

We just wanted to check in to see whether you’re still seeing that error message appear in your modem GUI. If you are, could you please try performing a full factory reset to see if that helps?

Please keep us posted.

@BellPatricia 

[I-Vlad]

Hi Patricia,

Unfortunately that didn't help after I've reset to factory defaults. To my surprise the modem retained my WIFI settings and I didn't have to change my network name. That suggests some settings stored at Bell's side and automatically reapplied .

I also ran into another problem: my port‑forwarding rule for 443→443 stopped working. Several forum posts indicate that external ports 80 and 443 are blocked on residential service. Can you please confirm whether these ports are restricted for residential customers or another issue?

Thanks, Vlad

[SabSnake]

I've had issues with Bell and my Cloudflare DNS/Website hosting ( linked to my domain ) and parsec/media server issues lately. Past 3 weeks I think now?
My internet went out, then back on and my stuff just  stopped working, none of my fixes worked like previously.

TL:DR: Replaced the Giga Hub 2.0 Router with a new one, it worked/fixed it. Then internet went out then back on and now I'm having the exact same issues.

Hoping for input from Bell. I don't think they understand what I was trying to explain to them as well.

[BellPatricia]

Good day @I-Vlad 

Thank you for your reply and for all of the steps you have tried 🙂

Allow me to review the modem error further from here, and I will get back to you with an update once we know more.

Regarding port forwarding, can you clarify more about what you mean by 'my port‑forwarding rule for 443→443 stopped working.' - For example, is there an error or anything in particular that is happening?

If you continue to have trouble  check out this thread Port forwarding 443, 80 and 8123 and be sure to join the conversation so the community can help.

@BellPatricia 

[SabSnake]

Anyone know why this keeps happening? Don't want to have to keep getting new modems.

[I-Vlad]

Hi @SabSnake,

Think my issue with NOIP and 443 port forwarding is quite the same. On Apr 21, 2026 my fiber got cut off and a technician came to repair it. The issues started right after. Probably got routed thru another backend equipment.

[Vanadiel]

Looks to me, based on the logs, that a modem firmware update was forced followed by a deactivation of UPnP IGD services.

Could be a firmware bug, or an intended change. Without UPnP IGD automatic port forwarding will not work and you will have to manually open ports as needed.

link. 

[BellPatricia · Accepted solution]

Hi everyone 🙂

Thanks again for bringing this to our attention.

We have shared the details with the appropriate team This is now under investigation, and our teams are working towards a resolution. We’ll keep you updated as soon as new information becomes available.

@BellPatricia 

[Jasmike]

Hello, 

is there any update from the appropriate team ?   I have the exact same issue with my No-IP service and I cannot get it to work. 

Thanks

[SeanC]

I have same and see many people on Reddit. Port forwarding anything to 443 locally doesn't work.

[SeanC]

My issues also started on April 21. Port 443 stopped working. Plex stopped working.

[Vanadiel]

Port 443 is default port for HTTPS connectivity.

No-IP's Dynamic DNS service uses specific ports to allow client devices to securely communicate IP address changes to its servers. 

• Port 443: This is the standard HTTPS port used for secure, encrypted updates to No-IP's servers.  When a Dynamic Update Client (DUC) sends an update request via HTTPS, it connects to https://dynupdate.no-ip.com/nic/update on port 443. This is the recommended and most secure method. 

• Port 80: This is the standard HTTP port used for unencrypted updates.  Clients can send update requests to http://dynupdate.no-ip.com/nic/update on port 80. 

• Port 8245: This is an alternative HTTP port specifically designed to bypass transparent HTTP proxies that might interfere with or block requests on the standard port 80.  It provides a way for the update client to connect when network conditions prevent the use of port 80. 

It is not necessary to open any of these ports (80, 443, or 8245) for inbound traffic on your router's firewall for the update process to work.  The Dynamic Update Client makes an outbound connection from your network to the No-IP servers.  Your firewall must, however, allow this outbound traffic. Port forwarding is only required for the specific services (like a web server on port 80 or a camera on port 8080) that you want to access remotely using your No-IP hostname. 

It should still work, but access to your local LAN servers from outside your network might not work anymore if port forwarding is broken.

Technically speaking Bell does not allow web services to be run on home internet plans, so it is possible this is an update on their end to prevent such activities. Could also be a bug in the modem firmware, as I mentioned before.

Only Bell would be able to confirm the root cause of this issue.