ssh -R 9000:localhost:4200 my.server.is.awesome.com
Boom, your local server is reachable on my.server.is.awesome.com:9000
It's actually quite a useful trick that I use when needing to test integration with 3rd parties when on the dev branch of our API code.
If you like these kind of tricks. I'd really advice watching this talk. https://vimeo.com/54505525
But if you are tunneling an HTTP service, you can be assigned a random hostname (random.ngrok.com), or you can request a specific hostname (pkaeding-test.ngrok.com), and your service will be available over both HTTP (port 80) and HTTPS (port 443) on that hostname. This can be critical for testing webhook callbacks where the remote service only allows HTTPS on port 443.
Also, when you are tunneling HTTP services (using HTTP or HTTPS), ngrok will start a web UI running at localhost:3030, detailing all incoming requests. You can examine the headers and body from both request and response, and even replay requests. This is immensely helpful when debugging webhooks.
(I am not affiliated with ngrok, except as a happy user.)
So I expose :9000 on the remote host, and then map :9000 to blah.my.website.com:443 using ngnix