Peculiar network, portforward, web server issue after new router installed
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Peculiar network, portforward, web server issue after new router installed
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi All,
need some help sorting out a peculiar port forwarding issue
I have purchased a new Archer AX55/3000 router to replace an older Archer VR2100
Basic set up is
Fibre connection, have a static IP via ISP, 192.168.20.x subnet, apache web server on port 80,443 for a couple of small business websites
I also host a few other things, jellyfin server, Storj nodes, Seafile server etc
I have port forwards setup for various PCs, but the main issues is the web server is on 192.168.20.196
When I was using the VR2100 everything worked fine EXCEPT for an issue with limited availability of port forward entries (no more than 11 was allowed, since RESOLVED with a factory reset) - "error code: 9812 The number of entries has reached its limit"
this issue made me go out and purchase the AX55...
With the AX55 router in place and everything set up on the same subnet, using address reservations and port forwards, everything else the same, the web server works fine initially BUT after 20 minutes or so, the web server stops working.
Chrome responds with a page error
This site can’t provide a secure connection [my website address] sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
this appears to be consistently after 15-20 minutes of router power on time, works fine for 15 minutes, webserver connections fail, reboot router, starts working, 20 minutes later web server off line again with the same ssl error.
I swap back the old VR2100, power on, everything works fine, for extended periods of time...
The AX55 did a firmware update pretty much immediately so that is up to date.
Is the AX55 interfering with the web traffic?
Not sure it is a port forward failure, I might have thought a certificate error of some kind perhaps - is there anything that runs on the router after 15 minutes that might be interfering with it?
I'm at a loss of how to proceed to resolve this...
at the moment i'm just use the old VR2100 in place and everything works fine (and now I can add extra port forwards), but I would like to be using my new router if I can
Much appreciate any insight you might have, let me know if any other information needed.
Cheers
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
You are right on the money with the uPNP comment, turning uPNP off on the router after it was playing up fixed the problem within 15 seconds...
I tried disabling the uPNP in the DCS camera but that seems to make no difference, i could still see it adding entries into the uPNP client list, from what I can see online it is common complaint about them
When I re-enabled the uPNP in the router, I had to wait a while (all very consistent with the original behaviour) but eventually the camera added a couple of entries, one initially for port 8080 internal to 80 external, and one for port 443, the latter took a bit longer to appear and as soon as it did it packed up again.
So we will go with the original plan and decommission that Camera.
I guess the only comment I could make for tp-link regarding the firmware going forward is it could be a good idea to have an option to block specific devices from adding uPNP entries, for these older, errant devices
Much appreciate your help
Cheers
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1236
Replies: 11
Voters 0
No one has voted for it yet.