Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 551
    • Issues 551
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 41
    • Merge requests 41
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #3929

Closed
Open
Created May 25, 2016 by AndyPL@andrzejs

ISPC 3.1 b1 letsencrypt bug

Please change configuration letsencrypt because when we create hosting with support letsencrypt get information.

urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://domain.ltd/.well-known/acme-challenge/Sk1C7t4Xvj9absx1uCmI7hfSIw1ebZHFjYhQ6pL6Wqc:

Letsencrypt works correctly if you create the first web hosting and later add support letsencrypt.

Assignee
Assign to
Time tracking