This was actually very difficult to setup. A lot of trial and error to make it work. Basically I wanted to be able to access the SharkRF Dashboard from the internet but I did not want the connection to go directly to the SharkRF server for security reasons (as in an exploit breaching my SharkRF Connector Server).

What I did was use my web server that already serves my websites to act as a reverse proxy to display my SharkRF Connector Dashboard. In other words, when somebody accesses my SharkRF Dashboard, they are actually accessing my web server which is then accessing my SharkRF Dashboard.

On top of that, I wanted all of this protected and behind Cloudflare ( https://www.cloudflare.com ). With this, my SharkRF Dashboard is now served up with TLS (https) and my actual server IP address is not publicly exposed because all connections are going through Cloudflare.

I don't necessarily have a guide, per say, but my thoughts and steps can be found here: https://www.johndball.com/sharkrf-connector-server-behind-apache-proxy-behind-cloudflare/
The SSL protection of my RF Dashboard can be seen here: https://www.ssllabs.com/ssltest/analyze.html?d=rf01vdash.johndball.com&s=104.24.112.153&hideResults=on&latest

Finally, the working SharkRF Connector Dashboard proof of concept can be accessed here: https://rf01vdash.johndball.com/

Happy geeking.