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 482
    • Issues 482
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #5048

Closed
Open
Opened May 23, 2018 by umaxx@umaxx

letsencrypt symlinks are not updated after renewal

short description

SSL/Letsencrypt enabled site does not update symlinks after letsencrypt renewal. Certifcate got renewed 30 days before expiration as expected, but ispconfig site symlinks in ssl/ folder still point to the previous certificate, e.g. chain1.pem instead of the new chain2.pem. Like this:

# ls -l /var/www/www.example.com/ssl/
total 24
lrwxrwxrwx 1 root root   73 May 23 11:10 www.example.com-le.bundle -> ../../../../../../etc/letsencrypt/archive/www.example.com/chain1.pem

[...] Also note the usage of archive/ instead of live/ folder above The following link: https://www.howtoforge.com/community/threads/lets-encrypt-certificates-not-auto-renewed-symlink-archive-vs-live.75338/ suggests that live/ should be used here instead?!

correct behaviour

Symlinks should be updated to point to the new cert files, e.g. chain2.pem ...or probably use live/ folder instead?

environment

Server OS: centos Server OS version: centos7.5 ISPConfig version: 3.1.11 (with nginx)

workaround

[ ] disable and [x] re-enable letsenrcrypt for site to get symlink updated to point to the new cert, though still in archive/ folder.

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