NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Vernatronics's avatar
Vernatronics
Aspirant
Aug 24, 2013

Xplorer not working - connection was reset

Hi.
I installed Xplorer (AJAX File Explore) by super-poussin on my ReadyNAS Ultra 2 (firmware: RAIDiator 4.2.24), but cannot get it to work.

Each time I try http://192.168.1.170/explorer/ (192.168.1.170 is the IP of the ReadyNAS) I get the "The connection to the server was reset while the page was loading." error.

I did install PHP (version Version 5.4.16-0rnx2 by WhoCares) after installaing EnableRootSSH
The only other add-on installed is Logitech Media Server

I already tried the following without success:
- Search the web and this forum for a soltuion
- Remove and reinstall Xplorer
- Spend half a day making a complete back-up and performing a complete factory reset.

Another wierd syntom is the fact that when I add a share I receive a "The webserver configuration is invalid" message, but otherwise the share is added correctly.
I don't know if this has anything to do with the problem that Xplorer doesn't work.

Any help would be apreciated.

Thank you in advance
Vernatronics

5 Replies

Replies have been turned off for this discussion
  • Hi again,

    Is there anyone that can help me with this problem ???

    I tried everything and still get the "The connection was reset" error in Internet Explorer or FireFox when trying to access Xplorer (http://192.168.1.170/explorer/ or clicking on the "Open XPLORER File Manager" button from the istalled Add-ons in the ReadyNAS Frontview.

    Thanks in advance for any help on this.

    Regards,
    Vernatronics
  • The latest version of PHP WhoCares has posted is what's causing this issue IMHO. I've been running AjaXplorer with the prior PHP release with no issues. Now, various add-ons I use, that ALL utilize PHP are giving me this error with WhoCares latest PHP release. It may not be his fault, it may be a bug or an incompatibility in the latest PHP version, but I'm convinced it's PHP that is causing the issue(s).

    Unfortunately, I deleted the copy of the older release I had once I downloaded/installed the latest one, so have nothing to revert to.

    Also, I would post this issue in the PHP thread at his site: www.rnxtras.com.
  • gibxxi wrote:
    The latest version of PHP WhoCares has posted is what's causing this issue IMHO.

    For what it's worth, I'm using that recent version of the WhoCares addon without any problem. If the addon really is at fault, the root cause is probably just a misconfiguration; maybe looking at the error log will make obvious what needs to be changed:

    cat /var/log/frontview/error.log | grep -i PHP
  • Thank you for the reply.
    Now I have at least a starting point for trying to fix this.

    In the /var/log/frontview/error.log there are just "notice" lines containing PHP:
    [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 PHP/5.4.16-0rnx2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations

    But I also noticed errors relating to Xplorer directly, I think:
    [error] [client 192.168.1.100] [AjaXplorer] There was an error writing to log file - Error was 09-01-13 10:50:02\t192.168.1.100\tERROR\tshared\tAJXP_Logger failed to close the handle to the log file\n

    Could this be a bug in Xplorer (AjaXplorer)?

    Regards,
    Vernatronics
  • If I was getting the error I'm seeing with JUST AjaXplorer, I'd be inclined to agree. But I'm not.

    I'm getting the EXACT same error message for half a dozen add-ons, all of which are powered by (or use in some form) PHP. So it's something in the latest PHP addon that's either a misconfiguration or has the wrong credentials assigned to it, thus preventing it's use/execution. AjaXplorer has it's issues, but nothing that will prevent the UI from loading or basic functionality from working. I'm using the same add-on edition of that app now, as I was before I recently factory-defaulted my NAS, when it was working fine.

    Now there could be an issue with the recent "security" changes Netgear made to the 4.2.24 FW, but if that's the case, I wouldn't know where to look. Simply downgrading to the previous firmware release doesn't cure the issue, that I do know as I tried.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More