[bigbluesky5151]

Screen shots sent to [email protected]. No errors reported on the Console Tab.

[bigbluesky5151]

none. Prior updates were successful. No changes in environment since last update.

[bigbluesky5151]

of the five I’ve tried, the only one that had any plugins was Firefox. So its an (almost) no.

[bigbluesky5151]

After successfully using Edge to get to v2.5.2, same error as above occurs on all five major browsers (added Safari for good measure) when attempting auto update to v2.5.3. Any other thoughts I could troubleshoot?

[bigbluesky5151]

I had tried Firefox, Google Chrome and IE (all failed), but since you brought it up above, I figured I’d try Edge as well just to cover the bases. Sure enough, MSFT Edge worked. Thanks for your help!

[bigbluesky5151]

Hardware model: AC Toronto

Under System>Flash New Firmware>Auto Update (Radio)> [Click] “Check for Updates”;
“A new firmware updates is available (v2.5.2). Upgrade now?”? > [Click] “Upgrade”;
A progress bar appears showing “0%”. In about 20 seconds, that view closes and a message appears “Oops! Something weird happened!”.
[Click] “Ok”;
Any additional action: “This site can’t be reached”
[Power recycle]

[bigbluesky5151]

Per your above, the port forwarding 80 from the ER4 to the pcWRT did the trick, but only after I allowed ICMP traffic through. And I did get to the pcWRT subnet (from the ER4) when I adjusted the ‘next hop’ address of the static route to the ‘WAN’ IP of the pcWRT, not the native subnet gateway. That might explain why it didn’t matter if I have the firewall turned off.

• This reply was modified 3 years, 11 months ago by bigbluesky5151.

[bigbluesky5151]

Hi. Related to the above comments, I have a more general question. I have set the pcWRT behind a Ubiquiti ER4, and setup static routes between the two subnets (a 192.168.x, and 10.x respectively). The pcWRT routes out fine, and can ping into the Ubiquiti subnet (the 10.x) fine. The reverse isn’t working even if I turn off the iptables in the pcWRT. Even stranger is this: The pcWRT gets assigned a ‘WAN’ IP (10.x) from the Ubiquiti subnet, and I can ping that fine from both subnets; however, I can’t bring up the administrative interface on that ‘WAN’ IP in the Ubiquiti subnet, even though its a LAN IP from the ER4. This doesn’t make any sense to me, particularly since the last comment confirms port forwarding isn’t necessary. Basically, at the end of the day, I want to manage the pcWRT only from the Ubiquiti subnet. Thoughts welcome.

[Author]

Posts