Well that's a rate limit problem that only time can fix.
You may have to wait 4 more days to clear it.
Or try adding another name to the cert: xxx.sonicfiber.pk
But you will need DNS to resolve that name to your IP.
And add it as a ServerAlias in your conf file for the cert validation to complete.
who will clear the rate limit problem ??
you are saying that i can get the new ssl of my new sub domain ?
TIME.
- The limit is 5 same named certs per week (7 days)
- 20 certs per week for any domain.
So you fail #1 (for a few more days) but you could still pass #2 now
I'm saying add another name to the list of names and it will look like a new cert request.
And not fail #1.
You want two names but limit stop you - but if you get three names today no limit to stop you.
should i create a new virtual host in machine or should i give an other alias to this domain ( sonicfiber.pk) . ?
alias is much faster
it will work ?? i add one more alias in it. ??
ServerName www.sonicfiber.pk
ServerAlias sonicfiber.pk
ServerAlias sonicfiber
DocumentRoot /var/www/html
./certbot-auto --apache -d sonicfiber.pk -d www.sonicfiber.pk -d sonicfiber ( new command will be ?? )
It has to be a real name - an FQDN
that can be seen from the Internet.
And DNS must point that name to your IP
(directly or via CNAME)
Name: sonicfiber.pk
Address: 202.63.197.101
Aliases: www.sonicfiber.pk
Name: sonicfiber.pk
Address: 202.63.197.101
Name: test.sonicfiber.pk
*** UnKnown can’t find test.sonicfiber.pk: Non-existent domain
Name: sonicfiber
*** UnKnown can’t find sonicfiber: Server failed
ServerName www.sonicfiber.pk
ServerAlias sonicfiber.pk
ServerAlias www1.sonicfiber
add www1 and add Cname as well in m yDNS .
./certbot-auto --apache -d sonicfiber.pk -d www.sonicfiber.pk -d www1.sonicfiber.pk ???
yes try that combination
Created an SSL vhost at /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf Deploying Certificate to VirtualHost /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf Enabling site /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf by adding Include to root configuration Deploying Certificate to VirtualHost /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf We were unable to find a vhost with a ServerName or Address of www1.sonicfiber.pk. Which virtual host would you like to choose? (note: conf files with multiple vhosts are not yet supported) ------------------------------------------------------------------------------- 1: ssl.conf | | HTTPS | Enabled 2: sonicfiber.pk.conf | Multiple Names | | Enabled 3: sonicfiber.pk-le-ssl.conf | Multiple Names | HTTPS | Enabled ------------------------------------------------------------------------------- Select the appropriate number [1-3] then [enter] (press 'c' to cancel):
Can you guide ?? please
number 3 …
Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 3 Deploying Certificate to VirtualHost /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. ------------------------------------------------------------------------------- 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. ------------------------------------------------------------------------------- Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Redirecting vhost in /etc/httpd/sites-enabled/sonicfiber.pk.conf to ssl vhost in /etc/httpd/sites-available/sonicfiber.pk-le-ssl.conf ------------------------------------------------------------------------------- Congratulations! You have successfully enabled https://sonicfiber.pk, https://www.sonicfiber.pk, and https://www1.sonicfiber.pk You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=sonicfiber.pk https://www.ssllabs.com/ssltest/analyze.html?d=www.sonicfiber.pk https://www.ssllabs.com/ssltest/analyze.html?d=www1.sonicfiber.pk ------------------------------------------------------------------------------- IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/sonicfiber.pk/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/sonicfiber.pk/privkey.pem Your cert will expire on 2018-08-06. To obtain a new or tweaked version of this certificate in the future, simply run certbot-auto again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot-auto renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le
But still not working …
1: ssl.conf | | HTTPS | Enabled
That file is messing things up.
find / -name ssl.conf
[root@localhost /]# find / -name ssl.conf /usr/lib/python2.7/site-packages/certbot_apache/tests/testdata/centos7_apache/apache/httpd/conf.d/ssl.conf /usr/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/multiple_vhosts/apache2/mods-available/ssl.conf /usr/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/default_vhost/apache2/mods-available/ssl.conf /usr/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/augeas_vhosts/apache2/mods-available/ssl.conf /opt/eff.org/certbot/venv/lib/python2.7/site-packages/certbot_apache/tests/testdata/centos7_apache/apache/httpd/conf.d/ssl.conf /opt/eff.org/certbot/venv/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/multiple_vhosts/apache2/mods-available/ssl.conf /opt/eff.org/certbot/venv/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/default_vhost/apache2/mods-available/ssl.conf /opt/eff.org/certbot/venv/lib/python2.7/site-packages/certbot_apache/tests/testdata/debian_apache_2_4/augeas_vhosts/apache2/mods-available/ssl.conf /etc/httpd/conf.d/ssl.conf [root@localhost /]#
Show it here
more /etc/httpd/conf.d/ssl.conf
then put it away
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.original
or delete it:
rm /etc/httpd/conf.d/ssl.conf
then restart web apache
# When we also provide SSL we have to listen to the
# the 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
# 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 file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512
#
# 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
##
# 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
# SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect. Disable SSLv2 access by default:
SSLProtocol all -SSLv2
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5:!SEED:!IDEA
# Speed-optimized SSL Cipher configuration:
# If speed is your main concern (on busy HTTPS servers e.g.),
# you might want to force clients to specific, performance
# optimized ciphers. In this case, prepend those ciphers
# to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
# Caveat: by giving precedence to RC4-SHA and AES128-SHA
# (as in the example below), most connections will no longer
# have perfect forward secrecy - if the server's key is
# compromised, captures of past or future traffic must be
# considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on
# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/localhost.crt
##########SSLCertificateFile /etc/pki/tls/certs/certificate.crt
######SSLCertificateFile /etc/pki/tls/certs/sonicfiber.pk-crt-domain.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.)
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
########SSLCertificateKeyFile /etc/pki/tls/private/sonicfiber.pk-account.key
#############SSLCertificateKeyFile /etc/pki/tls/private/private.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/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
#############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.
#
#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]+$/
#
# 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
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
# 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
SSLOptions +StdEnvVars
# 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
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"
delete it then restart apache
webiste is not working 
i move the ssl file in /tmp/
Show this file:......
[root@localhost sites-available]# cat sonicfiber.pk-le-ssl.conf
<VirtualHost *:443>
ServerName www.sonicfiber.pk
ServerAlias sonicfiber.pk
ServerAlias www1.sonicfiber
DocumentRoot /var/www/html
ErrorLog /var/log/httpd/error.log
CustomLog /var/log/httpd/requests.log combined
Include /etc/letsencrypt/options-ssl-apache.conf
ServerAlias www1.sonicfiber.pk
SSLCertificateFile /etc/letsencrypt/live/sonicfiber.pk/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sonicfiber.pk/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/sonicfiber.pk/chain.pem
[root@localhost sites-available]#