Update README.md

ISSUE_TEMPLATE.md

@@ -1,12 +1,12 @@
 #### Expected Behavior
 
-(what you expect to happen goes here)
+<!-- what you expect to happen goes here -->
 
 -----
 
 #### Actual Behavior
 
-(what actually happens goes here)
+<!-- what actually happens goes here -->
 
 -----
 
@@ -30,5 +30,5 @@
 - Include what you've done so far in the installation, and if you got any error messages along the way.
 - Indicate whether or not you've manually edited any data directly.
 
-Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
+<!-- Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you. -->
 

README.md

@@ -16,6 +16,12 @@ If you don't want NFS capabilities run ```sudo apt-get remove nfs-common```.
 * Do not use LAMP
 * SSH Access is optional, but highly recommended
 
+## SSL and Reverse Proxies
+
+Please understand you are required to use a RP to setup SSL on XO (and XOCE). Some documentation on the process. https://xen-orchestra.com/docs/reverse_proxy.html
+
+The YAML file required can be found at ```/opt/xen-orchestra/packages/xo-server/.xo-server.yaml```
+
 # Goals/Backstory for this script
 
 I'm often asked "why can't this be run on CentOS or Fedora" to which my only reply is and has ever been: The goal was to be the XCP-ng of XS. Which means I wanted a solution that offered as much as XOA offers, while using what is available freely and from open sources. Without restrictions.