@Nuxwin someone summoned the doctor?
Posts by theemstra
-
-
Privet,
The i-MSCP 1.1.14 release (which is inside the 1.x) series is no longer supported, because many bugs have been fixed in the following releases, possibly also this one.
Please upgrade your i-MSCP installation, make sure to read the appropriate ERRDATA files! -
Hi eelorriaga,
The vesion of i-MSCP you are using:
i-MSCP 1.1.20
is old and needs to be updated.
The 1.x branch is no longer supported, you should upgrade your installation.
Note that you should read the appropriate errdata documentation before doing an upgrade like this. Maybe @Nuxwin has some advice how to proceed.
-
Hello @eelorriaga,
I see this is your first post to our forum.
Welcome to the i-MSCP community!Please make sure to read the Reporting Rules for anything that might be a bug.
Please reply to this post with the required information, then we can look into your issue!
With regards,
Thom
-
@Nuxwin I think that would be more proportional, yes.
-
Hi @bytewerk.net,
I think you misunderstood.
The warning is a general one. Not one specific for your situation.
It will always be there to warn users about the situation at Let's Encrypt.You are right, this is the German Corner, but my German isn't that good, Mein Deutch is nicht so güt, aber mein Engels und Niederlandisch ist besser.
Ciao
-
Welcome to our community forum!
Please take note of our community reporting rules for any post that is specific to a bug.In this case, the message you note it not a warning specific to your situation.
The warning just lets you know that there is a limit per domain name, to prevent problems.So there should not be any problems regarding that, so go ahead and request your domain names.
With regards,
Thom
-
Hi @norcalhelpdesk, give @Nuxwin a chance to catch sleep. The guy works his ass off for the project.
You can see you are on his radar, because he responded for you, you are on his to do list and he'll get back to you when he has a chance!
-
Alright, sounds cool.
Should it be said in errdata that the specific listener then is no longer needed and should be removed to prevent trouble? -
Me too, but it should be configurable in the installer then
For me, the listener works fine as well.
So, what will you do, just ask during the installation how to configure DNS?
1. Use ns1.domain.tld only
2. Use ns1.domain.tld and ns2.domain.tld (future use, when multiple servers are used)
3. Use completely custom dns servers.Currently I'm also using https://github.com/i-MSCP/imsc…med_slave_provisioning.pl, but the hostnames are not related to the customer domains at all
