Skip to content

Conversation

Jarli01
Copy link

@Jarli01 Jarli01 commented Jul 25, 2025

Outlines the steps required to close port 80 on a per host basis if the pool wide option doesn't address the issue.

Before submitting the pull request, you must agree with the following statements by checking both boxes with a 'x'.

  • [ x ] "I accept that my contribution is placed under the CC BY-SA 2.0 license [1]."
  • [ x] "My contribution complies with the Developer Certificate of Origin [2]."

[1] https://creativecommons.org/licenses/by-sa/2.0/
[2] https://docs.xcp-ng.org/project/contributing/#developer-certificate-of-origin-dco

Outlines the steps required to close port 80 on a per host basis if the pool wide option doesn't address the issue. 

Signed-off-by: Dustin B <[email protected]>
@stormi stormi requested review from psafont and stormi July 30, 2025 14:59
xe pool-param-set uuid=<pool-uuid> https-only=true
```

If the pool wide settings don't close port 80, you may need to run the below command on each host to restrict the use of HTTP
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand "If the pool wide settings don't close port 80". It sounds like it's random, it may or may not work. Do we have more information about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants