\u672c\u7a3f\u3067\u306fLet\u2019s Encrypt\u3067\u30b5\u30fc\u30d0\u30fc\u8a3c\u660e\u66f8\u3092\u767a\u884c\u3059\u308b\u624b\u9806\u3092\u8a18\u8f09\u3057\u307e\u3059\u3002<\/p>\n
Tera Term\u3067\u8a72\u5f53\u30b5\u30fc\u30d0\u30fc\u306bSSH\u3067\u30ed\u30b0\u30a4\u30f3\u3057\u307e\u3059\u3002
\n\u30ed\u30b0\u30a4\u30f3\u3057\u305f\u3089\u4ee5\u4e0b\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002<\/p>\n
\u6539\u884c\u3059\u308b\u5834\u5408\uff1a\u6539\u884c\u306e\u524d\u306b\u300c\\\u300d\u3092\u5165\u308c\u308b<\/p>\n
\u5b9f\u884c\u3059\u308b\u3068\u4ee5\u4e0b\u304c\u8868\u793a\u3055\u308c\u307e\u3059\u3002<\/p>\n
[tmcadmin@TMCZXSV01 etc]$ sudo certbot certonly \\
\n–manual \\
\n–preferred-challenges dns \\
\n-d zabbix.three-meister.com
\nSaving debug log to \/var\/log\/letsencrypt\/letsencrypt.log
\nRequesting a certificate for zabbix.three-meister.com<\/p>\n
– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
\nPlease deploy a DNS TXT record under the name:<\/p>\n
_acme-challenge.zabbix.three-meister.com.<\/p>\n
with the following value:<\/p>\n
PnKFeEf2OE7f8qrHNk0abdPmS0UHo8s4dqXJLllcpM4<\/span><\/p>\n Before continuing, verify the TXT record has been deployed. Depending on the DNS – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – \u3053\u3053\u307e\u3067\u8868\u793a\u3055\u308c\u305f\u3089\u3001\u304a\u540d\u524d\u30c9\u30c3\u30c8\u30b3\u30e0\u306b\u30a2\u30af\u30bb\u30b9\u3057\u3066\u3001DNS\u306b\u4ee5\u4e0b\u3092\u767b\u9332\u3057\u307e\u3059\u3002<\/p>\n 10\u5206\u5f85\u3063\u305f\u5f8c\u3001\u30a8\u30f3\u30bf\u30fc\u30ad\u30fc\u3092\u62bc\u3057\u307e\u3059\u3002<\/p>\n<\/div>\n Successfully received certificate. NEXT STEPS: – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – \u8a3c\u660e\u66f8\u306e\u767a\u884c\u78ba\u8a8d\u3067\u4ee5\u4e0b\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002<\/p>\n \u4ee5\u4e0b\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3057\u3066ssl\u306e\u8a2d\u5b9a\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002<\/p>\n [tmcadmin@TMCZXSV01 etc]$ sudo cat \/etc\/httpd\/conf.d\/ssl.conf ## # Pass Phrase Dialog: # Inter-Process Session Cache: # ## <VirtualHost _default_:443><\/p>\n # General setup for the virtual host, inherited from global configuration # Use separate log files for the SSL virtual host; note that LogLevel # SSL Engine Switch: # List the protocol versions which clients are allowed to connect with. # User agents such as web browsers are not configured for the user’s # SSL Cipher Suite: # Point SSLCertificateFile at a PEM encoded certificate. If # Server Private Key: # Server Certificate Chain: # Certificate Authority (CA): # Client Authentication (Type): # Access Control: # SSL Engine Options: # SSL Protocol Adjustments: # Per-Server Logging: <\/VirtualHost><\/p>\n<\/div>\n<\/div>\n
\nprovider, this may take some time, from a few seconds to multiple minutes. You can
\ncheck if it has finished deploying with aid of online tools, such as the Google
\nAdmin Toolbox: https:\/\/toolbox.googleapps.com\/apps\/dig\/#TXT\/_acme-challenge.zabbix.three-meister.com.
\nLook for one or more bolded line(s) below the line ‘;ANSWER’. It should show the
\nvalue(s) you’ve just added.<\/p>\n
\nPress Enter to Continue<\/p>\n<\/div>\n
\n\u30db\u30b9\u30c8\u540d\uff1a_acme-challenge.zabbix
\nTTL:300
\n\u5024\uff1aPnKFeEf2OE7f8qrHNk0abdPmS0UHo8s4dqXJLllcpM4<\/span>
\n\u203b\u5024\u306f\u4e0a\u8a18\u306b\u8868\u793a\u3055\u308c\u3066\u3044\u308b\u30ad\u30fc\u3092\u8a2d\u5b9a<\/span><\/span>\u203b\u53cd\u6620\u307e\u30675\u5206\u304b\u304b\u308b\u305f\u3081\u300110\u5206\u7a0b\u5ea6\u653e\u7f6e\u3059\u308b<\/p>\n
\nCertificate is saved at: \/etc\/letsencrypt\/live\/zabbix.three-meister.com\/fullchain.pem
\nKey is saved at: \/etc\/letsencrypt\/live\/zabbix.three-meister.com\/privkey.pem
\nThis certificate expires on 2026-11-05.
\nThese files will be updated when the certificate renews.<\/p>\n
\n– This certificate will not be renewed automatically. Autorenewal of –manual certificates requires the use of an authentication hook script (–manual-auth-hook) but one was not provided. To renew this certificate, repeat this same certbot command before the certificate’s expiry date.<\/p>\n
\nIf you like Certbot, please consider supporting our work by:
\n* Donating to ISRG \/ Let’s Encrypt: https:\/\/letsencrypt.org\/donate
\n* Donating to EFF: https:\/\/eff.org\/donate-le
\n– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –<\/p>\n<\/div>\n<\/div>\n
\n-rw-r–r–. 1 root root 692 8\u6708 7 10:40 README
\nlrwxrwxrwx. 1 root root 48 8\u6708 7 10:40 cert.pem -> ..\/..\/archive\/zabbix.three-meister.com\/cert1.pem
\nlrwxrwxrwx. 1 root root 49 8\u6708 7 10:40 chain.pem -> ..\/..\/archive\/zabbix.three-meister.com\/chain1.pem
\nlrwxrwxrwx. 1 root root 53 8\u6708 7 10:40 fullchain.pem -> ..\/..\/archive\/zabbix.three-meister.com\/fullchain1.pem
\nlrwxrwxrwx. 1 root root 51 8\u6708 7 10:40 privkey.pem -> ..\/..\/archive\/zabbix.three-meister.com\/privkey1.pem<\/div>\n<\/div>\n\u8a3c\u660e\u66f8\u306e\u9069\u7528<\/h2>\n
\n[sudo] tmcadmin \u306e\u30d1\u30b9\u30ef\u30fc\u30c9:
\n#
\n# When we also provide SSL we have to listen to the
\n# standard HTTPS port in addition.
\n#
\nListen 443 https<\/p>\n
\n## SSL Global Context
\n##
\n## All SSL configuration in this context applies both to
\n## the main server and all SSL-enabled virtual hosts.
\n##<\/p>\n
\n# Configure the pass phrase gathering process.
\n# The filtering dialog program (`builtin’ is a internal
\n# terminal dialog) has to provide the pass phrase on stdout.
\nSSLPassPhraseDialog exec:\/usr\/libexec\/httpd-ssl-pass-dialog<\/p>\n
\n# Configure the SSL Session Cache: First the mechanism
\n# to use and second the expiring timeout (in seconds).
\nSSLSessionCache shmcb:\/run\/httpd\/sslcache(512000)
\nSSLSessionCacheTimeout 300<\/p>\n
\n# Use “SSLCryptoDevice” to enable any supported hardware
\n# accelerators. Use “openssl engine -v” to list supported
\n# engine names. NOTE: If you enable an accelerator and the
\n# server does not start, consult the error logs and ensure
\n# your accelerator is functioning properly.
\n#
\nSSLCryptoDevice builtin
\n#SSLCryptoDevice ubsec<\/p>\n
\n## SSL Virtual Host Context
\n##<\/p>\n
\n#DocumentRoot “\/var\/www\/html”
\nServerName zabbix.three-meister.com
\n\u203b\u30b3\u30e1\u30f3\u30c8\u3092\u5916\u3057\u3066\u3001\u30b5\u30fc\u30d0\u30fc\u540d\u3092\u5909\u66f4<\/span><\/p>\n
\n# is not inherited from httpd.conf.
\nErrorLog logs\/ssl_error_log
\nTransferLog logs\/ssl_access_log
\nLogLevel warn<\/p>\n
\n# Enable\/Disable SSL for this virtual host.
\nSSLEngine on<\/p>\n
\n# The OpenSSL system profile is used by default. See
\n# update-crypto-policies(8) for more details.
\n#SSLProtocol all -SSLv3
\n#SSLProxyProtocol all -SSLv3<\/p>\n
\n# own preference of either security or performance, therefore this
\n# must be the prerogative of the web server administrator who manages
\n# cpu load versus confidentiality, so enforce the server’s cipher order.
\nSSLHonorCipherOrder on<\/p>\n
\n# List the ciphers that the client is permitted to negotiate.
\n# See the mod_ssl documentation for a complete list.
\n# The OpenSSL system profile is configured by default. See
\n# update-crypto-policies(8) for more details.
\nSSLCipherSuite PROFILE=SYSTEM
\nSSLProxyCipherSuite PROFILE=SYSTEM<\/p>\n
\n# the certificate is encrypted, then you will be prompted for a
\n# pass phrase. Note that restarting httpd will prompt again. Keep
\n# in mind that if you have both an RSA and a DSA certificate you
\n# can configure both in parallel (to also allow the use of DSA
\n# ciphers, etc.)
\n# Some ECC cipher suites (http:\/\/www.ietf.org\/rfc\/rfc4492.txt)
\n# require an ECC certificate which can also be configured in
\n# parallel.
\nSSLCertificateFile \/etc\/letsencrypt\/live\/zabbix.three-meister.com\/fullchain.pem
\n\u203b\u5148\u307b\u3069\u767a\u884c\u3057\u305f\u8a3c\u660e\u66f8\u3092\u8a2d\u5b9a
\n<\/span><\/p>\n
\n# If the key is not combined with the certificate, use this
\n# directive to point at the key file. Keep in mind that if
\n# you’ve both a RSA and a DSA private key you can configure
\n# both in parallel (to also allow the use of DSA ciphers, etc.)
\n# ECC keys, when in use, can also be configured in parallel
\nSSLCertificateKeyFile \/etc\/letsencrypt\/live\/zabbix.three-meister.com\/privkey.pem
\n\u203b\u5148\u307b\u3069\u767a\u884c\u3057\u305f\u8a3c\u660e\u66f8Key<\/span>\u3092\u8a2d\u5b9a
\n<\/span><\/p>\n
\n# Point SSLCertificateChainFile at a file containing the
\n# concatenation of PEM encoded CA certificates which form the
\n# certificate chain for the server certificate. Alternatively
\n# the referenced file can be the same as SSLCertificateFile
\n# when the CA certificates are directly appended to the server
\n# certificate for convenience.
\n#SSLCertificateChainFile \/etc\/pki\/tls\/certs\/server-chain.crt<\/p>\n
\n# Set the CA certificate verification path where to find CA
\n# certificates for client authentication or alternatively one
\n# huge file containing all of them (file must be PEM encoded)
\n#SSLCACertificateFile \/etc\/pki\/tls\/certs\/ca-bundle.crt<\/p>\n
\n# Client certificate verification type and depth. Types are
\n# none, optional, require and optional_no_ca. Depth is a
\n# number which specifies how deeply to verify the certificate
\n# issuer chain before deciding the certificate is not valid.
\n#SSLVerifyClient require
\n#SSLVerifyDepth 10<\/p>\n
\n# With SSLRequire you can do per-directory access control based
\n# on arbitrary complex boolean expressions containing server
\n# variable checks and other lookup directives. The syntax is a
\n# mixture between C and Perl. See the mod_ssl documentation
\n# for more details.
\n#<Location \/>
\n#SSLRequire ( %{SSL_CIPHER} !~ m\/^(EXP|NULL)\/ \\
\n# and %{SSL_CLIENT_S_DN_O} eq “Snake Oil, Ltd.” \\
\n# and %{SSL_CLIENT_S_DN_OU} in {“Staff”, “CA”, “Dev”} \\
\n# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \\
\n# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \\
\n# or %{REMOTE_ADDR} =~ m\/^192\\.76\\.162\\.[0-9]+$\/
\n#<\/Location><\/p>\n
\n# Set various options for the SSL engine.
\n# o FakeBasicAuth:
\n# Translate the client X.509 into a Basic Authorisation. This means that
\n# the standard Auth\/DBMAuth methods can be used for access control. The
\n# user name is the `one line’ version of the client’s X.509 certificate.
\n# Note that no password is obtained from the user. Every entry in the user
\n# file needs this password: `xxj31ZMTZzkVA’.
\n# o ExportCertData:
\n# This exports two additional environment variables: SSL_CLIENT_CERT and
\n# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
\n# server (always existing) and the client (only existing when client
\n# authentication is used). This can be used to import the certificates
\n# into CGI scripts.
\n# o StdEnvVars:
\n# This exports the standard SSL\/TLS related `SSL_*’ environment variables.
\n# Per default this exportation is switched off for performance reasons,
\n# because the extraction step is an expensive operation and is usually
\n# useless for serving static content. So one usually enables the
\n# exportation for CGI and SSI requests only.
\n# o StrictRequire:
\n# This denies access when “SSLRequireSSL” or “SSLRequire” applied even
\n# under a “Satisfy any” situation, i.e. when it applies access is denied
\n# and no other module can change it.
\n# o OptRenegotiate:
\n# This enables optimized SSL connection renegotiation handling when SSL
\n# directives are used in per-directory context.
\n#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
\n<FilesMatch “\\.(cgi|shtml|phtml|php)$”>
\nSSLOptions +StdEnvVars
\n<\/FilesMatch>
\n<Directory “\/var\/www\/cgi-bin”>
\nSSLOptions +StdEnvVars
\n<\/Directory><\/p>\n
\n# The safe and default but still SSL\/TLS standard compliant shutdown
\n# approach is that mod_ssl sends the close notify alert but doesn’t wait for
\n# the close notify alert from client. When you need a different shutdown
\n# approach you can use one of the following variables:
\n# o ssl-unclean-shutdown:
\n# This forces an unclean shutdown when the connection is closed, i.e. no
\n# SSL close notify alert is sent or allowed to be received. This violates
\n# the SSL\/TLS standard but is needed for some brain-dead browsers. Use
\n# this when you receive I\/O errors because of the standard approach where
\n# mod_ssl sends the close notify alert.
\n# o ssl-accurate-shutdown:
\n# This forces an accurate shutdown when the connection is closed, i.e. a
\n# SSL close notify alert is sent and mod_ssl waits for the close notify
\n# alert of the client. This is 100% SSL\/TLS standard compliant, but in
\n# practice often causes hanging connections with brain-dead browsers. Use
\n# this only for browsers where you know that their SSL implementation
\n# works correctly.
\n# Notice: Most problems of broken clients are also related to the HTTP
\n# keep-alive facility, so you usually additionally want to disable
\n# keep-alive for those clients, too. Use variable “nokeepalive” for this.
\n# Similarly, one has to force some clients to use HTTP\/1.0 to workaround
\n# their broken HTTP\/1.1 implementation. Use variables “downgrade-1.0” and
\n# “force-response-1.0” for this.
\nBrowserMatch “MSIE [2-5]” \\
\nnokeepalive ssl-unclean-shutdown \\
\ndowngrade-1.0 force-response-1.0<\/p>\n
\n# The home of a custom SSL log file. Use this when you want a
\n# compact non-error SSL logfile on a virtual host basis.
\nCustomLog logs\/ssl_request_log \\
\n“%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \\”%r\\” %b”<\/p>\n
\nAH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using fe80::250:56ff:fea7:68e7%ens33. Set the ‘ServerName’ directive globally to suppress this message
\nSyntax OK<\/span><\/div>\n