The result above shows the connection hash for your hyper port.
This will be the hash used as your subdomain later in this process.
NOTE: The "hellothere" above is the connection "topic" this is used to generate the hash and it can be any string or key phrase you wish.
# The Reverse proxy
We will proxy all of the traffic to their specific peers using a reverse proxy method, in this example, we will utilize httpd/apache below you will find the standard configuration that will work for our purposes.
```
<VirtualHost*:443>
SSLProxyEngine On
ServerAlias *.your-tld.here
ServerAdmin webmaster@your-tld.here
DocumentRoot /var/www/html
ErrorLog /var/log/error.log
CustomLog /var/log/access.log combined
SSLCertificateFile /path/to/fullchain.pem
SSLCertificateKeyFile /path/to/privkey.pem
# Reverse Proxy for subdomains
<Proxy*>
Require all granted
</Proxy>
ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto https
ProxyPass "/" "http://localhost:8081/"
ProxyPassReverse "/" "http://localhost:8081/"
</VirtualHost>
```
NOTE 1: This requires `mod_proxy` and `mod_ssl` to work properly.
NOTE 2: This requires the full use of the wildcard *.your-told.here you will not be able to use any subdomain within this scope unless it runs via a hyper-relay.
We highly reccomend using SSL only for this reverse connection, however, you may configure your proxy pass as desired.
# Wildcard DNS Entry
In order to serve your subdomain hashes without the need to generate an A record create a wildcard subdomain record.
Example:
`*.example.com. IN A 192.0.2.1`
This system does work well with cloudflare proxy, feel free to proxy your traffic!