The commands below have been run and nothing happens
[root@these ~]# rm -f /etc/pki/tls/certs/localhost.crt
[root@these ~]# rm -f /etc/pki/tls/private/localhost.key
[root@these ~]# ln -s /etc/letsencrypt/live/these.diahoua.com/fullchain.pem /etc/pki/tls/certs/localhost.crt
[root@these ~]# ln -s /etc/letsencrypt/live/these.diahoua.com/privkey.pem /etc/pki/tls/private/localhost.key
[root@these ~]# systemctl restart httpd.service
Your webserver is working now correctly over https, congratulations:
pi@raspberrypi:~ $ curl -s -v 'https://these.diahoua.com/' > /dev/null
* Expire in 0 ms for 6 (transfer 0x15358b0)
* Expire in 1 ms for 1 (transfer 0x15358b0)
* Expire in 0 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 1 ms for 1 (transfer 0x15358b0)
* Expire in 1 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 1 ms for 1 (transfer 0x15358b0)
* Expire in 1 ms for 1 (transfer 0x15358b0)
* Expire in 4 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 4 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 2 ms for 1 (transfer 0x15358b0)
* Expire in 5 ms for 1 (transfer 0x15358b0)
* Trying 37.59.161.180...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x15358b0)
* Connected to these.diahoua.com (37.59.161.180) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [25 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4034 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=these.diahoua.com
* start date: Jan 21 17:23:05 2022 GMT
* expire date: Apr 21 17:23:04 2022 GMT
* subjectAltName: host "these.diahoua.com" matched cert's "these.diahoua.com"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
} [5 bytes data]
> GET / HTTP/1.1
> Host: these.diahoua.com
> User-Agent: curl/7.64.0
> Accept: */*
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [281 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [281 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
< HTTP/1.1 403 Forbidden
< Date: Fri, 21 Jan 2022 18:30:41 GMT
< Server: Apache/2.4.37 (centos) OpenSSL/1.1.1c
< Last-Modified: Sun, 27 Jun 2021 23:47:13 GMT
< ETag: "30c0b-5c5c7fdeec240"
< Accept-Ranges: bytes
< Content-Length: 199691
< Content-Type: text/html; charset=UTF-8
<
{ [7921 bytes data]
* Connection #0 to host these.diahoua.com left intact
pi@raspberrypi:~ $
@bruncsak It's good, it works, thank you very much.
But what was blocking if you can explain for others who will have the same as me!
The program certbot does not handle correctly the default CentOS system, it requires some small massaging (webroot + symbolic links to the certificate data).
Thanks again to all of you for the time you spent on this post. Have a good weekend
Hello,
Since this morning, I seem to have been stuck trying to install Docker and Wekan, and I notice that the SSL no longer works.
Apache is inactive
So I did what is below to see if there were any ports already occupied
# netstat -punta | grep LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 25296/sshd
tcp6 0 0 :::22 :::* LISTEN 25296/sshd
# grep '443' /etc/httpd/conf.d/*
/etc/httpd/conf.d/ssl.conf:Listen 443 https
/etc/httpd/conf.d/ssl.conf:<VirtualHost _default_:443>
/etc/httpd/conf.d/ssl.conf:#ServerName www.example.com:443
# vim /etc/httpd/conf.d/ssl.conf
# vim /etc/httpd/conf.d/ssl.conf
Have you tried?:
systemctl start apache
As @rg305 wrote, you should start with the command the web server:
systemctl start httpd.service
However, you want to configure that after system reboot, the web server to start automatically:
systemctl enable httpd.service
[root@these ~]# systemctl start apache
Failed to start apache.service: Unit apache.service not found.
[root@these ~]# systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@these ~]# systemctl enable httpd.service
Created symlink /etc/systemd/system/multi-user.target.wants/httpd.service → /usr/lib/systemd/system/httpd.service
What does the command:
apachectl configtest
give?
Hello,
I don't remember running this command.
apachectl configtest
Unless I'm mistaken, I did this:
# systemctl start apache
# systemctl start httpd.service
# systemctl enable httpd.service
Please run it now, and let me know its output.
[root@these ~]# apachectl configtest
AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or is empty
Let's have a look at this file:
[root@these ~]# cat /etc/httpd/conf.d/ssl.conf
#
# When we also provide SSL we have to listen to the
# standard HTTPS port in addition.
#
Listen 443 https
##
## 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 exec:/usr/libexec/httpd-ssl-pass-dialog
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
SSLSessionCache shmcb:/run/httpd/sslcache(512000)
SSLSessionCacheTimeout 300
#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names. NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec
##
## SSL Virtual Host Context
##
<VirtualHost _default_:443>
# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com: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
# List the protocol versions which clients are allowed to connect with.
# The OpenSSL system profile is used by default. See
# update-crypto-policies(8) for more details.
#SSLProtocol all -SSLv3
#SSLProxyProtocol all -SSLv3
# User agents such as web browsers are not configured for the user's
# own preference of either security or performance, therefore this
# must be the prerogative of the web server administrator who manages
# cpu load versus confidentiality, so enforce the server's cipher order.
SSLHonorCipherOrder on
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
# The OpenSSL system profile is configured by default. See
# update-crypto-policies(8) for more details.
SSLCipherSuite PROFILE=SYSTEM
SSLProxyCipherSuite PROFILE=SYSTEM
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that restarting httpd will prompt again. Keep
# in mind that if you have both an RSA and a DSA certificate you
# can configure both in parallel (to also allow the use of DSA
# ciphers, etc.)
# Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
# require an ECC certificate which can also be configured in
# parallel.
SSLCertificateFile /etc/pki/tls/certs/localhost.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.)
# ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile /etc/pki/tls/private/localhost.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 convenience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.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
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<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 sent or allowed to be 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 sent 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-5]" \
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>
[root@these ~]#
That's a default and a pretty useless.
I'd delete it (or move it to another location).
Please execute the following command:
ls -l /etc/pki/tls/*/localhost.*
and give its result.
[root@these ~]# ls -l /etc/pki/tls/*/localhost.*
--w------- 1 root root 0 Jan 24 23:05 /etc/pki/tls/certs/localhost.crt
lrwxrwxrwx 1 root root 51 Jan 24 23:01 /etc/pki/tls/private/localhost.key -> /etc/letsencrypt/live/these.diahoua.com/privkey.pem
[root@these ~]#
Something overwrote the localhost.crt file. In addition too, it has very strange, unusual permission. So, please execute the following commands to fix the problem:
rm -f /etc/pki/tls/certs/localhost.crt
ln -s /etc/letsencrypt/live/these.diahoua.com/fullchain.pem /etc/pki/tls/certs/localhost.crt
systemctl start httpd.service
Please do not expect much output of these commands. UNIX is typically not very chatty, if all goes fine it keeps quiet.
[root@these ~]# rm -f /etc/pki/tls/certs/localhost.crt
[root@these ~]# ln -s /etc/letsencrypt/live/these.diahoua.com/fullchain.pem /etc/pki/tls/certs/localhost.crt
[root@these ~]# systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@these ~]#