Vous n'êtes pas identifié(e).
Pages : 1
mon port.conf
mon /etc/hosts
un netstat -tap
il ressort que mon port 443 n'est pas en écoute:(, confirmé par un zenmap
j'ai bien sur essayé en désactivant le parefeu
la configuration est similaire avec mon serveur et les connexions ssl sont fonctionnelles avec pure-ftpd
je ne vois plus trop d'où ça peut venir
Merci pour vos bons conseils
Dernière modification par totophe56 (14-11-2014 23:59:46)
Hors ligne
Hors ligne
Ensuite, pour le module ssl, tu as bien fait :
Enfin, le tuto lance le script d'init à la main, ce qui est une très mauvaise pratique (car les variables d'environnements ne sont pas nettoyées, le système d'init utilisé n'est pas forcément le bon, etc.). À la place, il faut faire :
captnfab,
Association Debian-Facile, bépo.
TheDoctor: Your wish is my command… But be careful what you wish for.
Hors ligne
Hors ligne
Y − 3HG − Auto-hébergé
Hors ligne
Quand tu "reload" apache, y a-t-il un quelconque message d'erreur dans les logs?
pas de message d'erreur non et je ne vois rien qui concerne le port 443 dans les log
/var/log/apache2/acces.log
/var/log/apache2/access.log.1
/var/log/apache2/error.log
/var/log/apache2/error.log.1
/var/log/apache2/other_vhosts_access.log = vide
Hors ligne
Tu peux passer LogLevel warn à LogLevel debug dans ton fichier apache2.conf afin de rendre les logs plus bavards (si ce n'est pas déja fait...).
Cette commande peut débloquer des choses je crois (redémarrage en douceur):
Le post 8 de ce lien http://www.webhostingtalk.com/showthread.php?t=1236986 peut également t'aider...
En espérant que ça t'aidera à avancer...
@+
Leonlemouton
°(")°
Hors ligne
j'ai commenté la ligne NameVirtualHost *.80 et NameVirtualHost *.443 dans mon ports.conf, vu que je reste sur localhost mais ça ne change rien, je me connecte en http et pas en https
mon dernier error.log
toujours rien à propos du port 443
Hors ligne
Leonlemouton
°(")°
Hors ligne
oki; peut-être ça :
http://serverfault.com/questions/576939 … -no-effect
The solution to your problem is to remove the NameVirtualHost directive.=> la solution : enlever la directive NameVirtualHost
...
@+
pardon, je me suis mal exprimé
j'ai commenté les directives virtualhost(même résultat que de supprimer les lignes) et plus de message d'erreur
mais cela ne change rien quand au non fonctionnement du https
Hors ligne
captnfab,
Association Debian-Facile, bépo.
TheDoctor: Your wish is my command… But be careful what you wish for.
Hors ligne
pardon, je me suis mal exprimé
C'est moi ; j'ai lu trop vite...
Voici mon ssl.conf ; si tu veux essayer...
Leonlemouton
°(")°
Hors ligne
pardon, je me suis mal exprimé
C'est moi ; j'ai lu trop vite...
Voici mon ssl.conf ; si tu veux essayer...<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
# 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/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/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.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/apache2/ssl.crt/server-ca.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
# 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 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>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
tout pareil
en pensant que default-ssl.conf-save pouvait entrer en conflit, j'ai essayé :
je fais quoi je le supprime manuellement ?
Dernière modification par totophe56 (14-11-2014 23:55:08)
Hors ligne
Donc, clairement, tu n'as pas activé le module ssl
captnfab,
Association Debian-Facile, bépo.
TheDoctor: Your wish is my command… But be careful what you wish for.
Hors ligne
merci tout plein à vous
Problème résolu
Merdouille ..... plus d'excuses pour pas développer
Dernière modification par totophe56 (14-11-2014 23:59:18)
Hors ligne
Leonlemouton
°(")°
Hors ligne
Que le site soit beau !!
on va essayer
y'a plus qu'à faire une mise à niveau xhtml 4.1 html5
Hors ligne
Pages : 1