ich habe meinen Server auf Debian Jessie aktualisiert. Seit dem ist ?ber den Apache keine SSL Verbindung mehr m?glich. Im Browser bekomm ich die Fehlermeldung "ssl_error_rx_record_too_long". Ein Test der SSL-Verbindung auf z. B. sslshopper.com, gibt folgende Fehlermeldung:
"No SSL certificates were found on domain1.de. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server's firewall."
Die Domain zeigt auf den korrekten Server und die korrekte IP. Die Firewall wurde deaktiviert und alle Einstellungen in Froxlor entsprechend gesetzt. Im Error-Log des Apache oder der Domain kommt dazu kein Fehler an, da scheinbar erst gar keine korrekt SSL Verbindung aufgebaut werden kann. In Froxlor ist Apache 2.4 aktiviert. Zertifikate sind alle g?ltig bis 2016 und die Checksum von crt und key sind identisch.
Als vHosts hab ich folgende:
lrwxrwxrwx 1 root root 35 Mai 5 09:29 000-default.conf -> ../sites-available/000-default.conf
lrwxrwxrwx 1 root root 35 Mai 5 10:51 000-default-ssl -> ../sites-available/default-ssl.conf
-rw-r--r-- 1 root root 818 Mai 4 16:57 10_froxlor_ipandport_IP.443.conf
-rw-r--r-- 1 root root 807 Mai 4 16:57 10_froxlor_ipandport_IP.80.conf
-rw-r--r-- 1 root root 1,4K Mai 4 16:57 22_froxlor_normal_vhost_domain2.de.conf
-rw-r--r-- 1 root root 1,4K Mai 4 16:57 22_froxlor_normal_vhost_domain1.de.conf
-rw-r--r-- 1 root root 1,8K Mai 4 16:57 22_froxlor_ssl_vhost_domain2.de.conf
-rw-r--r-- 1 root root 1,8K Mai 4 16:57 22_froxlor_ssl_vhost_domain1.de.conf
lrwxrwxrwx 1 root root 35 Mai 5 09:29 default-ssl.conf -> ../sites-available/default-ssl.conf
Benenne ich z. B. 22_froxlor_ssl_vhost_domain1.de.conf in 00_froxlor_ssl_vhost_domain1.de.conf um, ist die SSL-Verbindung zu dieser Domain korrekt m?glich. Mache ich dies weider r?ckg?ngig, ist keine SSL-Verbindung mehr m?glich. Ich seh allerdings nicht den Fehler bzw. die Ursache, die den Fehler verursacht. Scheinbar erfolgt kein korrektes "Durchreichen" der Verbindung zu dem SSL vhost. Ich hab jetzt schon vieles gepr?ft, komme aber nicht weiter. Hat vielleicht jemand einen Tipp f?r mich? Mit Wheezy und Apache 2.2 lief alles mit den gleichen Einstellungen korrekt.
10_froxlor_ipandport_IP.80.conf
# 10_froxlor_ipandport_IP.80.conf
# Created 05.05.2015 08:55
# Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
<VirtualHost IP:80>
DocumentRoot "/var/www/froxlor/"
ServerName www.froxlordomain.de
FastCgiExternalServer /var/www/php-fpm/froxlor.panel/www.froxlordomain.de/e23b.fpm.external -socket /var/lib/apache2/fastcgi/froxlor.panel-www.froxlordomain.de-php-fpm.socket -idle-timeout 180
<Directory "/var/www/froxlor/">
<FilesMatch "\.(php)$">
AddHandler php5-fastcgi .php
Action php5-fastcgi /fastcgiphp
Options +ExecCGI
</FilesMatch>
Require all granted
</Directory>
Alias /fastcgiphp /var/www/php-fpm/froxlor.panel/www.froxlordomain.de/e23b.fpm.external
</VirtualHost>
10_froxlor_ipandport_IP.443.conf
# 10_froxlor_ipandport_IP.443.conf
# Created 05.05.2015 09:43
# Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
<VirtualHost IP:443>
DocumentRoot "/var/www/froxlor/"
ServerName www.froxlordomain.de
FastCgiExternalServer /var/www/php-fpm/froxlor.panel/www.froxlordomain.de/8afc.ssl-fpm.external -socket /var/lib/apache2/fastcgi/froxlor.panel-www.froxlordomain.de-php-fpm.socket -idle-timeout 180
<Directory "/var/www/froxlor/">
<FilesMatch "\.(php)$">
AddHandler php5-fastcgi .php
Action php5-fastcgi /fastcgiphp
Options +ExecCGI
</FilesMatch>
Require all granted
</Directory>
Alias /fastcgiphp /var/www/php-fpm/froxlor.panel/www.froxlordomain.de/8afc.ssl-fpm.external
</VirtualHost>
22_froxlor_normal_vhost_domain1.de.conf
# 22_froxlor_normal_vhost_domain1.de.conf
# Created 05.05.2015 09:43
# Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
# Domain ID: 1 - CustomerID: 1 - CustomerLogin: domain1
<VirtualHost IP:80>
ServerName domain1.de
ServerAlias www.domain1.de
ServerAdmin test@domain1.de
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^/(.*) https://domain1.de/$1'>https://domain1.de/$1
</IfModule>
Redirect / https://domain1.de/
</VirtualHost>
22_froxlor_ssl_vhost_domain1.de.conf
# 22_froxlor_ssl_vhost_domain1.de.conf
# Created 05.05.2015 09:43
# Do NOT manually edit this file, all changes will be deleted after the next domain change at the panel.
# Domain ID: 1 (SSL) - CustomerID: 1 - CustomerLogin: x-dast
<VirtualHost IP:443>
ServerName domain1.de
ServerAlias www.domain1.de
ServerAdmin test@domain1.de
SSLEngine On
SSLProtocol ALL -SSLv2 -SSLv3
SSLHonorCipherOrder On
SSLCipherSuite AES256+EECDH:AES256+EDH
SSLVerifyDepth 10
SSLCertificateFile /etc/ssl/froxlor-custom/domain1.de.crt
SSLCertificateKeyFile /etc/ssl/froxlor-custom/domain1.de.key
SSLCACertificateFile /etc/ssl/froxlor-custom/domain1.de_CA.pem
SSLCertificateChainFile /etc/ssl/froxlor-custom/domain1.de_chain.pem
DocumentRoot "/var/customers/webs/x-dast/websites/main/"
SuexecUserGroup "x-dast" "x-dast"
FastCgiExternalServer /var/www/php-fpm/x-dast/domain1.de/ssl-fpm.external -socket /var/lib/apache2/fastcgi/x-dast-domain1.de-php-fpm.socket -idle-timeout 180
<Directory "/var/customers/webs/x-dast/websites/main/">
<FilesMatch "\.php$">
SetHandler php5-fastcgi
Action php5-fastcgi /fastcgiphp
Options +ExecCGI
</FilesMatch>
Require all granted
</Directory>
Alias /fastcgiphp /var/www/php-fpm/x-dast/domain1.de/ssl-fpm.external
Alias /webalizer "/var/customers/webs/x-dast/webalizer"
ErrorLog "/var/customers/logs/x-dast-error.log"
CustomLog "/var/customers/logs/x-dast-access.log" combined
</VirtualHost>
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.
# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration snippets which manage modules,
# global configuration fragments, or virtual host configurations,
# respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.
# Global configuration
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5
# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log
#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn
# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
# Include list of ports to listen on
Include ports.conf
# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
Options FollowSymLinks
AllowOverride None
Require all denied
</Directory>
<Directory /usr/share>
AllowOverride None
Require all granted
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
#<Directory /srv/>
# Options Indexes FollowSymLinks
# AllowOverride None
# Require all granted
#</Directory>
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Require all denied
</FilesMatch>
#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.
# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf
# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
ssl.conf
<IfModule mod_ssl.c>
# 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 builtin
SSLRandomSeed startup file:/dev/urandom 512
SSLRandomSeed connect builtin
SSLRandomSeed connect file:/dev/urandom 512
##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##
#
# Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl .crl
# 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 exec:/usr/share/apache2/ask-for-passphrase
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
# (The mechanism dbm has known memory leaks and should not be used).
#SSLSessionCache dbm:${APACHE_RUN_DIR}/ssl_scache
SSLSessionCache shmcb:${APACHE_RUN_DIR}/ssl_scache(512000)
SSLSessionCacheTimeout 300
# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
# (Disabled by default, the global Mutex directive consolidates by default
# this)
#Mutex file:${APACHE_LOCK_DIR}/ssl_mutex ssl-cache
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate. See the
# ciphers(1) man page from the openssl package for list of all available
# options.
# Enable only secure ciphers:
SSLCipherSuite HIGH:!aNULL
# SSL server cipher order preference:
# Use server priorities for cipher algorithm choice.
# Clients may prefer lower grade encryption. You should enable this
# option if you want to enforce stronger encryption, and can afford
# the CPU cost, and did not override SSLCipherSuite in a way that puts
# insecure ciphers first.
# Default: Off
#SSLHonorCipherOrder on
# The protocols to enable.
# Available values: all, SSLv3, TLSv1, TLSv1.1, TLSv1.2
# SSL v2 is no longer supported
SSLProtocol all -SSLv3
# Allow insecure renegotiation with clients which do not yet support the
# secure renegotiation protocol. Default: Off
#SSLInsecureRenegotiation on
# Whether to forbid non-SNI clients to access name based virtual hosts.
# Default: Off
#SSLStrictSNIVHostCheck On
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
ports.conf
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
apache2ctl -S
[10:58:28 root /etc/apache2/mods-available]> apache2ctl -S
VirtualHost configuration:
IP:80 is a NameVirtualHost
default server www.froxlordomain.de (/etc/apache2/sites-enabled/10_froxlor_ipandport_IP.80.conf:5)
port 80 namevhost www.froxlordomain.de (/etc/apache2/sites-enabled/10_froxlor_ipandport_IP.80.conf:5)
port 80 namevhost domain2.de (/etc/apache2/sites-enabled/22_froxlor_normal_vhost_domain2.de.conf:6)
alias www.domain2.de
port 80 namevhost domain1.de (/etc/apache2/sites-enabled/22_froxlor_normal_vhost_domain1.de.conf:6)
alias www.domain1.de
IP:443 is a NameVirtualHost
default server www.froxlordomain.de (/etc/apache2/sites-enabled/10_froxlor_ipandport_IP.443.conf:5)
port 443 namevhost www.froxlordomain.de (/etc/apache2/sites-enabled/10_froxlor_ipandport_IP.443.conf:5)
port 443 namevhost domain2.de (/etc/apache2/sites-enabled/22_froxlor_ssl_vhost_domain2.de.conf:6)
alias www.domain2.de
port 443 namevhost domain1.de (/etc/apache2/sites-enabled/22_froxlor_ssl_vhost_domain1.de.conf:6)
alias www.domain1.de
port 443 namevhost froxlordomain.de (/etc/apache2/sites-enabled/default-ssl.conf:2)
*:80 froxlordomain.de (/etc/apache2/sites-enabled/000-default.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/lock/apache2" mechanism=fcntl
Mutex mpm-accept: using_defaults
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
Define: ENABLE_USR_LIB_CGI_BIN
User: name="www-data" id=33
Group: name="www-data" id=33
Question
x-dast
Hallo,
ich habe meinen Server auf Debian Jessie aktualisiert. Seit dem ist ?ber den Apache keine SSL Verbindung mehr m?glich. Im Browser bekomm ich die Fehlermeldung "ssl_error_rx_record_too_long". Ein Test der SSL-Verbindung auf z. B. sslshopper.com, gibt folgende Fehlermeldung:
"No SSL certificates were found on domain1.de. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server's firewall."
Die Domain zeigt auf den korrekten Server und die korrekte IP. Die Firewall wurde deaktiviert und alle Einstellungen in Froxlor entsprechend gesetzt. Im Error-Log des Apache oder der Domain kommt dazu kein Fehler an, da scheinbar erst gar keine korrekt SSL Verbindung aufgebaut werden kann. In Froxlor ist Apache 2.4 aktiviert. Zertifikate sind alle g?ltig bis 2016 und die Checksum von crt und key sind identisch.
Als vHosts hab ich folgende:
Benenne ich z. B. 22_froxlor_ssl_vhost_domain1.de.conf in 00_froxlor_ssl_vhost_domain1.de.conf um, ist die SSL-Verbindung zu dieser Domain korrekt m?glich. Mache ich dies weider r?ckg?ngig, ist keine SSL-Verbindung mehr m?glich. Ich seh allerdings nicht den Fehler bzw. die Ursache, die den Fehler verursacht. Scheinbar erfolgt kein korrektes "Durchreichen" der Verbindung zu dem SSL vhost. Ich hab jetzt schon vieles gepr?ft, komme aber nicht weiter. Hat vielleicht jemand einen Tipp f?r mich? Mit Wheezy und Apache 2.2 lief alles mit den gleichen Einstellungen korrekt.
10_froxlor_ipandport_IP.80.conf
10_froxlor_ipandport_IP.443.conf
22_froxlor_normal_vhost_domain1.de.conf
22_froxlor_ssl_vhost_domain1.de.conf
mods-enabled:
conf-enabled:
apache2.conf
ssl.conf
ports.conf
apache2ctl -S
openssl s_client -connect domain1.de:443 -state -debug
Gru? x-dast
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.