GoDaddy SSL installeren op YourHosting VPS

[Torrentus]

Ik heb bij GoDaddy een SSL-certificaat aangevraagd, omdat ik dat wil gebruiken om de communicatie tussen bezoeker en server te versleutelen. Het SSL-certificaat is succesvol aangevraagd, en ik heb inmiddels twee bestanden van GoDaddy ontvangen; een .crt bestand voor het domein en een bundle.crt bestand.

Nu moet ik deze dus installeren in Apache op de door YourHosting geleverde TurnkeyLinux LAMP omgeving. Ik heb de bestanden geupload naar de server, en het apacheconfiguratie bestand gevonden in /etc/apache2/sites-available/default-ssl

In dat bestand heb ik een aantal regels aangepast, zodat ze matchen met de locaties van mijn ssl-certificaat:

SSLCertificateFile /etc/ssl/certs/domein.nl.crt
SSLCertificateKeyFile /etc/ssl/private/rgp.key
SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt

Vervolgens heb ik met het commando /etc/init.d/apache2 reload via ShellinaBox de Apache server opnieuw opgestart. Er kwam een (in mijn ogen onbelangrijke?) melding bij het herstarten van de server;

* Reloading web server config apache2
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.
1.1 for ServerName

Helaas is er iets niet goed gegaan, want als ik naar mijn domein ga (https://109.235.76.84), wordt het standaard certificaat gebruikt, in plaats van mijn legitieme GoDaddy SSL certificaat.

Kan iemand me wijzen op een eventuele fout die ik gemaakt heb in het proces?

Voor zover nog niet duidelijk was; Dit is mijn eerste project met een VPS/SSL, en de eerste keer dat ik met Linux werk

Bedankt alvast

[AK47]

Weet je zeker dat die URL matched met je VirtualHost config?

Ik heb een vergelijkbare SSL VirtualHost config, ik heb even het e.e.a. gerenamed naar rgp.nl:

code:

<VirtualHost *:443>
        SSLEngine on
        SSLCertificateFile /etc/ssl/certs/rgp.nl.crt
        SSLCertificateKeyFile /etc/ssl/certs/rgp.key
        SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt

        ServerName rgp.nl
        DocumentRoot /var/www/rgp.nl

        ErrorLog /var/log/apache2/rgp_nl_ssl_error.log
        CustomLog /var/log/apache2/rgp_nl_ssl_access.log combined

        <Directory /var/www/rgp.nl/>
                Options -Indexes -MultiViews
                Allowoverride All
        </Directory>
</VirtualHost>

PS: als je op IP blijft verbinden blijf je altijd warnings houden aangezien je certificaat voor 1 of meerdere domains is uitgegeven. Maar ik zie inderdaad dat niet het GoDaddy certificaat gepresenteerd wordt.

[Torrentus]

Volgens mij wel ja, zie onderstaande kopie van mijn gehele default-ssl:

code:

<IfModule mod_ssl.c>
<VirtualHost _default_:443>
    ServerAdmin webmaster@localhost

    DocumentRoot /var/www
    <Directory />
        Options FollowSymLinks
        AllowOverride None
    </Directory>
    <Directory /var/www/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride None
        Order allow,deny
        allow from all
    </Directory>

    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
    <Directory "/usr/lib/cgi-bin">
        AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Order allow,deny
        Allow from all
    </Directory>

    ErrorLog /var/log/apache2/error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog /var/log/apache2/ssl_access.log combined

    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from 127.0.0.0/255.0.0.0 ::1/128
    </Directory>

    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on

    #   A self-signed (snakeoil) certificate can be created by installing
    #   the ssl-cert package. See
    #   /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
    #   If both key and certificate are stored in the same file, only the
    #   SSLCertificateFile directive is needed.
    SSLCertificateFile    /etc/ssl/certs/domein.nl.crt
    SSLCertificateKeyFile /etc/ssl/private/rgp.key

    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt

    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #   Note: Inside SSLCACertificatePath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath /etc/ssl/certs/
    #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

    #   Certificate Revocation Lists (CRL):
    #   Set the CA revocation path where to find CA CRLs for client
    #   authentication or alternatively one huge file containing all
    #   of them (file must be PEM encoded)
    #   Note: Inside SSLCARevocationPath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath /etc/apache2/ssl.crl/
    #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10

    #   Access Control:
    #   With SSLRequire you can do per-directory access control based
    #   on arbitrary complex boolean expressions containing server
    #   variable checks and other lookup directives.  The syntax is a
    #   mixture between C and Perl.  See the mod_ssl documentation
    #   for more details.
    #<Location />
    #SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    #            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    #            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    #            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    #            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
    #           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #</Location>

    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #     Translate the client X.509 into a Basic Authorisation.  This means that
    #     the standard Auth/DBMAuth methods can be used for access control.  The
    #     user name is the `one line' version of the client's X.509 certificate.
    #     Note that no password is obtained from the user. Every entry in the user
    #     file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #     This exports two additional environment variables: SSL_CLIENT_CERT and
    #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #     server (always existing) and the client (only existing when client
    #     authentication is used). This can be used to import the certificates
    #     into CGI scripts.
    #   o StdEnvVars:
    #     This exports the standard SSL/TLS related `SSL_*' environment variables.
    #     Per default this exportation is switched off for performance reasons,
    #     because the extraction step is an expensive operation and is usually
    #     useless for serving static content. So one usually enables the
    #     exportation for CGI and SSI requests only.
    #   o StrictRequire:
    #     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #     under a "Satisfy any" situation, i.e. when it applies access is denied
    #     and no other module can change it.
    #   o OptRenegotiate:
    #     This enables optimized SSL connection renegotiation handling when SSL
    #     directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
        SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory /usr/lib/cgi-bin>
        SSLOptions +StdEnvVars
    </Directory>

    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #     This forces an unclean shutdown when the connection is closed, i.e. no
    #     SSL close notify alert is send or allowed to received.  This violates
    #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #     this when you receive I/O errors because of the standard approach where
    #     mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #     This forces an accurate shutdown when the connection is closed, i.e. a
    #     SSL close notify alert is send and mod_ssl waits for the close notify
    #     alert of the client. This is 100% SSL/TLS standard compliant, but in
    #     practice often causes hanging connections with brain-dead browsers. Use
    #     this only for browsers where you know that their SSL implementation
    #     works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    BrowserMatch "MSIE [2-6]" \
        nokeepalive ssl-unclean-shutdown \
        downgrade-1.0 force-response-1.0
    # MSIE 7 and newer should be able to use keepalive
    BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

</VirtualHost>
</IfModule>

Edit:
Ik vond ook nog het bestand default (dus zonder ssl, zoals default-ssl in de map /etc/apache2), en vond daar (tegen verwachting in) ook een SSL-configuratie in aan. Die heb ik inmiddels ook gewijzigd, maar zonder resultaat.

Default:

code:

NameVirtualHost *:80
NameVirtualHost *:443

<VirtualHost *:80>
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/
</VirtualHost>

<VirtualHost *:443>
        SSLEngine on
        SSLCertificateFile /etc/ssl/certs/domein.nl.crt
        SSLCertificateKeyFile /etc/ssl/private/rgp.key
        SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/
</VirtualHost>

ScriptAlias /cgi-bin/ /var/www/cgi-bin/

<Directory /var/www/>
        Options Indexes FollowSymLinks MultiViews
        Order allow,deny
        allow from all
</Directory>

[ Voor 5% gewijzigd door Torrentus op 25-06-2012 13:16 ]

[AK47]

code:

#SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt

Staat gecomment....

[Torrentus]

AK47 schreef op maandag 25 juni 2012 @ 12:43:

code:

#SSLCertificateChainFile /etc/ssl/certs/gd_bundle.crt

Staat gecomment....

Was me ook opgevallen Had ik al aangepast en meteen na plaatsen uit post in dit topic ge-edit, maar het verandert niets aan de situatie

[e00y]

Apache herstart na de aanpassing ?

[Bastien]

En heb je de betreffende configuratie in sites-available ook wel enabled (a2ensite) zodat deze ook in sites-enabled staat? En daarna apache reloaden uiteraard.

[Torrentus]

Bastien schreef op maandag 25 juni 2012 @ 12:49:
En heb je de betreffende configuratie in sites-available ook wel enabled (a2ensite) zodat deze ook in sites-enabled staat? En daarna apache reloaden uiteraard.

Dat heb ik niet gedaan, kun je dat nog iets toelichten?
In sitesenabled staan twee snelkoppelingen;
000-default & phpmyadmin

Na elke wijziging wel Apache herstart natuurlijk

[lordgandalf]

in sites-enabled staan de configs die actief zijn dus even a2ensite <configfilenaam> doen dan apache een trap nageven en dan zou het moeten werken

[Torrentus]

Bingo, dat was het. Bedankt voor jullie hulp

[ Voor 72% gewijzigd door Torrentus op 25-06-2012 21:04 ]

[Koffie]

Move PNS > NOS