I went from the R9000 latest stock firmware to r51937. Flash went well. I changed the user and password upon prompt without issues. I am able to ping the router gateway and all devices are online, however, the GUI goes unresponsive. After about 10-20 minutes, I am able to hit the GUI again but after a few seconds of browsing the interface it goes unresponsive with ERR_CONNECTION_RESET.
I did the 10 second factory reset, put in my new login creds and entered but again, after a few seconds the GUI went unresponsive. Tried multiple browsers with private mode also, no luck.
Code:
curl -v 192.168.1.1
* Trying 192.168.1.1:80...
* Connected to 192.168.1.1 (192.168.1.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 192.168.1.1
> User-Agent: curl/7.86.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
This usually happens when the user/password is entered incorrectly several times.
I get exactly the same message when my IP is blocked.
Code:
curl -v 192.168.1.1
* Trying 192.168.1.1:80...
* TCP_NODELAY set
* Connected to 192.168.1.1 (192.168.1.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 192.168.1.1
> User-Agent: curl/7.68.0
> Accept: */*
>
* Recv failure: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
* Closing connection 0
curl: (56) Recv failure: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
If the httpd would crash and stop then there would be a different message.
So you and your browser are surely doing something wrong.
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Sat Mar 11, 2023 17:01 Post subject:
try the older 51935 or even 51887 im still on it and waiting the big WIP to settle down...but i can see some positive R9000 reports even with 51937... so no idea what's happening on your side....more details will put more light on the problem...
also try to switch to https web interface access as most of the new edge browsers prevent the http use
and force https... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Thank you all for the replies. I could not enable SSH to check the block list, unfortunately. The access was denied almost immediately.
Oddly enough, both of my M1/ARM Mac's (MacStudio and MacBookPro) could not access the GUI. I then tried my old Intel Windows 11 machine with IE, and it worked without issues.
I have no idea why this is the case. Once I was in, I enabled ssh and checked the block list but found no IP's. Very confusing issue for me but I'll continue to access the GUI via the Windows machine until I can pinpoint the problem.
The blocked IPs are only blocked and stored for a few minutes.
So you have to look when you have no access with the other device.
The description fits anyway, first works, then 10min not, works again, then not again etc.
Edit: another possibility would be to activate syslod in the "services" tab.
Then you could look in /tmp/var/log/messages if the httpd process crashes.
If you lock yourself out with wrong password the timeout is 5 minutes and it resets this timer if you are impatient.
However, sounds like a browser issue. Configuration, addons extensions plugins, most commonly history or cache.
Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.