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💗

  • 0 Votes
    17 Posts
    366 Views

    @DownPW anytime

  • SSL certificates

    Solved Configure
    4
    2 Votes
    4 Posts
    150 Views

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

  • 9 Votes
    26 Posts
    2k Views

    @Hari said in Virtualmin Setup DigitalOcean:

    i have felt it is very hard to manage Virtualmin the settings are confusing

    It’s a bit of a learning curve, admittedly, but very powerful and easy to use provided you understand the implications of what you are doing. For example, moving a VirtualMin server to subserver and then back again without changing underlying components that rely on the correct placement of the server, of course it will no longer work.

  • 3 Votes
    10 Posts
    721 Views

    @Hari DDoS protection is not just a switch, or one component. It’s a collection of different and often disparate technologies that when grouped together form the basis of a combined toolset that can be used in defence.

    Typically these consist of IDS (Instrusion Detection System) and IPS (Intrusion Prevention System) components that detect irregularities in network traffic, and will take decisive action based on predefined rulesets, or in the case of more modern systems, AI and ML.

    Traditional “traffic shaping” technology is also deployed, so if an attack cannot be easily identified as malicious, the bandwidth available to that connection is severely limited to nothing more than a trickle rather than a full flow.

    Years ago, ISP’s used traffic shaping (also called “policers”) as an effective means of stopping applications such as BearShare, eDonkey, Napster, and other P2P based sharing systems from functioning correctly - essentially reducing the “appeal” of distributing and seeding illegal downloads. This was essentially the ISP’s way of saying “stop what you are doing please” without actually pulling the plug.

    These days, DDoS attacks are designed to overwhelm - not assume control of - webservers and other public facing components. It’s rare for small entities to be attacked unless there is some form of political agenda driven by your site or product. A classic example is governmental institutions or lawmakers who effectively are classed as “enforcers” and those who disagree are effectively making a statement in the form of Denial of Service.

    DDoS protection is effectively the responsibility of the hosting provider, but you shouldn’t just assume that they will protect you or your site. Their responsibility stops at their infrastructure, so it’s then up to you too decide how you full the gap in between your host and the website.

    Typically, you’d leverage something like Imunify360 which you can get for Plesk (and something I’d strongly recommend) but it’s not free, and is a paid (not expensive per month) subscription. If you want to use VirtualMin then there are a variety of tools readily available out of the box such as firewalls and fail2ban.

  • 14 Votes
    65 Posts
    5k Views

    @crazycells huh. Thanks. Will need to check that as well.

  • 1 Votes
    2 Posts
    330 Views

    @Hari this helped

  • nginx can't start again

    Moved Solved Configure
    20
    2 Votes
    20 Posts
    898 Views

    @elhana-fine Yes that will happen of of course if you still choose to restart the NGINX service after making a change and the test fails. The test on it’s own will state the error and the line number allowing you to fix that first 🙂

  • 0 Votes
    5 Posts
    767 Views

    @Ash3T I’m going to mark this post as solved as I’ve not heard from you in a while. Let me know if this isn’t the case and you need more help.