ls -la /etc/ssl/certs ?
did you also run update-ca-certificates -f ?
ls -la /etc/ssl/certs ?
did you also run update-ca-certificates -f ?
Good morning
So many solutions here
The problem is not about certbot, nor about i-MSCP or its LetsEncrypt plugin but about openSSL v1.0.x which cannot validate the SSL certificates.
To solve the problem, you need in order:
kess Good job. I don't think that all steps are required. You don't need to import the full CA. Regarding certbot, I'll update it.
kivamp You're totally right. To solve the problem, install the ISRG root X1 and remove the expired one manually from /etc/ssl/certs
Good morning,
Any log ? Nothing, dada ?
It's not working ok... but ... any relevant data would be welcome.
Thank you...
The best way is the PhpSwitcher plugin.
The project is not dead. Rewrite time. I'll not spend much time to explain why it's so long.
Is there a timeline? How is the state of dev? 10,20,30 or 80%?
No state will be given. I don't like much the pressure you tend to make on our head.
People could fork, then make some pull requests but I've a new for you: Nobody help. They only talk about we should do that and this. That so easy to talk.. There is no really a community here. There is end users that don't really known what they're talking about. Not so grave for me but this is the reality. I'm open for any contribution. Just start with pull requests
Good morning,
I've been involved in that project since several years, starting with VHCS, then ispCP and now i-MSCP.
i-MSCP provides several layers which were not part from ispCP. This has been a hard work to add these layers such as the plugin management layer, the event system and so on...
However, this is not really a one man show. joximu is right when he say that working with me is not easy. This is because I'm a bit rigid and also because i-MSCP involves several programming languages such as Perl, PHP, C, Bash but not that all. i-MSCP also requires Debian expertise and more generally, GNU linux expertise, including knowledge of all software involved in hosting (http server, smtp, imap, pop, ftp servers and so on ...). This is not so easy to known all about these "technologies". It is really easy to say: I'll do a fork... Ok, I'm fine with this but one thing remain each time someone tried to make a fork of the project: The lack of knowledge...
On the current situation: The project is not dead. This is not because you don't see anything on the forum that we are not working behing the scene. i-MSCP is in a rewriting period. A full rewrite is not something that can be done in few months.
I'm working hand in hand with some of my colleagues on the full rewrite:
For those people which are really developers, they can think a bit about the work needed to deliver a new version. We cannot only type on a keyboard without any thinking. First there is the specification to write (what we want, what the clients need, what we need to make it, how we can do and so on...). Then, there is a reflexion period on which technologies we need to use (PHP, Perl, framework, libraries...).
Also the next version need to provide docker support and be cloud ready, so this is something totally new that need to be integrated from the begin.
About me
These last two years, my personal life changed:
---> A full time job (I'll talk more about that below)
---> A new girl friend
---> A move to a new city
---> A baby project
...
About my full time job
I'm working for a firm that provide accounting software for oil tankers (TOTAL, ENI, AVIA, BP...). This is not an easy work. That why I've been a bit away from here. However, I'm now in a new life step. I'll surely leave that job really soon to concentrate my effort on i-MSCP, working for an d IT compagny which rely on i-MSCP.
I cannot say anything more here. I'm still there. i-MSCP is not dead.
BTW: For those people which want fork, just do it but please, don't use our forums to talk about this.