Pages : 1
#1 Le 23/03/2026, à 23:08
- gilles deloustal
RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Bonjour
Je suis en train de transférer mes sites sur mon ordinateur portable et tout a déraillé après de nombreuses tentatives d'obtenir un certificat ssl avec certbot pour un nouveau site. Et soudain, j'obtiens un échec de connexion sécurisée sur informer38 qui marchait bien.
J'ai dé-installé le LAMP et l'ai ré-installé. Avec certbot j'ai demandé de nouveaux certificats sans amélioration.
Je suis sous ubuntu 24.04
J'ai installé gufw, mais j'ai inactivé le firewall
sudo ufw status
État : inactifJ'avais un site informer38.ovh qui marchait bien et maintenant j'obtiens l'erreur SSL_ERROR_RX_RECORD_TOO_LONG
<VirtualHost *:80>
ServerName informer38.ovh
ServerAlias www.informer38.ovh
DocumentRoot "/var/www/nextcloud"
<Directory "/var/www/nextcloud">
Options +FollowSymLinks
AllowOverride all
Require all granted
</Directory>
ErrorLog /var/log/apache2/error.informer38.ovh.log
CustomLog /var/log/apache2/access.informer38.ovh.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =informer38.ovh [OR]
RewriteCond %{SERVER_NAME} =www.informer38.ovh
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
<VirtualHost *:443>
ServerName informer38.ovh
ServerAlias www.informer38.ovh
ServerAdmin webmaster@informer38.ovh
DocumentRoot "/var/www/nextcloud"
<Directory "/var/www/nextcloud">
Options -Indexes +FollowSymLinks +MultiViews
AllowOverride none
Require all granted
</Directory>
# directives obligatoires pour TLS
SSLEngine on
# Header always set Strict-Transport-Security "max-age=15768000"
ErrorLog /var/log/apache2/error.informer38.ovh.log
CustomLog /var/log/apache2/access.informer38.ovh.log combined
SSLCertificateFile /etc/letsencrypt/live/informer38.ovh/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/informer38.ovh/privkey.pem
</VirtualHost>DNS via HTTPS dans firefox est désactivé
sudo certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: decidim.ovh
2: www.decidim.ovh
3: informer38.ovh
4: www.informer38.ovh
5: nextcloud.localhost
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 3
Certificate not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/informer38.ovh.conf)
What would you like to do?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Attempt to reinstall this existing certificate
2: Renew & replace the certificate (may be subject to CA rate limits)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Renewing an existing certificate for informer38.ovh
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/informer38.ovh/fullchain.pem
Key is saved at: /etc/letsencrypt/live/informer38.ovh/privkey.pem
This certificate expires on 2026-06-21.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
Deploying certificate
Successfully deployed certificate for informer38.ovh to /etc/apache2/sites-enabled/informer38.conf
Your existing certificate has been successfully renewed, and the new certificate has been installed.apachectl configtest
AH00526: Syntax error on line 36 of /etc/apache2/sites-enabled/informer38.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/informer38.ovh/fullchain.pem' does not exist or is emptysudo bluefish /etc/letsencrypt/live/informer38.ovh/fullchain.pem
-----BEGIN CERTIFICATE-----
MIIDiDCCAw6gAwIBAgISBpYI8bw5z/3SOypKu04z3OESMAoGCCqGSM49BAMDMDIx
CzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQDEwJF
ODAeFw0yNjAzMjMxOTMzNTJaFw0yNjA2MjExOTMzNTFaMBkxFzAVBgNVBAMTDmlu
Zm9ybWVyMzgub3ZoMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAERpw/153fQpuV
KcrxTJrdRrx5NTmeWp+GwiTyk1miHPzRfzKO3Qw3mGx5pVLt337hsfNitptqewBh
BUfc26dKLqOCAhswggIXMA4GA1UdDwEB/wQEAwIHgDATBgNVHSUEDDAKBggrBgEF
BQcDATAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBRqwbYmUECnHbiIyf/59TA+iokU
LjAfBgNVHSMEGDAWgBSPDROi9i5+0VBsMxg4XVmOI3KRyjAyBggrBgEFBQcBAQQm
MCQwIgYIKwYBBQUHMAKGFmh0dHA6Ly9lOC5pLmxlbmNyLm9yZy8wGQYDVR0RBBIw
EIIOaW5mb3JtZXIzOC5vdmgwEwYDVR0gBAwwCjAIBgZngQwBAgEwLQYDVR0fBCYw
JDAioCCgHoYcaHR0cDovL2U4LmMubGVuY3Iub3JnLzE5LmNybDCCAQ0GCisGAQQB
1nkCBAIEgf4EgfsA+QB3AJaXZL9VWJet90OHaDcIQnfp8DrV9qTzNm5GpD8PyqnG
AAABnRxmC/sAAAQDAEgwRgIhANRQdiztd74mt6L/52dF1hGyv3zrvHuGJT8dC9pw
TORZAiEArjCYEwph/i5wMVwd57fmbnvrfJIgjzWhIAclIAB9ZIMAfgAai51pSleY
yJmgyoi99I/AtFZgzMNgDR9x9Gn/x9GsowAAAZ0cZhyUAAgAAAUAWEatGQQDAEcw
RQIgYuGNfSpsLdByA7cQJ/mJ6p8gFuD2nTSkFLmtZkdrJoECIQCm5LBpcxosxPnO
xBxhw5wJdf2cs/Za1wh0Ph+wW01iZDAKBggqhkjOPQQDAwNoADBlAjAcv987fRzq
SsFkvbQlUChtF3+4iBu3ZVvZP9gqHtd57rI61zVVuMu0jSTvxJdrgRcCMQD+GbEw
08WasiayDM2daN/kED3+9cDalqIRIMACooldAHpmoWJ3BBgiwPYSY4uqkZQ=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIEVjCCAj6gAwIBAgIQY5WTY8JOcIJxWRi/w9ftVjANBgkqhkiG9w0BAQsFADBP
MQswCQYDVQQGEwJVUzEpMCcGA1UEChMgSW50ZXJuZXQgU2VjdXJpdHkgUmVzZWFy
Y2ggR3JvdXAxFTATBgNVBAMTDElTUkcgUm9vdCBYMTAeFw0yNDAzMTMwMDAwMDBa
Fw0yNzAzMTIyMzU5NTlaMDIxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBF
bmNyeXB0MQswCQYDVQQDEwJFODB2MBAGByqGSM49AgEGBSuBBAAiA2IABNFl8l7c
S7QMApzSsvru6WyrOq44ofTUOTIzxULUzDMMNMchIJBwXOhiLxxxs0LXeb5GDcHb
R6EToMffgSZjO9SNHfY9gjMy9vQr5/WWOrQTZxh7az6NSNnq3u2ubT6HTKOB+DCB
9TAOBgNVHQ8BAf8EBAMCAYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMB
MBIGA1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0OBBYEFI8NE6L2Ln7RUGwzGDhdWY4j
cpHKMB8GA1UdIwQYMBaAFHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEB
BCYwJDAiBggrBgEFBQcwAoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzATBgNVHSAE
DDAKMAgGBmeBDAECATAnBgNVHR8EIDAeMBygGqAYhhZodHRwOi8veDEuYy5sZW5j
ci5vcmcvMA0GCSqGSIb3DQEBCwUAA4ICAQBnE0hGINKsCYWi0Xx1ygxD5qihEjZ0
RI3tTZz1wuATH3ZwYPIp97kWEayanD1j0cDhIYzy4CkDo2jB8D5t0a6zZWzlr98d
AQFNh8uKJkIHdLShy+nUyeZxc5bNeMp1Lu0gSzE4McqfmNMvIpeiwWSYO9w82Ob8
otvXcO2JUYi3svHIWRm3+707DUbL51XMcY2iZdlCq4Wa9nbuk3WTU4gr6LY8MzVA
aDQG2+4U3eJ6qUF10bBnR1uuVyDYs9RhrwucRVnfuDj29CMLTsplM5f5wSV5hUpm
Uwp/vV7M4w4aGunt74koX71n4EdagCsL/Yk5+mAQU0+tue0JOfAV/R6t1k+Xk9s2
HMQFeoxppfzAVC04FdG9M+AC2JWxmFSt6BCuh3CEey3fE52Qrj9YM75rtvIjsm/1
Hl+u//Wqxnu1ZQ4jpa+VpuZiGOlWrqSP9eogdOhCGisnyewWJwRQOqK16wiGyZeR
xs/Bekw65vwSIaVkBruPiTfMOo0Zh4gVa8/qJgMbJbyrwwG97z/PRgmLKCDl8z3d
tA0Z7qq7fta0Gl24uyuB05dqI5J1LvAzKuWdIjT1tP8qCoxSE/xpix8hX2dt3h+/
jujUgFPFZ0EVZ0xSyBNRF3MboGZnYXFUxpNjTWPKpagDHJQmqrAcDmWJnMsFY3jS
u1igv3OefnWjSQ==
-----END CERTIFICATE-----sudo bluefish /etc/letsencrypt/renewal/informer38.ovh.conf
version = 5.4.0
archive_dir = /etc/letsencrypt/archive/informer38.ovh
cert = /etc/letsencrypt/live/informer38.ovh/cert.pem
privkey = /etc/letsencrypt/live/informer38.ovh/privkey.pem
chain = /etc/letsencrypt/live/informer38.ovh/chain.pem
fullchain = /etc/letsencrypt/live/informer38.ovh/fullchain.pem
[renewalparams]
account = fff5ff955ebe70bf1ea570d55c34d254
authenticator = apache
server = https://acme-v02.api.letsencrypt.org/directory
key_type = ecdsa
installer = apache
[acme_renewal_info]
ari_retry_after = 2026-03-23T22:11:29sudo ss -tnlp
[sudo] Mot de passe de gilles :
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 4096 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=2076,fd=8))
LISTEN 0 32 10.0.3.1:53 0.0.0.0:* users:(("dnsmasq",pid=2881,fd=7))
LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=981,fd=15))
LISTEN 0 70 127.0.0.1:33060 0.0.0.0:* users:(("mysqld",pid=2199,fd=21))
LISTEN 0 128 127.0.0.1:5939 0.0.0.0:* users:(("teamviewerd",pid=2845,fd=16))
LISTEN 0 4096 0.0.0.0:22 0.0.0.0:* users:(("systemd",pid=1,fd=143))
LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=981,fd=17))
LISTEN 0 151 127.0.0.1:3306 0.0.0.0:* users:(("mysqld",pid=2199,fd=25))
LISTEN 0 4096 [::1]:631 [::]:* users:(("cupsd",pid=2076,fd=7))
LISTEN 0 511 *:443 *:* users:(("apache2",pid=37978,fd=6),("apache2",pid=37977,fd=6),("apache2",pid=37719,fd=6),("apache2",pid=37718,fd=6),("apache2",pid=36257,fd=6),("apache2",pid=35999,fd=6),("apache2",pid=35998,fd=6),("apache2",pid=35997,fd=6),("apache2",pid=35996,fd=6),("apache2",pid=35995,fd=6),("apache2",pid=33206,fd=6))
LISTEN 0 4096 [::]:22 [::]:* users:(("systemd",pid=1,fd=146))
LISTEN 0 511 *:80 *:* users:(("apache2",pid=37978,fd=4),("apache2",pid=37977,fd=4),("apache2",pid=37719,fd=4),("apache2",pid=37718,fd=4),("apache2",pid=36257,fd=4),("apache2",pid=35999,fd=4),("apache2",pid=35998,fd=4),("apache2",pid=35997,fd=4),("apache2",pid=35996,fd=4),("apache2",pid=35995,fd=4),("apache2",pid=33206,fd=4))Cordialement
Dernière modification par gilles deloustal (Le 25/03/2026, à 20:42)
Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne
#2 Le 24/03/2026, à 08:44
- gilles deloustal
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Bonjour
J'ai remis un peu d'ordre dans mon informer38.conf et je trouve cette erreur sur la commande HEADER bizarre.
<VirtualHost *:80>
ServerName informer38.ovh
ServerAlias www.informer38.ovh
DocumentRoot "/var/www/nextcloud"
<Directory "/var/www/nextcloud">
Options +FollowSymLinks
AllowOverride all
Require all granted
</Directory>
ErrorLog /var/log/apache2/error.informer38.ovh.log
CustomLog /var/log/apache2/access.informer38.ovh.log combined
</VirtualHost>
<VirtualHost *:443>
ServerName informer38.ovh
ServerAlias www.informer38.ovh
ServerAdmin webmaster@informer38.ovh
DocumentRoot "/var/www/nextcloud"
<Directory "/var/www/nextcloud">
Options -Indexes +FollowSymLinks +MultiViews
AllowOverride none
Require all granted
</Directory>
# directives obligatoires pour TLS
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/informer38.ovh/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/informer38.ovh/privkey.pem
Header always set Strict-Transport-Security "max-age=15768000"
ErrorLog /var/log/apache2/error.informer38.ovh.log
CustomLog /var/log/apache2/access.informer38.ovh.log combined
</VirtualHost>gilles@gilles:~$ sudo a2dissite informer38
[sudo] Mot de passe de gilles :
Site informer38 disabled.
To activate the new configuration, you need to run:
systemctl reload apache2
gilles@gilles:~$ sudo a2ensite informer38
Enabling site informer38.
To activate the new configuration, you need to run:
systemctl reload apache2
gilles@gilles:~$ systemctl reload apache2
Job for apache2.service failed.
See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details.journalctl -xeu apache2.service
mars 24 07:39:18 gilles systemd[1]: Reloading apache2.service - The Apache HTTP>
░░ Subject: L'unité (unit) apache2.service a commencé à recharger sa configurat>
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a commencé à recharger sa configuration.
mars 24 07:39:18 gilles apachectl[5840]: AH00526: Syntax error on line 29 of /e>
mars 24 07:39:18 gilles apachectl[5840]: Invalid command 'Header', perhaps miss>
mars 24 07:39:18 gilles systemd[1]: apache2.service: Control process exited, co>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecReload= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mars 24 07:39:18 gilles systemd[1]: Reload failed for apache2.service - The Apa>
░░ Subject: L'unité (unit) apache2.service a terminé de recharger configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a terminé de recharger configuration,
░░ avec le résultat failed.Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne
#3 Le 24/03/2026, à 08:51
- gilles deloustal
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Un peu plus facile à lire
journalctl -xeu apache2.service
mars 24 07:32:57 gilles apachectl[2225]: AH00558: apache2: Could not reliably determine the server's fully qualified domain nam>
mars 24 07:32:58 gilles systemd[1]: Started apache2.service - The Apache HTTP Server.
░░ Subject: L'unité (unit) apache2.service a terminé son démarrage
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a terminé son démarrage, avec le résultat done.
mars 24 07:39:18 gilles systemd[1]: Reloading apache2.service - The Apache HTTP Server...
░░ Subject: L'unité (unit) apache2.service a commencé à recharger sa configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a commencé à recharger sa configuration.
mars 24 07:39:18 gilles apachectl[5840]: AH00526: Syntax error on line 29 of /etc/apache2/sites-enabled/informer38.conf:
mars 24 07:39:18 gilles apachectl[5840]: Invalid command 'Header', perhaps misspelled or defined by a module not included in th>
mars 24 07:39:18 gilles systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecReload= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mars 24 07:39:18 gilles systemd[1]: Reload failed for apache2.service - The Apache HTTP Server.
░░ Subject: L'unité (unit) apache2.service a terminé de recharger configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a terminé de recharger configuration,
░░ avec le résultat failed.Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne
#4 Le 24/03/2026, à 20:37
- gilles deloustal
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Bonjour
J'ai tout repris à zéro et ré-installé lamp php mysql
J'ai un site dans /var/www/nexcloud auquel j'accède correctement en local par nexcloud.localhost
<VirtualHost *:80>
ServerAdmin webmaster@localhost
ServerName nextcloud.localhost
DocumentRoot /var/www/nextcloud
<Directory /var/www/nextcloud/>
Require all granted
AllowOverride All
Options FollowSymLinks MultiViews
</Directory>
</VirtualHost>Maintenant, je veux y accéder à partir de informer38.ovh
<VirtualHost *:80>
ServerAdmin webmaster@informer38.ovh
ServerName informer38.ovh
ServerAlias www.informer38.ovh
DocumentRoot "/var/www/nextcloud"
<Directory "/var/www/nextcloud">
Options +FollowSymLinks
AllowOverride all
Require all granted
</Directory>
ErrorLog /var/log/apache2/error.informer38.ovh.log
CustomLog /var/log/apache2/access.informer38.ovh.log combinedet j'obtiens une erreur dans /etc/apache2/apache2.conf
journalctl -xeu apache2.service
░░ The process' exit code is 'exited' and its exit status is 1.
mars 24 19:21:25 gilles systemd[1]: Reload failed for apache2.service - The Apache HTTP Server.
░░ Subject: L'unité (unit) apache2.service a terminé de recharger configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a terminé de recharger configuration,
░░ avec le résultat failed.
mars 24 19:35:21 gilles systemd[1]: Reloading apache2.service - The Apache HTTP Server...
░░ Subject: L'unité (unit) apache2.service a commencé à recharger sa configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a commencé à recharger sa configuration.
mars 24 19:35:22 gilles apachectl[55695]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line >
mars 24 19:35:22 gilles systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecReload= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mars 24 19:35:22 gilles systemd[1]: Reload failed for apache2.service - The Apache HTTP Server.
░░ Subject: L'unité (unit) apache2.service a terminé de recharger configuration
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) apache2.service a terminé de recharger configuration,
░░ avec le résultat failed.Pour info, le firewall est inactif
J'ai ouvert les ports 80 et 443 dans ma livebox
netstat -a -n --inet -p
(Tous les processus ne peuvent être identifiés, les infos sur les processus
non possédés ne seront pas affichées, vous devez être root pour les voir toutes.)
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN -
tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:33060 0.0.0.0:* LISTEN -
tcp 0 0 192.168.1.149:46008 34.120.208.123:443 TIME_WAIT -
tcp 0 0 192.168.1.149:58190 192.168.1.1:80 TIME_WAIT -
tcp 0 0 192.168.1.149:58196 192.168.1.1:80 TIME_WAIT -
tcp 0 0 192.168.1.149:58226 192.168.1.1:80 TIME_WAIT -
tcp 0 0 192.168.1.149:58250 192.168.1.1:80 TIME_WAIT -
tcp 0 0 192.168.1.149:52572 34.107.243.93:443 ESTABLISHED 52445/firefox
tcp 0 0 192.168.1.149:44332 34.49.51.44:443 ESTABLISHED 52445/firefox
tcp 0 0 192.168.1.149:48424 34.111.211.209:443 TIME_WAIT -
udp 0 0 0.0.0.0:39568 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 10.0.3.1:53 0.0.0.0:* -
udp 0 0 127.0.0.54:53 0.0.0.0:* -
udp 0 0 127.0.0.53:53 0.0.0.0:* -
udp 0 0 0.0.0.0:67 0.0.0.0:* -
udp 0 0 192.168.1.149:68 192.168.1.1:67 ESTABLISHED - Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne
#5 Le 24/03/2026, à 22:31
- ujiko
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
mars 24 19:35:22 gilles apachectl[55695]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line >
Hors ligne
#6 Le 25/03/2026, à 11:38
- gilles deloustal
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Bonjour
J'ai mis cette ligne 225 en commentaire
# Include the virtual host configurations:
# IncludeOptional sites-enabled/*.confj'ai à nouveau enabled informer38 et re-démarré apache2, vérifié que le pare feu est inactif et tandis que http://informer38.ovh ne peut établir de connexion, nexcloud.localhost affiche désormais "it works" la page par défaut de /var/www/html.
En revanche, j'arrive à démarrer localhost/phpmyadmin
Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne
#7 Le 25/03/2026, à 11:46
- ujiko
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
J'en conclus qu'il y a une erreur dans le fichier de conf des hôtes virtuels.
Hors ligne
#8 Le 25/03/2026, à 16:38
- gilles deloustal
Re : RESOLU Echec de connexion SSL_ERROR_RX_RECORD_TOO_LONG
Un grand merci.
J'avais déjà mis un site en ssl par le passé et là je pense qu'il me manquait simplement de définir le port 80 dans la livebox.
J'ai remis gufw en marche. Voici mes règles. Te semblent-elles correctes ?
sudo ufw status
État : actif
Vers Action De
---- ------ --
443/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
53 ALLOW OUT Anywhere
53 (v6) ALLOW OUT Anywhere (v6)Cordialement
Je suis en Ubuntu 24.04.2 LTS installé from scratch depuis une clé usb
Lenovo intel core i3-2328Mx4 4Go RAM 500Go SSD
Hors ligne