Posts by Athar

Well, for sure, i-MSCP was a good solution, and finding something similar is hard 😁

KeyHelp could have been a way to go (where an old user of this panel made a migration script to move on it), but the code is obfuscated/crypted ==> It's a "No Go" (if one day, they make it as a "pay solution", you'll be stuck with it and will suffer a lot).

In the end, I chose to go with ISPConfig (which have Let's Encrypt, and also DNSSEC support).

The "bad counterpart" with it is that all the stuff is mostly manual (you can define a template for the DNS, but that's all).

Creating a web site, where i-MSCP create the DNS, default mail accounts, etc... aren't made with ISPConfig, every section need to be done manually.

Some good points though : Emails account are easily "migrable" as you can keep the salted password from i-MSCP to this new system (moving over 125 mails accounts (+ approx. 200 forward accounts), with the data migration, had been made in 2-3 hours).

There might be other solutions available, but it was a long old time plan to move to ISPConfig (2012 😂 but then, i-MSCP did rise, and this initial plan was gone).

Good luck in finding the one that fit your need 😉

Hi there, for those of you still around the corner

It's time, time to change, I waited as much as I could, but I can't remain on an OS which isn't maintained anymore, where Surry also drop the support for it.

Trying to pass on Debian 11 this release would have been a pain (mostly with Let's Encrypt), so as far as the security is a main concern for me, I had to drop it.

Also, we were a few waiting on a newer version, which may arrive one day or another, but too late for me (Debian 10 + i-MSCP 1.5.3 which is 5 years old too (PHP7... EoL in Jan 2019 (and Dec 2019 for 7.1)).

The only reason I sticked on it was the fact that this system isn't overused and so, not a big security threat.

Anyways, 48 Hours to migrate to another system, but here I'm, I can now breathe a little knowing Debian 12 is under support until mid-2028 (even though I have some configs to correct).

Thanks Nuxwin for this panel which helped me a lot in managing my server effortless, wish you the best for the future to you and everyone that was involved in this journey !

Was some nice 15 years or so (iSPCP then here 😋)

Cya 🫡

This doc is still available and working, to add new PHP Versions : https://wiki.i-mscp.net/doku.php?id=plugins:phpswitcher

Well, from what I could find :

Quote

Process Control support in PHP is not enabled by default. You have to compile the CGI or CLI version of PHP with --enable-pcntl configuration option when compiling PHP to enable Process Control support.

So, your only option would be to compile your own version of PHP8.1 with this option enabled.

==> https://www.php.net/manual/en/book.pcntl.php

If you see it enabled, it should work, as no settings are available in the php.ini (from those pages), but I don't know this extension so...

Yeah, R3 should be the default, but might be replaced in the future by E5/E6 (RSA to ECDSA).

And checking some info, I can confirm this : https://community.letsencrypt.…uction-environment/150679 , I quote from the last answer 11 days ago:

Quote

In one week, on June 6th, we will be switching to new issuance chains 38, which will include issuing ECDSA by default.

As a result, the ECDSA opt-in form is no longer needed and has been closed.

Just did a check on my system and yeah, I confirm this is still working for newly added domain on my end.

On an "old" one, I got one cert from R3+Root X1.

On the new test domain created yesterday night (and certificate just a few minutes ago), got it from E6+Root X1.

But you seems to have fixed it, it's fine for now 😁

2 years but still there... ok why not 😄

I guess you have some time to waste.

Yeah, no issues on my end too, still renewing fine so far.

I know that on recent Ubuntu releases (20+ at least), there is this package installed : unattended-upgrades

This install "harmless" update without letting you know by default.

Well, harmless, it depend, as this update Docker even with containers running (so they crash and reboot once updated )

I had to remove this package to ensure I didn't run into that anymore, maybe something to look on your side ?

Yeah, didn't find a lot of informations so far.

Only thing I saw, someone who tried to update from 18.04 to 18.10 and break everything (no real solution) and some other who might have got failed normal updates (but this was, mostly, on RedHat/CentOS ).

All in all, the only advise I could read there was to check no updates were pending or in a fail state.