Ich warte seit 2 Monaten auf eine Plugin-Rechnung, also Geld scheint hier auch nicht wirklich im Vordergrund zu stehen...
Ich will gerade von 5.6 auf 7.0 updaten, aber via
lässt sich die Version nicht anpassen.
EDIT: So geht es:Quote
You need rerun the distribution installer with the --reconfigure option and php item:
I encountered an SQL error in mail.log (spamd: auto-whitelist: sql-based get_addr_entry nxxx: SQL error: Unknown column 'last_hit' in 'order clause') that has already been fixed in 2.1.0 plugin version (https://youtrack.i-mscp.net/issue/IP-1808) - but the most recent release is still 2.0.1
Do we get another update in the free branch before 3.0 is ready?
I am running plugin version 3.3.0
I figured out the reason for me was a failb2ban apache rule, it blocked my own public ip from using port 443 locally. I temporary disabled fail2ban and it worked immediately then. Did not take further investigations yet what exactly was that rule and why it has been triggered, but maybe you should check your iptables for any active https input filter on your own interfaces.
already have some domains with LE working flawlessly, now added an alias domain with same mount point as the primary domain, getting mentioned error.
I tried to remove all possible rewrites from that space as mentioned but no luck.
Ooops, ok, thx. Didn't expect it to be a bug but rather an issue on my installation. Will check the tracker next time before posting.
I migrated my installation from Jessie (8.1) to Stretch (9.4; another machine), and everything seems to work fine, except for one thing:
When i try to create a self-signed certificate for a subdomain, it is rejected with an error and i receive an error mail:Code
- Version: 1.5.1
- Build: 20170908
- Nachrichtenpriorität : Error
- [184.108.40.206] Could not write in
- /var/www/imscp/gui/data/tmp/13-openssl.cnf0re5bK openssl temporary
- configuration file.
The mentioned folder has the same permission as on the old machine.
Any advice to address this problem?
Just updated to the latest i-MSCP and the pool file vanished. So that is not yet the best solution
Wow thank you very much, it works this way.
However i modified it a bit because "phptmp" does not exist there per default, so i created a "htdocs, phptmp" subdirectory structure there and i also edited the 00_ServerDefaultPage_ssl.conf
Here is my result: https://itscz.org/ (accept the self-signed here)
But i am wondering if this is update safe?