Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 563
    • Issues 563
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 53
    • Merge requests 53
  • 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
  • Merge requests
  • !1604

nginx: Added ACME redirect to main domain based on alias domain fix

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Judah - MW requested to merge maximaweb/ispconfig3:4618-allow-acme-with-proxy-redirect into develop Apr 28, 2022
  • Overview 0
  • Commits 1
  • Pipelines 2
  • Changes 1

#4618 (closed) was closed when a fix was added for alias and sub domains, however main domains using a proxy redirect are still not able to generate or renew Lets Encrypt certificates because they don't have the necessary vhost location to allow the ACME challenge through to the correct directory.

This fix allows sites using redirect=proxy to still generate ACME certificates by not passing the acme requests through to the proxy.

Perhaps we should also consider using this for other features available such as stats, own error documents, SSI and custom directives. These features are still available in the interface yet have no effect on the vhost when redirect=proxy due to line 91: <tmpl_if name='use_proxy' op='!=' value='y'>. It is not very intuitive, and it would be best if either those features were disabled in the interface when redirect=proxy, or ideally, that they would be used when enabled.

Re-closes #4618 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 4618-allow-acme-with-proxy-redirect