WZR-HP-AG300H '19.07.0' Error XHR request timed out

Hello-
I recently updated by buffalo WZR-HP-AG300H from an older release to 19.07.0. In doing so, i updated to the ath79 build from ar71xx. I used sysupgrade with the flag to keep none of the configuration files, and reconfigured the unit from scratch.

I've found that accessing the luci web interface, page loads are very slow and often get 'Error XHR request timed out'

I found a reddit thread indicating a workaround of changing 'Connection reuse' to be 0 in the luci settings:

This appears to work for now, but I don't see mention of this timeout in the forums, and am interested in if this workaround is the correct approach to take, or working around some other problem.

Many thanks
Camden

Bulid info below

root@router01.'dryhollow':~# cat /etc/openwrt_release 
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='19.07.0'
DISTRIB_REVISION='r10860-a3ffeb413b'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 19.07.0 r10860-a3ffeb413b'
DISTRIB_TAINTS=''
root@router01.'dryhollow':~# cat /etc/openwrt_version 
r10860-a3ffeb413b
root@router01.'dryhollow':~#

I have the same situation with the latest snapshot on my Netgear R7800 router:

NAME="OpenWrt"
VERSION="SNAPSHOT"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt SNAPSHOT"
VERSION_ID="snapshot"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r12138-1e3bfbafd3"
OPENWRT_BOARD="ipq806x/generic"
OPENWRT_ARCH="arm_cortex-a15_neon-vfpv4"
OPENWRT_TAINTS="no-all busybox"
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt SNAPSHOT r12138-1e3bfbafd3"

When I access the root (/) of the luci web interface, I am ALWAYS getting the "Error XHR request timed out" and this started happening like about 3 weeks ago.

I've noticed that problem but only as long as my web browser is not trusting router web server certificate. Try switching to HTTP or issue certificate/add self signed to trusted.

Thanks for the advice, but the problem is elsewhere. If you are keen to know, feel free to follow this thread from the link below:

It's still being investigated and I am trying to help..

1 Like