{RESOLVED} ISPConfig 3.3.1p1 on debian

Discussion in 'General' started by jimdaus, Mar 24, 2026.

  1. jimdaus

    jimdaus New Member

    Hi all,
    I have been using ISPConfig for many years now with very little problems, but this one has me scratching my head.
    1. It started when i added a new website to my server (lets call it jet). jet was hosted on another platform and i was paying too much to keep only that site operational on that server, so i moved it to my ispconfig site and no issues with getting it operating on http, but turning HTTPS on, was an issue.
    2. i tried the usual googling and found this "" which suggested NOT to manually do anything with certbot (which actually doesn't exist on my server ???) and i cannot locate the certbot logs in /var/ so that was confusing me.
    3. next i tried removing an alias for jet and a few other edits (cannot remmember specifics as it was late). now i have the following waiting for update and am unsure how to push this through or revert the changes.
      The following changes are not yet populated to all servers:
      Update main config: 2
      Delete website: 1
      Update website settings: 3

    4. i have 2 websites (of about 8) now showing 503 errors ... jet and another mates site.
    questions are:
    1. where are certbot logs or how do i enable them?
    2. what do i need to monitor to get the errors for the apache2 server not loading the new config?

    As a side note, this forum has been unavailable from AUSTRALIA for the past few days (maybe a week ?). i needed to VPN to the US to view it. i get a cloudflare errorcode 520.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    See:

    https://forum.howtoforge.com/threads/lets-encrypt-error-faq.74179/

    Which is normal as ISPConfig does not use Certbot on recent installations; it uses acme.sh today.

    See:

    https://forum.howtoforge.com/threads/please-read-before-posting.58408/
     
  3. jimdaus

    jimdaus New Member

    thanks till, i guess more googling was required ... its fixed now.
     
    till likes this.

Share This Page