Posts by medienlampe

Quote from Nuxwin

Sure but if you have a static IP, you don't need such plugin... DynDNS is only need for home servers with a dynamic IP.

Mh, I think you might watch from a different angle.

As far as I remember, this plugin acts as de facto DynDNS-Service - not to use i-MSCP behind dynamic IPs but to assign dynamic hosts to clients via i-MSCP.
Your services with dynamic IPs connect via an API key to the i-MSCP-Plugin (which of course should have a static IP) which then updates its DNS entries for the clients with any new assigned IP.

TL;DR:
Afaik, OwnDDNS acts as privately hosted dynamic DNS service inside your i-MSCP instance for third party clients with dynamic IPs.

Hi Oliver,

Quote from fan-com

- ist der private key pro Domain,Reseller oder nur ein pro Server?

Das Zertifikat bzw. der Private Key ist pro (Sub-)Domain.

Quote from fan-com

- mit welchen Daten wird der private key erstellt?

Schau mal hier, dort wird beschrieben wie LE funktioniert: https://letsencrypt.org/how-it-works/

Quote from fan-com

- Ich habe bereits ein Zertifikat(nicht von Let's Encrypt) für mein Server ist das ein Problem?

Nope, LE lässt sich über das Plugin für jede Domain einzeln aktivieren.

Quote from fan-com

- Ich habe Kunden die mehrere Domains haben und nur für Ihre Hauptdomain ein Zertifikat haben, kann man für die restlichen Domain Let's Encrypt Zertfikate erstellen?

Ja.

Quote from fan-com

- ich habe gelesen das es nicht bei FTP und Mail der Domain funktionert, ist geplant die Zertfikate auch dafür einzubinden?

Mail-Zertfikate (S/MIME) werden von LE zur Zeit nicht unterstützt. Was die Integration von FTP/Mail-Daemons angeht, kann Dir @Nuxwin vielleicht mehr sagen.

Quote from fan-com

- Funktioniert das Plugin auch wenn ich ein reverse proxy benutze?

Wenn der Reverse Proxy bereits mit Deinen vorhandenen Zertifikaten zurechtkommt, sehe ich da kein Problem drin. Die entsprechenden Hosts auf Deinem Reverse Proxy sollten natürlich für sich gesichert bzw. evtl. LE auch hier extra eingerichtet sein.

Yes, it's compatible with >=1.3, see tab "Versions" here:

Quote from Ninos

Which error message is shown atm? Normally the complete relevant error message should be shown..

It's only showing:

The rest is stripped away.

Quote from Ninos

Problem here is that admin did not revoked old certificate. I cannot delete old directories because I don't know how the admin uses this certificates before.

Yeah, makes sense. An algorithm which is too smart might remove things not meant to be deleted.
But how about the status "error" and a button which shows the contents of the log file? That would be really nice as the error could be identified right out of i-MSCP thus enhancing the usability.

Quote from Ninos

BTW: You don't need to edit the db-entry. After solving problem just switch to /admin/imscp_debugger.php, where you can set status back

Awesome, thanks! Until now, this page has been totally out of focus for me.

I've got a suggestion for I found an annoyance.
If there is already some configuration inside

for a specific domain before using the plugin, the activation process inside i-MSCP will break up and display the status:

The reason behind is, that the client is asking for user action to renew the old file which is not handled by the plugin. This results in a deadlock inside the i-MSCP frontend. No user action is available to solve that issue.

The solution so far is to delete all directories in live and archive and the config inside renewal related to the domain. Finally, the corresponding entry in the database letsencrypt of i-MSCP has to be deleted to solve the deadlock.
After that, the Let's Encrypt Plugin in i-MSCP works like a charm.

A way to bypass that might be trying to delete any old directories/config in advance if there isn't any database entry for a domain yet.

Quote from Levitas

It would be very nice if someone could create screenshots how the process is now to require a new SSL Cert.

Like
1. Login as admin
2. Change to user
3. Go to Domains
4. click "generate Letsencrypt" cert.

I dont have the plugin yet (this will be change soon) but this would be a good "buy-decision-help"

Display More

It's indeed that simple, except:

4. Click "Let's Encrypt"
5. Click "Activate" for your desired (Sub-)Domain
6. Profit.

Kunde : Domains : Let's Encrypt 2016-06-27 16-30-03.png

Hi, there has been a discussion about that in this thread already.

Long story short:

• the development process was complex, therefore it's a bit more expensive (I made a rough calculation about that on the other thread)
• payed plugins are in general meant for commercial hosters

In my own opinion it's a very good price for something which is a one-time payment, especially if I think of the time it's saving.

Just now, I had a look in the source, also found out about the mistake and was on my way to write about the missing 'new'.

No problem mate, take a rest and have a chilled evening!
You are doing a great job!

It's already there...