[GH-ISSUE #89] Just needing to understand something #47

New issue

Open

opened 2026-05-05 10:58:36 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 10:58:36 -06:00

Owner

Originally created by @bmcgonag on GitHub (Mar 8, 2019).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/89

for host entry, if i use mytestroute.routetome.org does the whole thing have to be setup with DNS to point to my server? Or should I just be able to point routetome.org to my server, and then when I use the address https://mytestroute.routetome.org it will know where to send that particular subdomain request based on the host entry in my client .yml file?

This looks like a cool project, but having issues getting it to route right now. I have routetome.org setup with DNS pointing to my DO server, but not the sub-domain.

Was hoping this was a bit more like ngrok as far as subdomains on the fly. If any of you folks know how to get that setup using this project it would be totally great. More than happy to donate to an open source project like this as well.

Originally created by @bmcgonag on GitHub (Mar 8, 2019). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/89 for `host` entry, if i use mytestroute.routetome.org does the whole thing have to be setup with DNS to point to my server? Or should I just be able to point routetome.org to my server, and then when I use the address https://mytestroute.routetome.org it will know where to send that particular subdomain request based on the host entry in my client .yml file? This looks like a cool project, but having issues getting it to route right now. I have routetome.org setup with DNS pointing to my DO server, but not the sub-domain. Was hoping this was a bit more like ngrok as far as subdomains on the fly. If any of you folks know how to get that setup using this project it would be totally great. More than happy to donate to an open source project like this as well.

gitea-mirror commented

2026-05-05 10:58:39 -06:00

Author

Owner

@bmcgonag commented on GitHub (Mar 8, 2019):

I'm a knot-head and I apologize. I had to setup the * DNS A record to point to my server IP, and now it works just as I wanted. Thank you. Getting ready to donate. This is great!

@bmcgonag commented on GitHub (Mar 8, 2019): I'm a knot-head and I apologize. I had to setup the * DNS A record to point to my server IP, and now it works just as I wanted. Thank you. Getting ready to donate. This is great!

gitea-mirror commented

2026-05-05 10:58:40 -06:00

Author

Owner

@fusion44 commented on GitHub (Mar 24, 2019):

@bmcgonag Have you got this working for a subdomain? In my example I would like to use tunnel.mydomain.com for the server, so my subdomains would look like webui.tunnel.mydomain.com?

@fusion44 commented on GitHub (Mar 24, 2019): @bmcgonag Have you got this working for a subdomain? In my example I would like to use tunnel.mydomain.com for the server, so my subdomains would look like webui.tunnel.mydomain.com?

gitea-mirror commented

2026-05-05 10:58:42 -06:00

Author

Owner

@bmcgonag commented on GitHub (Mar 24, 2019):

@fusion44 I did. I think you would just register mydomain.com, then setup your A record for either *.tunnel.mydomain.com or *.mydomain.com . If the latter, then in the client yml file you will set the sub domain info as myplace.tunnel.mydomain.com and it will be registered with the server. Then you can change the subdomain to anything you want for each client.

@bmcgonag commented on GitHub (Mar 24, 2019): @fusion44 I did. I think you would just register mydomain.com, then setup your A record for either *.tunnel.mydomain.com or *.mydomain.com . If the latter, then in the client yml file you will set the sub domain info as myplace.tunnel.mydomain.com and it will be registered with the server. Then you can change the subdomain to anything you want for each client.

gitea-mirror commented

2026-05-05 10:58:44 -06:00

Author

Owner

@fusion44 commented on GitHub (Mar 29, 2019):

@bmcgonag Awesome, thanks!

@fusion44 commented on GitHub (Mar 29, 2019): @bmcgonag Awesome, thanks!