Skip to content

SSl expired on virtualmin

Solved Configure
  • @phenomlab

    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator manual, Installer None
    Renewing an existing certificate
    An unexpected error occurred:
    There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
    Please see the logfiles in /var/log/letsencrypt for more details.

    so i need to wait hour? month? 🐶

  • @justoverclock Yep, that’s the rate-limit message. Try again in an hour.

  • @phenomlab after one hour or more:

    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator manual, Installer None
    Renewing an existing certificate
    Performing the following challenges:
    dns-01 challenge for justoverclock.it
    dns-01 challenge for justoverclock.it
    Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
    Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
    Waiting for verification...
    Challenge failed for domain justoverclock.it
    Challenge failed for domain justoverclock.it
    dns-01 challenge for justoverclock.it
    dns-01 challenge for justoverclock.it
    Cleaning up challenges
    Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
    Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
    Some challenges have failed.
    IMPORTANT NOTES:
     - The following errors were reported by the server:
    
       Domain: justoverclock.it
       Type:   dns
       Detail: DNS problem: NXDOMAIN looking up TXT for
       _acme-challenge.justoverclock.it - check that a DNS record exists
       for this domain
    
       Domain: justoverclock.it
       Type:   dns
       Detail: DNS problem: NXDOMAIN looking up TXT for
       _acme-challenge.justoverclock.it - check that a DNS record exists
       for this domain
    
  • @justoverclock Seems your _acme-challenge DNS record is missing ?

    f0b3710d-40fa-4480-a520-1abc88385f2d-image.png

  • @phenomlab didn’t touch anything from your last visit 👀

  • @justoverclock Very odd. Let me have a look at another way

  • @justoverclock I have installed the --nginx version of certbot on your server as per
    https://sudonix.com/post/689

    It’s showing that the renewal will work, but the rate-limit is currently still enforced, so we still need to wait.

    Performing the following challenges:
    http-01 challenge for justoverclock.it
    http-01 challenge for www.justoverclock.it
    Waiting for verification...
    Cleaning up challenges
    
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    new certificate deployed with reload of nginx server; fullchain is
    /etc/letsencrypt/live/justoverclock.it/fullchain.pem
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ** DRY RUN: simulating 'certbot renew' close to cert expiry
    **          (The test certificates below have not been saved.)
    
    Congratulations, all renewals succeeded. The following certs have been renewed:
      /etc/letsencrypt/live/admin.justoverclock.it/fullchain.pem (success)
      /etc/letsencrypt/live/forum.justoverclock.it/fullchain.pem (success)
      /etc/letsencrypt/live/justoverclock.it/fullchain.pem (success)
    ** DRY RUN: simulating 'certbot renew' close to cert expiry
    **          (The test certificates above have not been saved.)
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    
    IMPORTANT NOTES:
     - Your account credentials have been saved in your Certbot
       configuration directory at /etc/letsencrypt. You should make a
       secure backup of this folder now. This configuration directory will
       also contain certificates and private keys obtained by Certbot so
       making regular backups of this folder is ideal.
    root@justoverclock:/home/justoverclock#
    
  • @justoverclock should be resolved now

    fdf08e7a-6c62-429b-815c-a01844528dd6-image.png

    1f1f523e-a0e8-4e29-8e3c-23e26589e5cd-image.png

    As a side note, this renewal won’t show in Virtualmin unless it is requested from there. This is done from the command line, so

    1. SSH into the server
    2. Change to root
    3. Execute certbot --nginx and follow the prompts
  • phenomlabundefined phenomlab has marked this topic as solved on
  • @phenomlab so this is the command that i need to use everytime my certificate expire? thank you, precious as always

  • @justoverclock Not necessarily. You only need to use this if it fails from the Virtualmin window


Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

  • 3 Votes
    30 Posts
    410 Views

    @DownPW any update?

  • 2 Votes
    4 Posts
    192 Views

    @Hari Ok, no issues. Keep me posted…

  • 0 Votes
    17 Posts
    399 Views

    @DownPW anytime

  • 0 Votes
    4 Posts
    366 Views

    @DownPW 🙂 most of this really depends on your desired security model. In all cases with firewalls, less is always more, although it’s never as clear cut as that, and there are always bespoke ports you’ll need to open periodically.

    Heztner’s DDoS protection is superior, and I know they have invested a lot of time, effort, and money into making it extremely effective. However, if you consider that the largest ever DDoS attack hit Cloudflare at 71m rps (and they were able to deflect it), and each attack can last anywhere between 8-24 hours which really depends on how determined the attacker(s) is/are, you can never be fully prepared - nor can you trace it’s true origin.

    DDoS attacks by their nature (Distributed Denial of Service) are conducted by large numbers of devices whom have become part of a “bot army” - and in most cases, the owners of these devices are blissfully unaware that they have been attacked and are under command and control from a nefarious resource. Given that the attacks originate from multiple sources, this allows the real attacker to observe from a distance whilst concealing their own identity and origin in the process.

    If you consider the desired effect of DDoS, it is not an attempt to access ports that are typically closed, but to flood (and eventually overwhelm) the target (such as a website) with millions of requests per second in an attempt to force it offline. Victims of DDoS attacks are often financial services for example, with either extortion or financial gain being the primary objective - in other words, pay for the originator to stop the attack.

    It’s even possible to get DDoS as a service these days - with a credit card, a few clicks of a mouse and a target IP, you can have your own proxy campaign running in minutes which typically involves “booters” or “stressers” - see below for more

    https://heimdalsecurity.com/blog/ddos-as-a-service-attacks-what-are-they-and-how-do-they-work

    @DownPW said in Setting for high load and prevent DDoS (sysctl, iptables, crowdsec or other):

    in short if you have any advice to give to secure the best.

    It’s not just about DDos or firewalls. There are a number of vulnerabilities on all systems that if not patched, will expose that same system to exploit. One of my favourite online testers which does a lot more than most basic ones is below

    https://www.immuniweb.com/websec/

    I’d start with the findings reported here and use that to branch outwards.

  • SSL certificates

    Solved Configure
    4
    2 Votes
    4 Posts
    160 Views

    @Panda Go for shared - don’t look at dedicated 😄

  • 4 Votes
    10 Posts
    593 Views

    @phenomlab thanks for sharing, after four or five months I will migrate to DO 2 or 4gb RAM droplet. 👍

  • 1 Votes
    2 Posts
    337 Views

    @Hari this helped

  • VirtualMin create virtual server

    Solved Configure
    4
    2 Votes
    4 Posts
    293 Views

    @justoverclock correct. You only need to keep an eye on the resources of the droplet itself