Posts by seinarsson

Yes yes I am.

Hi,

I was wrong. I tried it again with a certificate that was generated yesterday, and it worked like a charm. What a wonderful feature to have. I am in the process of upgrading multiple servers from Debian Wheezy to Jessie, and at the same time migrating from ispcp to imscp. Yesterday a valid certificate generated on Wheezy last year stopped working with the updated openssl package with the following error "Bad file contents or format - or even just a forgotten SSLCertificateKeyFile?" The issue was not solved until after we reissued the certificate. I guess it is related.

Best

Siggi

Hi,

My first assumption is always that I am doing something wrong. But I have tried this with a few valid certificate combos that are being used in a manual setup, with the error mentioned.

I have also tried a key, cert and an intermediate which work fine in the imscp setup, and it fails with this error.

But I will figure it out and then report back to the forum.

Best

Siggi

Hi,

The bug is still there in 1.2.2, "A certificate in your CA bundle is missing or invalid" for valid certificates.

Best

Siggi

I want to confirm that this works great. All you need to do is add to the pool template /etc/imscp/php-fpm/parts/pool.conf something like

The file does need to exist, but say you want to add custom php_value you can create it and add to it whatever is needed.

Best

Siggi

Hi,

Yes that is the solution. Include per pool is possible in php-fpm, so I will just put it in the pool template. The include file does not even have to exists. So when needed I will created and the settings will be used. Excellent. Thank you @bytesplit

Best

Siggi

Hi,

Can you recommend how to set custom php settings for a site in the php-fpm pool without them being overwritten when the user for example enables error logging or changes any of the other settings available. In this environment these values can't be set using the .htaccess file or on the apache level. Well at least I can't see how it is done.

Best

Siggi

I didn't even know you could create hooks. You have opened up a new world for me. Thank you.

Still it would be nice if the installer/updater would check the themes directory or the /etc/imscp/imscp.conf to see if a custom theme has been defined and treat it the way it treats the gui/plugins directory, which is left intact. You never expect an update procedure to wipe out something that is open for customization.

Running perl imscp-autoinstall -d wipes out any custom themes you may have under /var/www/imscp/gui/themes/

Best

Siggi