If your program runs on the remote server, you should be able to access it via the server’s IP (e.g. http://192.168.0.1:8080) unless the server configuration blocks that port.
I managed to set up Apache2 to proxy to a golang app by doing the following:
Install the proxy and proxy_http modules (e.g. sudo a2enmod proxy on an Ubuntu server)
It is not doing exactly what is required but at least it is producing output. This is far better than what I had before which was a blank screen and no access or error logs.
It is rather later here and have had enough for one day. I hope to try again tomorrow.
I tied myself in knots with the Apache2 Reverse Proxy. I managed to get it to reverse proxy to localhost and to my other sites but do not understand how to use the facility
I installed Golang on the remote server and now the sites are calling a compiled Golang executable:
Delighted to say the http://tools.Pingdom.com/fpt speed tests are exceptional for a first attempt, about 50ms!!!
Google Analytics was taking nearly four times as long to load than the rest of the page so I have temporarily disabled until I can find why it is so slow.
I managed to solve the multiple Apache2 Reverse Prosy problem by using CaddyServer and they utilise the Free Automatic Https Protocol which was recently released late December 2015.
Golang is interesting but for me it is hard-work According to a blog, it takes about three-months before it starts to make sense and then it becomes productive.