ER8411 - some websites no longer reachable after update to 1.3.1

Dear All,
anyone else experiencing problems to reach (some) websites and services after update to 1.3.1?
Updated last Sunday and since then some websites and services are no longer reachable, e.g., Miele SmartHome (this from LAN to LAN), OPNsense updates, some of my office resources etc. (LAN to WAN). Some sites take a loooong time to load.
Everything was easy with the pervious version 1.2.? (Can not remember what the ? was).
Went through the configuration, everything seems ok. DNS is 1.1.1.1/1.0.0.1.
Anyone else? Any ideas?
Thanks!
Br's Thomas
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

So, it is no longer reachable. You verified this by seeing that the devices cannot connect to the Internet?
What else did you do to verify that some websites are not working?
OPNsense? What is your diagram? Is there a second router?
No similar reports since 1.3.0 and 1.3.1 were released.
Website is not reachable, you should examine the DNS at least. More details should be provided before knowing what happened. At least from the reports from others do not reflect this. Likely to be a network environment issue.
- Copy Link
- Report Inappropriate Content
I updated to 1.3.1 and could not access my servers via URL anymore so I had to roll back to 1.2.3. It's like if NAT loopback was removed or not working.
I made a thread (https://community.tp-link.com/en/business/forum/topic/820170) last thursday but got nothing from TP-Link...
You can roll back to 1.2.3 via SSH.
Once logged into your gateway :
- type enable
- type roll-back
- Press Y
Your gateway should reboot and rollback to the firmware you had before upgrading to 1.3.1.
- Copy Link
- Report Inappropriate Content

So, it is no longer reachable. You verified this by seeing that the devices cannot connect to the Internet?
What else did you do to verify that some websites are not working?
OPNsense? What is your diagram? Is there a second router?
No similar reports since 1.3.0 and 1.3.1 were released.
Website is not reachable, you should examine the DNS at least. More details should be provided before knowing what happened. At least from the reports from others do not reflect this. Likely to be a network environment issue.
- Copy Link
- Report Inappropriate Content
Thanks - and sorry for not having been precise!
So, my post is already a couple of days old - and, fortunately, all services are back up since this morning.
What did I do to resolve? Of course I checked all DNS entries, changed to different providers and then returned to my original values, i.e., 1.1.1.1 and 1.0.0.1. Or the router address 192.168.0.1. Success? No. Have restarted the router several times over the past days: no improvement. Also restarted switches, no impact. Yesterday evening I was so frustrated that I simply took everything offline/powered off and restarted/powered back on this morning. It worked, everyting came back. I however saw in the Omada App that (some) devices were re-adopted.Perhaps something went wrong in the communication between the router and the rest of the infrastructure.
On the errors I have seen: Apple App store worked, Samsung/Android update services didn't. Windows update? No. Smart home solutions such as Philips HUE? No service. Miele Smart Home? No. Garden watering system (Gardena)? Yes. Connectivity to VoIP provider? No. LG smart devices? Yes. "No" means either an error message from the App such as "No connection/service unreachable" or just an animation /(running circles, ...). Interestingly, all smart home services were reachable from outside. But not if connected to the internal LAN/WLAN.
OPNsense: Using OPNsene as transparent bridge beween the router and the rest of the network. No routing or other functionality. Just sitting there and scanning traffic. The update function did not work, just an endless animation of a rotating circle.
Web pages: some public pages opened immediately, others presented content veeeeery slowly, came up with a "time out" or simply an empty page.
The only constant element over these past days was that those services which worked, always performed and those which didn' t open, remained unfunctional.
So, I assume that was a hick-up somewhere in the network causing this behaviour.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 501
Replies: 3
Voters 0
No one has voted for it yet.