• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    letsencrypt usage after installation

    Scheduled Pinned Locked Moved
    General Problems
    2
    4
    532
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      OlivierSchmitt
      last edited by

      Hello Dear All,

      Can someone explain how to install certificat with letsencrypt?

      I have use standard let’s encrypt installation for apache under ubuntu server.
      So, I have :

      ls -al /etc/letsencrypt/live/xxx.xxx.xxx.fr/

      lrwxrwxrwx 1 root root 45 janv. 16 17:17 cert.pem -> …/…/archive/xxx.xxx.xxx.fr/cert1.pem
      lrwxrwxrwx 1 root root 46 janv. 16 17:17 chain.pem -> …/…/archive/xxx.xxx.xxx.fr/chain1.pem
      lrwxrwxrwx 1 root root 50 janv. 16 17:17 fullchain.pem -> …/…/archive/xxx.xxx.xxx.fr/fullchain1.pem
      lrwxrwxrwx 1 root root 48 janv. 16 17:17 privkey.pem -> …/…/archive/xxx.xxx.xxx.fr/privkey1.pem

      On the fog side:
      /var/www/html/fog/management/other/ssl/srvpublic.crt
      /var/www/html/fog/management/other/ca.cert.pem

      /etc/apache2/sites-enabled/001-fog.conf:

      <VirtualHost :80>
      <FilesMatch “.php$”>
      SetHandler “proxy:fcgi://127.0.0.1:9000/”
      </FilesMatch>
      ServerName 130.79.125.236
      ServerAlias xxx.xxx.xxx.fr
      DocumentRoot /var/www/
      RewriteEngine On
      RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
      RewriteRule .
      - [F]
      RewriteRule /management/other/ca.cert.der$ - [L]
      RewriteCond %{HTTPS} off
      RewriteRule (.) https://%{HTTP_HOST}/$1 [R,L]
      </VirtualHost>
      <VirtualHost :443>
      KeepAlive Off
      <FilesMatch “.php$”>
      SetHandler “proxy:fcgi://127.0.0.1:9000/”
      </FilesMatch>
      ServerName yyy.yyy.yyy.yyy
      ServerAlias xxx.xxx.xxx.fr
      DocumentRoot /var/www/
      SSLEngine On
      SSLProtocol all -SSLv3 -SSLv2
      SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS>
      SSLHonorCipherOrder On
      SSLCACertificateFile /var/www/fog//management/other/ca.cert.pem
      <Directory /var/www/fog/>
      DirectoryIndex index.php index.html index.htm
      </Directory>
      RewriteEngine On
      RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
      RewriteRule .
      - [F]
      RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
      RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d
      RewriteRule ^/fog/(.
      )$ /fog/api/index.php [QSA,L]
      SSLCertificateFile /etc/letsencrypt/live/xxx.xxx.xxx.fr/fullchain.pem
      SSLCertificateKeyFile /etc/letsencrypt/live/xxx.xxx.xxx.fr/privkey.pem
      Include /etc/letsencrypt/options-ssl-apache.conf
      </VirtualHost>

      What must be copy/move/updated between they files?

      Many thanks in advance.

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @OlivierSchmitt The certificate is not only used by the web UI but also when PXE booting and by the fog-client. So copying/moving certificate and key files on the FOG server is not enough! You need to re-compile the iPXE binaries and eventually the fog-client as well or use letsencrypt and self-signed certs in parallel to not break the fog-client communication.

        Unfortunately there is no proper documentation we can point you to for this. I started a writeup in the wiki some time ago but never got to finish it. This is mainly due to the fact that few people use custom certs (be it letsencrypt or their own internal CA) und so this is very low on the priority list.

        As well I want to point out some security concerns. And I really need to stress this point: FOG was not build with the amount of security in mind that it would need to allow for an installation to be accessable from the internet. Sure you can technically do it but it’s all on your own risk.

        So I am wondering if you want to re-think hosting you FOG server to be accessable from the internet? Why don’t you setup VPN tunnels for people to access the FOG web UI from different locations?

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • O
          OlivierSchmitt
          last edited by

          @Sebastian-Roth Thanks for your reply.
          It was not for use on internet.
          I use let’s encrypt only for facility on a proof of concept.
          But if we decide to use FOG, we have to implement some ssl to in production with real certificate authority.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth

            @OlivierSchmitt said in letsencrypt usage after installation:

            It was not for use on internet.

            How do you get a letsencrypt certificate if the FOG server is not facing the internet? By copying the files from another system?

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            215

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project