Posts by itscz.org

    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
    1. Version: 1.5.1
    2. Build: 20170908
    3. Nachrichtenpriorität : Error
    4. ==========================================================================
    5. [79.227.204.40] Could not write in
    6. /var/www/imscp/gui/data/tmp/13-openssl.cnf0re5bK openssl temporary
    7. configuration file.
    8. ==========================================================================

    The mentioned folder has the same permission as on the old machine.


    Any advice to address this problem?

    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?

    Hi,


    this is not a bug but a question and hopefully anyone can help me.
    I developed a more user-friendly default page in php with some stat display and redirection (eg. for ssl-accessing non-ssl-enabled pages => plain http) and failed with enabling php for this page.


    If a add the following directives in the site config the page is loading endless:



    Code
    1. <Proxy "unix:/var/run/php5-fpm-www.sock|fcgi://127.0.0.1:9000/var/www/virtual/ServerDefaultPage/">
    2. ProxySet timeout=7200
    3. </Proxy>
    4. <FilesMatch ".+\.ph(p[3457]?|t|tml)$">
    5. SetHandler proxy:unix:/var/run/php5-fpm-www.sock|fcgi://127.0.0.1:9000/var/www/virtual/ServerDefaultPage/
    6. </FilesMatch>

    If i point to a real domain socket i receive "File not found" which seems legit to me due to filesystem permissions but i won't go ahead with misusing real domain user environments here.
    Anyone has an idea how to properly enable php for the default page?


    Thanks,
    Chris

    We will never enable PHP log by default. On production server where there is several hosted PHP applications, enabling PHP logs slow down the server.

    I didn't want it on as default too, but it would be nice to enable it per domain/site or whatever is my pool config. The little gain of speed will not help me in supporting customers to find bugs or misconfigurations :)


    The customer's home directory (what you calll root folder) is protected by default (using immutable bit) to prevent the customer to deleted default folders.

    Thank, i'll deal with it. Placing in htdocs is not a good idea, best would be "logs" as the name says but it's blocked, but i'll find a place...

    I also use a non-standard port, but it is below 1024 and other securities like fail2ban, keyonly, nonroot applied as well :)