Posts by Nuxwin

    Hi,

    /var/www/imscp/gui/ path is served by Nginx, not Apache. Nginx' HTTP Auth is working a little different, there are no .htaccess/.htpasswd files


    But another question, why do do that? PhpMyAdmin is installed by i-MSCP and has Cookie Auth agains SQL Users in the DB

    You're right for the .htaccess files but wrong for the .htpasswd file (auth feature in fact) ;) He want double protect PMA access to prevent running PMA itself (PHP) in case there is security hole in PMA auth layer...

    Good evening,


    PhpMyAdmin is run through NGINX (as the control panel), not through Apache2... Before starting to play, I would recommend you to learn a bit ;)


    Regarding your question, Nginx suport .htpasswd fil, (basic authentication in fact...) but not the .htaccess files... Therefore, the procedure, should be as follows:

    1. Create the htpasswd file: htpasswd -c /var/www/imscp/gui/data/persistent/.htpasswd <user>
    2. Edit the /etc/nginx/imscp_pma.conf file and then replace the following configuration stanza:
    Code
    1. location ^~ /pma/ {
    2. root /var/www/imscp/gui/public/tools;
    3. location ~ \.php$ {
    4. include imscp_fastcgi.conf;
    5. }
    6. }

    by:

    Code
    1. location ^~ /pma/ {
    2. root /var/www/imscp/gui/public/tools;
    3. auth_basic "PMA Authentication";
    4. auth_basic_user_file /var/www/imscp/gui/data/persistent/.htpasswd;
    5. location ~ \.php$ {
    6. include imscp_fastcgi.conf;
    7. }
    8. }


    Once done, reload the Nginx instance (service nginx reload), and try to access your PMA instance. If all goes well, you should be asked for auth data.


    Note that changes made in the /etc/nginx/imscp_pma.conf will not be persistent, meaning that if you update i-MSCP or trigger a full reconfiguration, changes will be lost. Best would be to inject those changes using an i-MSCP listener file. Regarding the .htpasswd file, you can see that I store it under the /var/www/imscp/gui/data/persistent directory. This effectively make it persistent.

    So wie es aussieht, hattest Du aber mal PHP 7.0 kompiliert und aktiviert.


    Schau mal unter /opt/phpswitcher/, welche Versionen da kompiliert sind. Und vergleiche das im Panel als Admin unter Einstellungen->PHP Switcher.

    The problem is fixed. This was due to a task for the software installer that failed and which prevented psw* services to be started/restarted...


    Another problem is the user himself which is a beginner and which play too much with the server, installing everything and anything (he installed almost all available i-MSCP free plugins and I bet he don't even known why). He also set bad directory/file permissions.

    can i ad an other domain for mail? "Dienstleistungen" ? or change this?

    You can add up to 100 SANs. But, you need understand that postfix doesn't support SNI. That why you need use the server hostname in your mail client. We already answered and explained that many time on our forum. Please make a search for futher details.

    what is the best way to use ssl with i-mscp panel a paid wildcard ssl or 2 different certs issued by letsencrypt ?

    Why you would like to have two SSL certificates for the control panel exactly? Don't forget, you can add up to 100 SANs per letsencrypt SSL certificate. Please look better at the letsencrypt interface.

    So, it's already enabled. You need now setup your mail client correctly, that is, set the server hostname (service certificate name) for both, the IMAP/POP and SMTP server.

    As administrator, go to the letsencrypt UI and enable letsencrypt for the services. Then, in your mail client, make use of the server hostname for both IMAP (or POP) and SMTP servers.


    BTW: Multiple accounts are not allowed on our forums. I'll remove the Sould account.