openmediavault-letsencrypt

omv-engined -df shows:

And posting in the Forum shows me

Fatal error: An error occured. Sorry.
Information:
ID: 6e29caadbfdeb6b27683554b5473f8f088ba9afc
Bitte teilen Sie dem Betreiber die oben stehende ID mit.
Die Fehlermeldung kann mit dieser ID über „ACP » Protokoll » Fehler“ eingesehen werden.

Zitat von ryecoaaron

That is the spam filter. Nothing I can do to fix that.

Ah ok. Thank you.

Zitat von ryecoaaron

I changed the line 177 (missing one parentheses) on my running system but forgot to change it in the code which causes engined to not run. Fixed in 3.4.3. The following should get your systems fixed

apt-get update
apt-get install openmediavault-letsencrypt

Oh. Sorry. I do not have seen your post.
There was a missing ) on line 177?

Now it works fine. Thank you.

Zitat von ryecoaaron

Sure. Give me a bit to add that.

Thank you very much for your help.
Just tried out this "--http-01-port 443"
But it gives me this fault:
certbot: error: unrecognized arguments: --http-01-port 443

But I have checked, and it is the correct argument. So I am out of ideas again.

what is the default webroot for https acces to OMV WebGUI?:

Zitat von raulfg3

what is the default webroot for https acces to OMV WebGUI?:

/var/www/openmediavault/

Hello! I updated the plugin LetsEncrypt. After that, new cert3.pem, chain3.pem, etc. appeared in the /etc/letsencrypt/archive/my_domain/ directory.
But in WebGUI Sytem->Certificates->SSL and in System->General Settings->Secure connection->Sertificate there was an old, but still valid certificate for my_domen.
I need to do something to make WebGUI a new certificate from /etc/letsencrypt/archive/my_domain/ or wait until my current certificate expires and it automatically changes to a certificate from /etc/letsencrypt/archive/my_domain/ ? Thank you.

Hi,
I've uninstalled the plugin and with new version with more options (from last night apparently) it seems it works. Is 3.4.3...but looks different.

Regarding domain verification, I had same issue and found an old discussion community.letsencrypt.org as issue is caused by changing http port from default one (80).
In my case after I've set back to default one, domains verification was fine and certificate was generated.

I hope would help.

Zitat von ryecoaaron

Just explaining why the plugin caused problems.

I finally managed to generate the certificates, not sure what caused the problem, but I think my NGinx Reverse proxy had something to do with it, I tried and tried until I fixed it.
But now I cleared out the old certificates from OMV WebUI, I deleted all the old ones and only kept the new one.
And tried using the new certificate with FTP, which failed: Handshake failed, TLS FTP?
But now to the new problem. I did a "/etc/init.d/nginx restart" and Nginx wont start at all now.
When doing a journalctl -xn this is the result:

journalctl -xn
-- Logs begin at Sun 2017-10-29 19:35:05 CET, end at Tue 2017-10-31 10:55:56 CET. --
Oct 31 10:55:26 nas monit[1111]: 'nginx' failed to start (exit status 1) -- /bin/systemctl: Job for nginx.service failed. See 'systemctl status nginx.service' and 'jo
Oct 31 10:55:56 nas monit[1111]: 'nginx' process is not running
Oct 31 10:55:56 nas monit[1111]: 'nginx' trying to restart
Oct 31 10:55:56 nas monit[1111]: 'nginx' start: /bin/systemctl
Oct 31 10:55:56 nas systemd[1]: Starting A high performance web server and a reverse proxy server...
-- Subject: Unit nginx.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has begun starting up.
Oct 31 10:55:56 nas nginx[24935]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/private/openmediavault-46857801-8281-48a9-8ed7-eb38dc08a284.key") failed (SSL:
Oct 31 10:55:56 nas nginx[24935]: nginx: configuration file /etc/nginx/nginx.conf test failed
Oct 31 10:55:56 nas systemd[1]: nginx.service: control process exited, code=exited status=1
Oct 31 10:55:56 nas systemd[1]: Failed to start A high performance web server and a reverse proxy server.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has failed.
--
-- The result is failed.
Oct 31 10:55:56 nas systemd[1]: Unit nginx.service entered failed state.

and also systemctl status nginx.service:

-- Logs begin at Sun 2017-10-29 19:35:05 CET, end at Tue 2017-10-31 10:55:56 CET. --
Oct 31 10:55:26 nas monit[1111]: 'nginx' failed to start (exit status 1) -- /bin/systemctl: Job for nginx.service failed. See 'systemctl status nginx.service' and 'jo
Oct 31 10:55:56 nas monit[1111]: 'nginx' process is not running
Oct 31 10:55:56 nas monit[1111]: 'nginx' trying to restart
Oct 31 10:55:56 nas monit[1111]: 'nginx' start: /bin/systemctl
Oct 31 10:55:56 nas systemd[1]: Starting A high performance web server and a reverse proxy server...
-- Subject: Unit nginx.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has begun starting up.
Oct 31 10:55:56 nas nginx[24935]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/private/openmediavault-46857801-8281-48a9-8ed7-eb38dc08a284.key") failed (SSL:
Oct 31 10:55:56 nas nginx[24935]: nginx: configuration file /etc/nginx/nginx.conf test failed
Oct 31 10:55:56 nas systemd[1]: nginx.service: control process exited, code=exited status=1
Oct 31 10:55:56 nas systemd[1]: Failed to start A high performance web server and a reverse proxy server.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has failed.
--
-- The result is failed.
Oct 31 10:55:56 nas systemd[1]: Unit nginx.service entered failed state.

I am not sure what I did caused this, can you help me figure it out and fix it?

Thank you!

With the latest update of letsencrypt I somehow killed it. So I uninstalled the plugin, removed letsencrypt & job from /etc/openmediavault/config.xml and reinstalled letsencrypt. Creation of a cert worked well, but settings within "settings"-tab are ignored, cron job is not added to /etc/openmediavault/config.xml crontab-section and neither to scheduled tasks tab within OMV Web-GUI.

May someone post the lines for letsencrypt between <job> and </job> or give some other hint to get letsencrypt running properly again.

Thank you in avance.

Edit: Is it possible, that the monthly cron job to revalidate the cert does not show up in scheduled tasks any more? If so, my porblem is solved.

Zitat von ryecoaaron

Yes, the new plugin does not create a job in schedule jobs because there is really no reason for it to be there. It puts in directly in /etc/cron.d - link

I assume you thought they were being ignored because there was no job in the scheduled jobs?

It had to look different to support multiple web roots.

Did you remember to change the cert used by the nginx plugin's servers?

I think so, I only used it for FTP, and if I hadn't changed it, I would not be able to delete the certificate? Becuase that makes the button greyed out.
This happened right after I tried a few things with the FTP TLS/SSL, but it can also be that I removed the old certs, as I had not restarted the nginx server before then. Any idea on what to try? RIght now I can only access the server via Putty.

Zitat von ryecoaaron

What does nginx -t tell you?

root@nas:~# nginx -t
nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/private/openmediavault-46857801-8281-48a9-8ed7-eb38dc08a284.key") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
nginx: configuration file /etc/nginx/nginx.conf test failed

Zitat von ryecoaaron

It doesn't like the cert. Maybe leftover parts from previous generates?

I have many leftover files when I check the /etc/letsencrypt folders, but I am not sure what I should remove, to not destroy my new cert?

live folder has one old folder for the cert (even though I deleted all except the newest one in OMV).
keys folder has files that looks like this: 0000_key-certbot.pem only 4 of 10 files are from today.
Same with csr-folder.
And archive has a lot of files.

What do you suggest me trying?

EDIT: Removed the old folder in /etc/letsencrypt/live, so now I only have the newest one.

But this changed nothing.

This is all I can find about this problem, and I've read through anything without any solutions. @ryecoaaron I hope you have some ideas! I'm totally stuck, because I cannot access the webgui either.
https://www.google.se/search?q…IMygDMAA&biw=1745&bih=885