Ordinarily, that would work, but with the apache configuration on this ReadyNAS, I can’t even find out what the web directory is!
Start with these:
grep -Eri 'servername|serveralias' /etc/apache2
grep -Eri 'servername|serveralias' /etc/frontview/apache
1 Like
grep -Eri ‘servername|serveralias’ /etc/apache2 :-
/etc/apache2/sites-available/000-default-le-ssl.conf: ServerName nibbles0522.ddns.net
/etc/apache2/sites-available/000-default-le-ssl.conf:ServerAlias nibbles0522.ddns.net
/etc/apache2/sites-available/000-default-le-ssl.conf: ServerName nibbles0522.ddns.net
/etc/apache2/sites-available/000-default.conf: # The ServerName directive sets the request scheme, hostname and port that
/etc/apache2/sites-available/000-default.conf: # redirection URLs. In the context of virtual hosts, the ServerName
/etc/apache2/sites-available/000-default.conf: #ServerName www.example.com
/etc/apache2/mods-available/info.conf: # http://servername/server-info (requires that mod_info.c be loaded).
/etc/apache2/mods-available/status.conf: # with the URL of http://servername/server-status
grep -Eri ‘servername|serveralias’ /etc/frontview/apache :- nothing returned.
Nothing of much interest here I’m afraid. 
So there is no access to that system via:
You can wrap the text with a line before and after containing only three tilde(back tick) key:
```
your text - which can contain < and > and #s and just about anything else...
```
1 Like
yes, there is access to the system via: nibbles0522.ddns.net, but only to the Frontview admin logon. If you try it, you’’ see what I mean. nibbles0522.ddns.net/nextcloud gets you to the Nexctloud sign-in page.
I don’t know if this helps any, but the only place that servername appears to be used in anger is in these 3 lines taken from the results of: grep -Eri ‘servername|serveralias’ /etc/
/etc/default/config/etc/proftpd/proftpd.conf:ServerName “NETGEAR ReadyNAS”
/etc/ssl/openssl.cnf:#nsSslServerName
/etc/ssl/openssl.cnf:#nsSslServerName
/etc/proftpd/proftpd.conf:ServerName “NETGEAR ReadyNAS”
There were more lines but they were the same as the search of /etc/apache
We should probably have a look at these files:
I don’t know why I didn’t think of this before, but I used a USB stick to get ddump.conf from the ReadyNAS (doh!). ddump.conf is now available at: https://nibbles0522.ddns.net:40444/ddump.conf
proftpd.conf is available at https://nibbles0522.ddns.net/proftpd.conf
I wouldn’t bother with 000-default-le-ssl.conf as it was my attempt at creating a suitable .conf file for my certificate files, so it won’t be correct.
The dump file is very filtered down.
I do see only one SSLCertificateFile line.
<VirtualHost _default_:443>
# In file: /etc/frontview/apache/ssl.conf
# 1:
SSLEngine on
# 2:
SSLCertificateFile /etc/frontview/apache/apache2.pem
We should probably start by looking at that file:
/etc/frontview/apache/ssl.conf
If that is all of it…
[It doesn’t even have a ServerName directive nor a DocumentRoot.]
I don’t see how that can be useful.
Those are the files as copied from the device. If there are any more i can post…
I know how to do it now!! :o)
It has to be tied up with frontview somehow. That’s what the device seems to be all about.
It is a very “unique” configuration.
Perhaps there is something to be found looking online for “frontview configuration”.
[I don’t know, I’ve never used it.]
Ok. I’ll investigate. Thanks for your input.
1 Like
Well, I thought I had it cracked by modifying the instructions here but ignoring the certbot part and continuing from part 3. after “Read Terms of Service”, but using the files I obtained using acme.sh thus:
cat /etc/letsencrypt/live/nibbles0522.ddns.net/key.pem >> apache2.pem
cat /etc/letsencrypt/live/nibbles0522.ddns.net/cert.pem >> apache2.pem
cat /etc/letsencrypt/live/nibbles0522.ddns.net/fullchain.pem >> chain.pem
When it came to reloading apache2, it failed with the following lines in journalctl:
Dec 13 13:45:35 ReadyNAS01 apachectl[11024]: AH00526: Syntax error on line 2 of
/etc/frontview/apache/ssl.conf:
Dec 13 13:45:35 ReadyNAS01 apachectl[11024]: SSLCertificateFile: file ‘/etc/fron
tview/apache/apache2.pem’ does not exist or is empty
Dec 13 13:45:35 ReadyNAS01 systemd[1]: apache2.service: Control process
exited, code=exited status=1
Now, I don’t know enough about apache2, but I suspect the cat /etc/letsencrypt… lines are intended to use the files in the cat command as apache2.pem. So for whatever reason, that didn’t work.
Success!
I realised I hadn’t stopped apache before making the changes. So I made the changes having stopped the service and when I restarted, it worked!
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.