[RESOLU] probleme ssl et https://

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 11 août 2014, 22:45

oui j'ai mis la directive dans le fichier ssl.conf

voici les fichier merci a toi

httpd.conf

Code : Tout sélectionner

# ZPanel Apache Include file for CentOS Linux
# Written by Bobby Allen, 15/05/2011

# Set the Zpanel Alias (used for development, sable will eventually use a VHOST)
Alias /zpanel /etc/zpanel/panel

# Setup the directory settings and PHP security flags for the Zpanel application directory.
<Directory /etc/zpanel/panel>
	Options FollowSymLinks
	AllowOverride All
	DirectoryIndex index.php
	<IfModule mod_php5.c>
		AddType application/x-httpd-php .php
		php_flag magic_quotes_gpc Off
		php_flag track_vars On
		php_flag register_globals Off
		php_admin_value upload_tmp_dir /etc/zpanel/temp
	</IfModule>

</Directory>

# Disallow web access to directories that don't need it/that we don't want people looking in!
<Directory /etc/zpanel/panel/cnf>
    Order Deny,Allow
    Deny from All
</Directory>

# Set server tokens (security??)
ServerTokens Maj

# Now we include the generic VHOST configuration file that holds all the ZPanel user hosted vhost data
Include /etc/zpanel/configs/apache/httpd-vhosts.conf
ssl.conf

Code : Tout sélectionner

#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these 
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
# 
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the 
# the HTTPS port in addition.
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism 
#   to use and second the expiring timeout (in seconds).
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization. 
SSLMutex default

#   Pseudo Random Number Generator (PRNG):
#   Configure one or more sources to seed the PRNG of the 
#   SSL library. The seed data should be of good random quality.
#   WARNING! On some platforms /dev/random blocks if not enough entropy
#   is available. This means you then cannot use the /dev/random device
#   because it would lead to very long connection times (as long as
#   it requires to make more entropy available). But usually those
#   platforms additionally provide a /dev/urandom device which doesn't
#   block. So, if available, use this one instead. Read the mod_ssl User
#   Manual for more details.

SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
SSLCryptoDevice builtin
SSLStrictSNIVHostCheck On

NameVirtualHost *:443

<VirtualHost *:443>

# General setup for the virtual host, inherited from global configuration
DocumentRoot "/var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr"
#ServerName www.hightech-shop.fr:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

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

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/hightechshop/hightech-shop_fr.crt

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/a1/hightech-shop.fr.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/pki/tls/certs/hightechshop/hightech-shop_fr.ca-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)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   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
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/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.
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>  
<VirtualHost *:443>  

# General setup for the virtual host, inherited from global configuration
DocumentRoot "/var/zpanel/hostdata/zadmin/public_html/defense-arms_fr"
#ServerName www.defense-arms.fr:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

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

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/defense-arms/defense-arms_fr.crt

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/a2/defense-arms.fr.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/pki/tls/certs/defense-arms/defense-arms_fr.ca-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)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   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
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/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.
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>  

Beta-Pictoris
Messages : 1017
Inscription : 07 janvier 2014, 21:48
Localisation : Angers, France

Re: probleme ssl et https://

Message par Beta-Pictoris » 12 août 2014, 01:21

Les directives 'ServerName' du fichier ssl.conf sont commentées. Je suppose qu'il y a une raison ?

Si ce sont bien les adresses des sites web, le serveur fonctionne en https puisqu'on a une page de maintenance https quand essaye d'ouvrir les pages en question.

Le navigateur renvoie juste un message stipulant que le site web n'est pas certifié. Il faut donc faire accepter le site par le navigateur.

Quand tu dis "qu'il fonctionne a 100% dans l'administration" , tu veux dire que tu testes le site à partir du serveur ?

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 12 août 2014, 08:39

Dans l'administration de la boutique

Si je comprend bien tout est correctement configuré?

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 12 août 2014, 08:51

j'ai effectuer une modif donc j'ai mis ServerName sans # et l'adresse du site sans les WWW dans le ssl.conf et maintenant les deux fonctionne en https coter administration de la boutique
mais le 404 not found ne disparait pas seul l'accueil de la boutique fonctionne coté client tout le reste se retrouve en erreur 404 (pareil pour les deux)

Beta-Pictoris
Messages : 1017
Inscription : 07 janvier 2014, 21:48
Localisation : Angers, France

Re: probleme ssl et https://

Message par Beta-Pictoris » 12 août 2014, 13:14

Il y a certainement quelque chose de mal configuré dans la configuration d'Apache. Apparemment, on a un problème de chemin incorrect.
Tu dois rechercher dans tous les logs d'Apache les messages d'erreurs significatifs.

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 12 août 2014, 13:57

le chemin d’accès dans le logs est bon mais affiche quand meme un 404 en https (en http cela fonctionne correctement)

Code : Tout sélectionner

[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/24-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/25-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/26-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/28-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/27-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:36:27 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/defense-arms_fr/29-home_default, referer: https://defense-arms.fr/
[Tue Aug 12 07:37:06 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/4-pieces, referer: https://hightech-shop.fr/
[Tue Aug 12 07:37:06 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/favicon.ico
[Tue Aug 12 07:37:20 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/c, referer: http://hightech-shop.fr/4-pieces
[Tue Aug 12 07:37:20 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/c, referer: http://hightech-shop.fr/4-pieces
[Tue Aug 12 07:37:31 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/mon-compte, referer: http://hightech-shop.fr/13-ordinateurs-de-bureau
[Tue Aug 12 07:37:38 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/c, referer: http://hightech-shop.fr/4-pieces
[Tue Aug 12 07:37:38 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/c, referer: http://hightech-shop.fr/4-pieces
[Tue Aug 12 07:40:09 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/4-pieces, referer: http://hightech-shop.fr/4-pieces
[Tue Aug 12 07:40:23 2014] [error] [client 78.219.138.180] File does not exist: /var/zpanel/hostdata/zadmin/public_html/hightech-shop_fr/4-pieces, referer: https://hightech-shop.fr/

Beta-Pictoris
Messages : 1017
Inscription : 07 janvier 2014, 21:48
Localisation : Angers, France

Re: probleme ssl et https://

Message par Beta-Pictoris » 12 août 2014, 15:06

Ton certificat doit être créé avec le nom exact du site virtuel. Est ce bien le cas ?

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 12 août 2014, 19:35

Oui car sinon je n'aurais eu aucun accès au site et le certificat aurai été invalide

corsinu
Messages : 11
Inscription : 10 août 2014, 22:59

Re: probleme ssl et https://

Message par corsinu » 13 août 2014, 11:13

salut beta-pictoris

j'ai trouver le problème de 404

enfaîte ça venait pas de la config

sur les boutique il y a une config URL simplifier il fallait la désactiver ^^

donc problème résolu

je te remercie énormément du temps que a pris pour essayer de régler mon souci

Répondre