I accidentally removed Apache from my ReadyNAS and no longer have an admin page.

Question

Like the title says, I was playing around trying to get OwnCloud working and without thinking did an apt-get purge and apt-get autoremove to Apache2 and related software. I was able to reinstall Apache and it's running, but the admin files from /var/www are gone. Is there any way I can extract them out of the firmware .img file? Can I download it from somewhere? Is there a procedure to restore it from the firmware image without deleting my data? Thanks in advance!
&nbsp;
Also, somewhat on topic, why does the ReadyNAS repo have such old apps on it? The default OwnCloud that it installed was version 5.x. 10.1 is current on OwnCloud's website.

StephenB · Answer

greasyrainbow&nbsp;wrote:
You're right, with Apache2 installed again I only see /var/www/index.html with guest permissions too. Can you look in your /etc/apache2/sites-available/ and sites-enabled/ for me? I have a feeling the ReadyCloud UI is somewhere in there.

root@NAS:/etc/apache2/sites-enabled# ls -als
total 12
0 drwxr-xr-x 1 admin admin  72 Mar  8 19:44 .
0 drwxr-xr-x 1 root  root  240 Jan 27 06:16 ..
4 lrwxrwxrwx 1 root  root   36 Mar  8 19:44 000-fv-http -&gt; /etc/apache2/sites-available/fv-http
4 lrwxrwxrwx 1 root  root   27 Jan 27 06:16 000-fv-https -&gt; ../sites-available/fv-https
4 -rw-r--r-- 1 admin admin 451 Mar  8 19:44 001-fv-https2root@NAS:/etc/apache2/sites-enabled# cat 001-fv-https2&lt;IfModule mod_ssl.c&gt;NameVirtualHost *:50020Listen 50020&lt;VirtualHost _default_:50020&gt;Include "/etc/frontview/apache/ssl.conf"Include "/etc/frontview/apache/defaults.conf"Include "/etc/frontview/apache/http-share-redirect.conf"Include "/etc/frontview/apache/fv-admin.conf"Include "/etc/frontview/apache/Shares.conf"Include "/etc/frontview/apache/apps-https.conf"Include "/etc/frontview/apache/READYDROP.conf"&lt;/VirtualHost&gt;&lt;/IfModule&gt;root@NAS:/etc/apache2/sites-enabled#
root@NAS:/etc/apache2/sites-available# ls -als
total 24
0 drwxr-xr-x 1 admin admin   92 Jan 27 06:16 .
0 drwxr-xr-x 1 root  root   240 Jan 27 06:16 ..
4 -rw-r--r-- 1 root  root   692 Aug  2  2012 default
8 -rw-r--r-- 1 root  root  7251 Aug  2  2012 default-ssl
4 -rw-r--r-- 1 admin admin  379 Oct  9 15:53 fv-http
4 -rw-r--r-- 1 admin admin  374 Oct  9 15:53 fv-http-admin
4 -rw-r--r-- 1 admin admin  412 Oct  9 15:53 fv-https
&nbsp;
root@NAS:/etc/apache2/sites-available# cat default
&lt;VirtualHost *:80&gt;
        ServerAdmin webmaster@localhost

DocumentRoot /var/www
        &lt;Directory /&gt;
                Options FollowSymLinks
                AllowOverride None
        &lt;/Directory&gt;
        &lt;Directory /var/www/&gt;
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        &lt;/Directory&gt;

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        &lt;Directory "/usr/lib/cgi-bin"&gt;
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all
        &lt;/Directory&gt;

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

CustomLog ${APACHE_LOG_DIR}/access.log combined
&lt;/VirtualHost&gt;
root@NAS:/etc/apache2/sites-available#
root@NAS:/etc/apache2/sites-available# cat default-ssl
&lt;IfModule mod_ssl.c&gt;
&lt;VirtualHost _default_:443&gt;
        ServerAdmin webmaster@localhost

DocumentRoot /var/www
        &lt;Directory /&gt;
                Options FollowSymLinks
                AllowOverride None
        &lt;/Directory&gt;
        &lt;Directory /var/www/&gt;
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        &lt;/Directory&gt;

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        &lt;Directory "/usr/lib/cgi-bin"&gt;
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all
        &lt;/Directory&gt;

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined

#   SSL Engine Switch:
        #   Enable/Disable SSL for this virtual host.
        SSLEngine on

#   A self-signed (snakeoil) certificate can be created by installing
        #   the ssl-cert package. See
        #   /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
        #   If both key and certificate are stored in the same file, only the
        #   SSLCertificateFile directive is needed.
        SSLCertificateFile    /etc/ssl/certs/ssl-cert-snakeoil.pem
        SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

