diff --git a/docs/releases/release-8-3.md b/docs/releases/release-8-3.md
index c1953b30..7a002d11 100644
--- a/docs/releases/release-8-3.md
+++ b/docs/releases/release-8-3.md
@@ -231,6 +231,11 @@ To close port 80, run the following command:
 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
+```
+xe host-param-set https-only=true uuid=<uuid of the host>
+```
+
 ### Improvements in the installer
 
 Two years ago, development around XenServer's (and XCP-ng's) installer [was opened](https://github.com/xenserver/host-installer), allowing us to introduce several improvements and fixes (while previously we could modify the installer, contributing upstream reduces the long-term maintenance burden of divergence between our version and theirs).
@@ -518,4 +523,4 @@ Live migrating a VM from an older XenServer version can sometimes result in erro
 * The VM may reboot.
 * The VM may get duplicated, meaning the same VM UUID (and usually its VDIs too) will appear both on the sender and receiver host. In such a case, you'll need to remove the duplicate from the receiver host.
 
-It would require a hotfix to the old XenServer, but since those versions are no longer supported, XenServer won't be developing one. If you need to migrate from such old host, you should rely on [Xen Orchestra warm migration feature](https://xen-orchestra.com/blog/warm-migration-with-xen-orchestra/).
\ No newline at end of file
+It would require a hotfix to the old XenServer, but since those versions are no longer supported, XenServer won't be developing one. If you need to migrate from such old host, you should rely on [Xen Orchestra warm migration feature](https://xen-orchestra.com/blog/warm-migration-with-xen-orchestra/).