Posts by BerndBonker

You have to update to a newer i-MSCP version, at least 1.4.x, then you can also update the let's encrypt plugin.
But the current plugin will be updated soon anyway, there are major problems with renewing certificates right now.

Quote from Nuxwin

@TheCry

I'm on the point to release i-MSCP 1.5.3 (maintenance release). I'll also provide a maintenance release for the LetsEncrypt plugin which will include fixes for:

• Bug regarding cron job for SSL certificate renewal
• Removal of check at GUI side to covers case where domains are not reacheable locally
• Make customers able to trigger a renewal or new attempt from their interface without having to deal with debugger interface (admin side) or like here, with mysql command line tool.

Does I forgot anything?

Note that for wildcard SSL feature, there will be another MAJOR version as this require big review.

Display More

@Nuxwin

So if we update to 1.5.3 now the issue should be fixed?
Sorry, didn't read correctly, if we update to 1.5.3 and then also update the plugin, right?
When will the plugin update be released?

Hello,

we have a problem with the Let's Encrypt Plugin, for one of our domains it says:Incomplete authorizations

Other domains are running fine at this point, what is the reason and how can we fix it?

Ich habe auch nochmal eine Frage.

Es gibt ja die Möglichkeit im Plugin "Themen und Alternativnamen" einzufügen.

Was genau bietet und bewirkt diese Funktion?

Wir haben das Problem, dass wir unsere E-Mails über ein ERP nicht verschlüsselt verschicken können und vermuten, dass dies an Let's Encrypt liegt.
Oder könnte es auch an einem DNS Eintrag liegen? In Thunderbird hat er nach der Umstellung auf Let's Encrypt eine Ausnahmegenehmigung angefordert und danach ging es dann.
Im ERP kommt so eine Meldung nicht.

Jemand eine Idee?

Nachtrag:

Das Problem ist wohl, dass bei uns im Zertifikat immer die URL des Cloudservers steht und nicht die jeweilige URL der Webseite, wie kann man das ändern?

It was the email address in the config file, there was just a placeholder, we changed it and now it works fine.

Thank you!

Do we have to change something in our email accounts if we also activate SSL for the services?

Quote from Nuxwin

@BerndBonker

We cannot say anything without having access to letsencrypt.log file. But, generally speaking, if the email you have used while installing i-MSCP is not a valid recipient, you can end with such a problem. That email is saved in the /etc/imscp/imscp.conf file.

Once again, without the logs from letsencrypt.log, we cannot help much.

You should ask us for online support when you'll have access to your server, not before.

Thank you for your understanding.

Display More

Okay, that could be possible, since I didn't install i-MSCP it was installed by the company we rent the server.
I will get back to you tomorrow then, merci!

Right now I don't, no, tomorrow morning I will be able to access root.
Any other idea what the problem could be?

How do I get there?
I mean can I access it through the backend?
I don't have SSH at the moment.

Hello,

installing the plugin worked fine, when trying to create/erstellen it is giving me the message:

"Unable to register an account with ACME server"

Both on panel and on any of the domains.

What could be the reasons for this and how can I fix it?

Thank you for your help!

EDIT:

• Your Distribution and its codename (Debian Jessie)
• The i-MSCP version in use (1.5.1)
• The i-MSCP server implementation in use for the concerned service (for instance: ITK, Fcgid, PHP-FPM, Proftpd, Vsftpd ...) ?
• The plugin name and its version if your problem belongs to a plugin (Lets Encrypt Plugin, newest version)
• A understandable description of the problem (see above)
• The service logs (generally located under /var/log) if any
• The exact steps to reproduce the problem (see above)

Verstehe nicht was du meinst.
Habe an den DNS Einstellungen nichts geändert.
Gibt es da gewisse Voraussetzungen?