#   Server Certificate Chain:
        #   Point SSLCertificateChainFile at a file containing the
        #   concatenation of PEM encoded CA certificates which form the
        #   certificate chain for the server certificate. Alternatively
        #   the referenced file can be the same as SSLCertificateFile
        #   when the CA certificates are directly appended to the server
        #   certificate for convinience.
        #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

#   Certificate Authority (CA):
        #   Set the CA certificate verification path where to find CA
        #   certificates for client authentication or alternatively one
        #   huge file containing all of them (file must be PEM encoded)
        #   Note: Inside SSLCACertificatePath you need hash symlinks
        #         to point to the certificate files. Use the provided
        #         Makefile to update the hash symlinks after changes.
        #SSLCACertificatePath /etc/ssl/certs/
        #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

#   Certificate Revocation Lists (CRL):
        #   Set the CA revocation path where to find CA CRLs for client
        #   authentication or alternatively one huge file containing all
        #   of them (file must be PEM encoded)
        #   Note: Inside SSLCARevocationPath you need hash symlinks
        #         to point to the certificate files. Use the provided
        #         Makefile to update the hash symlinks after changes.
        #SSLCARevocationPath /etc/apache2/ssl.crl/
        #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

#   Client Authentication (Type):
        #   Client certificate verification type and depth.  Types are
        #   none, optional, require and optional_no_ca.  Depth is a
        #   number which specifies how deeply to verify the certificate
        #   issuer chain before deciding the certificate is not valid.
        #SSLVerifyClient require
        #SSLVerifyDepth  10

#   Access Control:
        #   With SSLRequire you can do per-directory access control based
        #   on arbitrary complex boolean expressions containing server
        #   variable checks and other lookup directives.  The syntax is a
        #   mixture between C and Perl.  See the mod_ssl documentation
        #   for more details.
        #&lt;Location /&gt;
        #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
        #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
        #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
        #            and %{TIME_WDAY} &gt;= 1 and %{TIME_WDAY} &lt;= 5 \
        #            and %{TIME_HOUR} &gt;= 8 and %{TIME_HOUR} &lt;= 20       ) \
        #           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
        #&lt;/Location&gt;

#   SSL Engine Options:
        #   Set various options for the SSL engine.
        #   o FakeBasicAuth:
        #     Translate the client X.509 into a Basic Authorisation.  This means that
        #     the standard Auth/DBMAuth methods can be used for access control.  The
        #     user name is the `one line' version of the client's X.509 certificate.
        #     Note that no password is obtained from the user. Every entry in the user
        #     file needs this password: `xxj31ZMTZzkVA'.
        #   o ExportCertData:
        #     This exports two additional environment variables: SSL_CLIENT_CERT and
        #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
        #     server (always existing) and the client (only existing when client
        #     authentication is used). This can be used to import the certificates
        #     into CGI scripts.
        #   o StdEnvVars:
        #     This exports the standard SSL/TLS related `SSL_*' environment variables.
        #     Per default this exportation is switched off for performance reasons,
        #     because the extraction step is an expensive operation and is usually
        #     useless for serving static content. So one usually enables the
        #     exportation for CGI and SSI requests only.
        #   o StrictRequire:
        #     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
        #     under a "Satisfy any" situation, i.e. when it applies access is denied
        #     and no other module can change it.
        #   o OptRenegotiate:
        #     This enables optimized SSL connection renegotiation handling when SSL
        #     directives are used in per-directory context.
        #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
        &lt;FilesMatch "\.(cgi|shtml|phtml|php)$"&gt;
                SSLOptions +StdEnvVars
        &lt;/FilesMatch&gt;
        &lt;Directory /usr/lib/cgi-bin&gt;
                SSLOptions +StdEnvVars
        &lt;/Directory&gt;

#   SSL Protocol Adjustments:
        #   The safe and default but still SSL/TLS standard compliant shutdown
        #   approach is that mod_ssl sends the close notify alert but doesn't wait for
        #   the close notify alert from client. When you need a different shutdown
        #   approach you can use one of the following variables:
        #   o ssl-unclean-shutdown:
        #     This forces an unclean shutdown when the connection is closed, i.e. no
        #     SSL close notify alert is send or allowed to received.  This violates
        #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
        #     this when you receive I/O errors because of the standard approach where
        #     mod_ssl sends the close notify alert.
        #   o ssl-accurate-shutdown:
        #     This forces an accurate shutdown when the connection is closed, i.e. a
        #     SSL close notify alert is send and mod_ssl waits for the close notify
        #     alert of the client. This is 100% SSL/TLS standard compliant, but in
        #     practice often causes hanging connections with brain-dead browsers. Use
        #     this only for browsers where you know that their SSL implementation
        #     works correctly.
        #   Notice: Most problems of broken clients are also related to the HTTP
        #   keep-alive facility, so you usually additionally want to disable
        #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
        #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
        #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
        #   "force-response-1.0" for this.
        BrowserMatch "MSIE [2-6]" \
                nokeepalive ssl-unclean-shutdown \
                downgrade-1.0 force-response-1.0
        # MSIE 7 and newer should be able to use keepalive
        BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

