Device suddenly stopped working - trouble opening ports

[Doodles20]

Hi, I have full fibre and one of my devices on my network (microchip catflap hub connected by ethernet) has suddenly stopped working and is not connecting to the network after working fine. The device is fine as it actually works if I connect it to my phone through tethered ethernet (mobile data connection and my network WiFi.

I'm not sure if the issue is my broadband connection or the router which is an Eero 6.

One of the things the manufacturer has suggested is to check that there are no firewall restrictions and that ports HTTPS – 443 and/or MQTTS – 8883 are open outbound.

Using a port checker, it seems those ports are closed and I'm having trouble opening them. I've added a reservation on the catflap hub in the Eero app for port 443 but it still seems to be blocked on the hubs IP and my WAN IP.

Has anyone any suggestions? Am I opening the port correctly?

[mandisa1-TT]

You are most welcome and thank you so much for updating us the issue has now been resolved:)



Have a lovely day and take care.
 

[Doodles20]

Hi, thanks for your help. I was going to have a look at the DNS when I got back from work last night, however, when I got home I found the hub was working fine and connected to my network. I haven't done anything so I don't know what's changed. It had been offline for over a week and was when I left the house yesterday. 

Still seems fine at the moment so will keep an eye on things. Thanks again for your help.

[mandisa1-TT]

Hi there @blodwynblod Thank you so much for sharing, As we have been getting a few number of customers yesterday experiencing this issue.

[blodwynblod]

Hi, I dont know if it is anything to do with your problem but yesterday afternoon my sky box suddenly could not connect to sky through the sky router sagecom wifi hub most other sites I tried were ok I remembered a similar incident a year or two back and checked the dns servers in the router I changed them from 79.79.79.79 to googles public server 8.8.8.8 and the box connected immediately after rebooting( I had already tried rebooting alone ) I have since changed to the Open DNS public servers and have had no trouble since

regards

B

[Philile-TT]

Thank you for the support @KeithFrench 

[KeithFrench]

Hi @Doodles20 

@Philile-TT has asked me to help you. All ports are open in the outbound direction, so port forwarding is of no use. You cannot change the IPv4 firewall, so that won't be the case. If this worked before, the most likely cause of the problem is that your eero, via the Full Fibre network, has been allocated a new WAN IP address. However, normally, that won't have any effect on the outbound direction. Please can you feed this back to their support team for further advice on how this is supposed to work, in case I have overlooked anything.

Just in case, there are currently some issues with the TalkTalk DNS servers, which might cause this. If it is the cause of your problem, you can get around this by using a custom DNS server in the eero of 8.8.8.8 and 8.8.4.4. However, to do this, you need to disable advanced security and ad blocking. However, if you do that and you use HomeSafe or KidsSafe, then changing the DNS will mean these won't work as they require the TalkTalk DNS to do so.

[Philile-TT]

Hey @KeithFrench any advise on this?