camilaacolide
Occasional Visitor
Hello,
I have a RT-86U with version 384.17 which has been working perfectly since forever. I run a Raspberry Pi in my LAN with Nextcloud, and I could access it from anywhere using my DDNS (inside and outside the LAN). But last week, I had to reinstall it from scratch due to a corrupted SDCard. Since then, I am able to access it using my DDNS from outside my LAN reliably, but when accessing it from inside my LAN, it works only half the time. The other half of the time it errors with "connection refused", both on port 80 and 443.
It shouldn't be a problem with NAT loopback in the RT-86U, but I am without ideas of what could be happening. The router is connected directly to the internet, and the DDNS IP and the route WAN IP are the same. Could somebody help me?
Thanks.
I have a RT-86U with version 384.17 which has been working perfectly since forever. I run a Raspberry Pi in my LAN with Nextcloud, and I could access it from anywhere using my DDNS (inside and outside the LAN). But last week, I had to reinstall it from scratch due to a corrupted SDCard. Since then, I am able to access it using my DDNS from outside my LAN reliably, but when accessing it from inside my LAN, it works only half the time. The other half of the time it errors with "connection refused", both on port 80 and 443.
It shouldn't be a problem with NAT loopback in the RT-86U, but I am without ideas of what could be happening. The router is connected directly to the internet, and the DDNS IP and the route WAN IP are the same. Could somebody help me?
Thanks.