&lt;/VirtualHost&gt;
&lt;/IfModule&gt;
root@NAS:/etc/apache2/sites-available#
&nbsp;
root@NAS:/etc/apache2/sites-available# cat fv-http
&lt;VirtualHost *:80&gt;
        Include "/etc/frontview/apache/defaults.conf"
        Include "/etc/frontview/apache/http-share-redirect.conf"
        Include "/etc/frontview/apache/http-redirect.conf"
        Include "/etc/frontview/apache/Shares.conf"
        Include "/etc/frontview/apache/apps-https.conf"
        Include "/etc/frontview/apache/READYDROP.conf"
        Include "/etc/frontview/apache/lan-try.conf"
&lt;/VirtualHost&gt;
root@NAS:/etc/apache2/sites-available#
root@NAS:/etc/apache2/sites-available# cat fv-http-admin
&lt;VirtualHost *:80&gt;
        Include "/etc/frontview/apache/defaults.conf"
        Include "/etc/frontview/apache/http-share-redirect.conf"
        Include "/etc/frontview/apache/fv-admin.conf"
        Include "/etc/frontview/apache/Shares.conf"
        Include "/etc/frontview/apache/apps-https.conf"
        Include "/etc/frontview/apache/READYDROP.conf"
        Include "/etc/frontview/apache/lan-try.conf"
&lt;/VirtualHost&gt;
root@NAS:/etc/apache2/sites-available#
root@NAS:/etc/apache2/sites-available# cat fv-https
&lt;IfModule mod_ssl.c&gt;
&lt;VirtualHost _default_:443&gt;
        Include "/etc/frontview/apache/ssl.conf"
        Include "/etc/frontview/apache/defaults.conf"
        Include "/etc/frontview/apache/http-share-redirect.conf"
        Include "/etc/frontview/apache/fv-admin.conf"
        Include "/etc/frontview/apache/Shares.conf"
        Include "/etc/frontview/apache/apps-https.conf"
        Include "/etc/frontview/apache/READYDROP.conf"
&lt;/VirtualHost&gt;
&lt;/IfModule&gt;
root@NAS:/etc/apache2/sites-available#

Sandshark · Answer

On OS Re-install does not harm your data.&nbsp; See this thread:&nbsp;OS-Re-install-via-SSH.

StephenB · Answer

Sandshark&nbsp;wrote:
An OS Re-install does not harm your data.&nbsp; See this thread:&nbsp;OS-Re-install-via-SSH.

It is worth a try, but it doesn't reinstall everything.&nbsp; You still might end up with no web ui, and/or a damaged configuration.
&nbsp;
FWIW, I think there's more stuff missing than /var/www.&nbsp; All I see in there is one file (index.html) that you could easily recreate.&nbsp; Note it is owned by guest (which is a bit odd).
root@NAS:/var/www# ls -alstotal 40 drwxr-xr-x 1 root root 20 Jan 27 06:16 .0 drwxr-xr-x 1 root root 146 Jan 27 06:17 ..4 -rw-r--r-- 1 115 guest 53 Oct 9 15:53 index.html
root@NAS:/var/www# cat index.html
&lt;meta http-equiv="refresh" content="0; url=/admin/"&gt;

greasyrainbow · Answer

You're right, with Apache2 installed again I only see /var/www/index.html with guest permissions too. Can you look in your /etc/apache2/sites-available/ and sites-enabled/ for me? I have a feeling the ReadyCloud UI is somewhere in there.

greasyrainbow · Answer

The sites-enabled was it. Luckily, I just ran the "touch /.os_update" command and rebooted. It restored the apache2 conf and I can access my admin page again.

Forum Discussion

I accidentally removed Apache from my ReadyNAS and no longer have an admin page.

5 Replies

Related Content

ReadyNas 104 remove bonded network

How to recreate X-RAID volume after accidental removal of two drives

Remove Readynas from AD

ReadyNAS 214 "Remove inactive volumes to use the disk. Disk #1,2,3,4."

Readynas 104 - Cannot access data - remove inactive volumes to use the disk

NETGEAR Academy

ProSupport for Business