Dynamic DNS Giga Hub 2 NOIP stopped working

I-Vlad
Contributor II

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

 

0 33 570
33 REPLIES 33

 

Giga Hub 2.0 Firmware 3.11.6.1 Breaks Plex Local and Remote Playback Please Review this Bug 
The temp fix seems to be swapping the modem out to one that hasn't had the firmware updated. I myself swapped the modem and I now have firmware 3.11.3 which works perfectly. My Plex was working flawlessly for months. Since 3.11.6.1 came out it broke it.




Changing the modem to a new one with older firmware will only work temporary, as this issue seems to be related to the latest firmware of the modem.

Once the new modem updates to the latest firmware, it will stop working again.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

Unfortunately I'm aware of this. I myself have talked to a Bell employee who is an avid Plex user and they don't have this problem on Giga Hub 1.0 it seems. I requested a downgrade but Bell said no. 

 

Potential work arounds for when the firmware updates and Plex breaks again is a separate router using PPPoE or Advanced DMZ. These are just what I've been able to gather from the community. I have not tried it so I can't speak to the success. Last ditch effort is bypassing the Bell Giga Hub 2.0 all together which others have done but I really don't want to attempt. Swapping providers is not in the cards either as I have 8Gbps up and down and no one offers that..... YET

Zare
Contributor

I've been running into this issue myself for similar reasons. NoIP stopped functioning completely and refuses to connect; the issue seems to have happened around the same time as everyone else here; port forwarding just completely stopped functioning for me as well though. I was using a port tester to check and regardless of which port I opened, they all failed.