Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 495
    • Issues 495
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 28
    • Merge Requests 28
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4299

Closed
Open
Opened Oct 23, 2016 by Till Brehm@tbrehmOwner

SSL certificate key mismatch problem

The problem occurs when a custom ssl ert has been used before in a website, when you activate letsencrypt then and letsencrypt fails to validate a cert, then the key from letsencrypt is used with the old custom ssl cert which causes apache to fail to start.

Assignee
Assign to
3.1.1
Milestone
3.1.1
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4299