× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: Cannot connect to frontview

Squazz
Aspirant

Cannot connect to frontview

I can't seem to get any connection to the frontview of my readyNas Pro 4.

I can (read: could) connect to it via SSH, and RAIDar shows my NAS with a lot of fine green dots, as well as the IP address.

But, when I try to connect to the IP address in either Chrome or Firefox, I get the following message:
Oops! Google Chrome could not connect to 192.168.40.78

Try reloading: 192.­168.­40.­78
(And similar in Firefox)

I just tried to perform a OS re-install via the boot menu, but that didn't give me anything. Other than removing the possibility for accessing the NAS via ssh 😕
RAIDar tells me that I'm running with the latest firmware, 4.2.26

Any ideas of what I can do to access my NAS via frontview? 🙂
Message 1 of 9
StephenB
Guru

Re: Cannot connect to frontview

What is the IP address and subnet mask of the PC?
Message 2 of 9
Squazz
Aspirant

Re: Cannot connect to frontview

The IP is 192.186.40.10

Subnet I can't remember, but will check back when I get home from job 🙂
Message 3 of 9
StephenB
Guru

Re: Cannot connect to frontview

I am thinking there's a typo. Did you mean 192.168.40.10?
Message 4 of 9
Squazz
Aspirant

Re: Cannot connect to frontview

Yes, sry 🙂 It was a typo 🙂

Subnet is 255.255.255.0
Default gateway is manually set to 192.168.40.1
Message 5 of 9
StephenB
Guru

Re: Cannot connect to frontview

Ok. That confirms that the IP addresses are all in the same address space. So that is not the problem.

What firmware are you running?
Message 6 of 9
mdgm-ntgr
NETGEAR Employee Retired

Re: Cannot connect to frontview

If you can SSH in, what is the output of

# tail -n 20 /var/log/frontview/error.log
Message 7 of 9
Squazz
Aspirant

Re: Cannot connect to frontview

RAIDar says 4.2.26 🙂

I can't do SSH anymore
Message 8 of 9
mdgm-ntgr
NETGEAR Employee Retired

Re: Cannot connect to frontview

Some files that the apache conf for Photos II depended on were missing which broke apache and hence Frontview.

Installing the Photos II add-on over the top of itself and triggering an OS extraction (but not reset of config) using a flag file appears to have fixed the problem.
Message 9 of 9
Top Contributors
Discussion stats
  • 8 replies
  • 2129 views
  • 0 kudos
  • 3 in conversation
Announcements