NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 problems after upgrade to 6.10
I remotely upgraded one from 6.9.5 to 6.10 this week and lost remote access.
The dynamic DNS address is working correctly for all other services
When I had physical access I did the thre...
937carrera wrote:
Apr 30 12:35:38 Nas-102 apache2[2173]: [ssl:warn] [pid 2173] AH01909: ::1:443:0 server certificate does NOT include an ID which matches the server name
Apr 30 12:36:02 Nas-102 apache2[2177]: [cgi:error] [pid 2177] [client 111.222.333.444:52684] AH01215: Connect rddclient failed: /frontview/lib/dbbroker.cgi, referer: http://111.222.333.444/admin/index.html
It does look like it might be a consequence of an uplift in security, though it seems odd that it would only show up remotely. Did you try a local connection using the secondary port?
You could also try regenerating the key by changing the name on the https settings page, and clicking "Apply". If the key host already matches the hostname, then try changing it back.
Setting up a PC on the NAS site that has some form of remote desktop installed (google remote desktop perhaps) might be worth doing, as it would give you another path to the NAS.
BTW, I was able to find your earlier post - it was caught by the automatic spam filter. I released it.
Many thanks for finding and releasing my "spam", I'm not sure what I did deserve that :)
Anyway, back to the original issue and your suggestion to do a simple LAN connection. A good idea by the way.
I tried connecting to the RN104 specifying port 443 and "55555". Both worked and I was prompted for the security exception each time
On the RN102 I was prompted as expected on port 443
I received the partially obfuscated error page below on FF when using "55555"
Unable to connect
Firefox can't establish a connection to the server at 192.168.xxx.yyy:55555.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
This is the entry in the http log
May 01 16:51:46 Nas-102 apache_access[2412]: 192.168.xxx.zzz "GET / HTTP/1.1" 302
Isn't a 302 a moved /redirect http error code so the replacement URL should be provided to the requesting browser ?
Seems to be begining to look more like a failure of the second port to respond correctly than an SSL issue now ??
937carrera wrote:
I received the partially obfuscated error page below on FF when using "55555"
Unable to connect
Firefox can't establish a connection to the server at 192.168.xxx.yyy:55555.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.Seems to be begining to look more like a failure of the second port to respond correctly than an SSL issue now ??
Yes.
I've confirmed that the second https port won't connect on my RN526x also. I checked this with both Chrome and Firefox. Reconfiguring the second port doesn't change the behavior.
JohnCM_S / OOM-9: Can you log a bug for this (and hopefully provide a hotfix).
937carrera: I suspect forwarding 55555 to port 443 of the ReadyNAS in your router will provide a work around.
Woohoo, I found a bug :)
Seriously, many thanks for your help in identifying this Stephen, I know you do a lot around here helping people, it's really appreciated.
Now I just need to go away and figure out how to use port triggering on my Netgear router. I'll be back later
Thanks
I have concluded that my DGND3700v2 router cannot provide external port triggering combined with port forwarding, and as I don't want port 443 open to the world I am content to wait for the hotfix.
It's possible that the router at the remote location can do this so I may try that tomorrow.
While wandering around reading the logs I have spotted a new error occurring in the readynasd log, for example, this is the first occurrance and it arose in the reboot following upgrade to 6.10.0
Apr 25 23:16:10 Nas_102 readynasd[2673]: Failed to call method GetUnitFileState: No such file or directory
It occurs at random times from hours to seconds and also at regular 5 minute intervals.
Any ideas what this means - happy to create a new thread if that is preferred, or it may be related ???
.
937carrera wrote:
Apr 25 23:16:10 Nas_102 readynasd[2673]: Failed to call method GetUnitFileState: No such file or directory
I don't know what this is either, perhaps JohnCM_S or OOM-9 will know.
StephenB wrote:
937carrera wrote:
Apr 25 23:16:10 Nas_102 readynasd[2673]: Failed to call method GetUnitFileState: No such file or directory
I don't know what this is either, perhaps JohnCM_S or OOM-9 will know.
Thanks for that.
I have reinstalled the RN102 in its usual location and set up the port triggering / forwarding as suggested as that router has additional capabilities. It worked.
This is a workaround, not a solution, so I would still hope that Netgear can fix this properly.
As I have not seen any response in the thread or received a PM what's the best approach for logging / following up on bugs?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
