[GH-ISSUE #1] tunnelto.dev subdomains not working #1

New issue

Closed

opened 2026-03-02 23:01:34 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 23:01:34 +03:00

Owner

Originally created by @stealthybox on GitHub (Apr 22, 2020).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/1

Hi, cool project!
I was playing with it and instantly noticed the subdomain flag.

Are subdomains supposed to work on the public instance?
Do I need to configure an API key for that to work?

I expected this command to give me back a public URL similar to stealthybox.tunnelto.dev or stealthybox-aexsh3w5.tuneelto.dev, but instead, the -s option seems ignored.

wormhole start -s stealthybox -p 31888
Welcome to wormhole!

<trunctated>

Wormhole activated on: https://aexsh3w5.tunnelto.dev

Did I misunderstand that this is supposed to only be an overriden host-header that's passed into the proxied request?

If not and I'm understanding this feature correctly, we can probably implement an error or warning message and include some docs around API keys or the capabilities of private instances.

Originally created by @stealthybox on GitHub (Apr 22, 2020). Original GitHub issue: https://github.com/agrinman/tunnelto/issues/1 Hi, cool project! I was playing with it and instantly noticed the subdomain flag. Are subdomains supposed to work on the public instance? Do I need to configure an API key for that to work? I expected this command to give me back a public URL similar to `stealthybox.tunnelto.dev` or `stealthybox-aexsh3w5.tuneelto.dev`, but instead, the `-s` option seems ignored. ``` wormhole start -s stealthybox -p 31888 Welcome to wormhole! <trunctated> Wormhole activated on: https://aexsh3w5.tunnelto.dev ``` Did I misunderstand that this is supposed to only be an overriden host-header that's passed into the proxied request? If not and I'm understanding this feature correctly, we can probably implement an error or warning message and include some docs around API keys or the capabilities of private instances.

kerem closed this issue

2026-03-02 23:01:35 +03:00

kerem commented

2026-03-02 23:01:38 +03:00

Author

Owner

@agrinman commented on GitHub (Apr 22, 2020):

Hi @stealthybox, this is currently by design (though you're right that a helpful error message is needed). For the publicly hosted version, we're currently only allowing random subdomains. If you deploy it yourself, this is controlled by enabling a secret key as noted in the readme.

I like the idea of adding random characters to a specified subdomain though -- we can definitely support that in the publicly hosted deployment!

@agrinman commented on GitHub (Apr 22, 2020): Hi @stealthybox, this is currently by design (though you're right that a helpful error message is needed). For the publicly hosted version, we're currently only allowing random subdomains. If you deploy it yourself, this is controlled by enabling a secret key as noted in the readme. I like the idea of adding random characters to a specified subdomain though -- we can definitely support that in the publicly hosted deployment!

kerem commented

2026-03-02 23:01:38 +03:00

Author

Owner

@agrinman commented on GitHub (Apr 25, 2020):

Fixed in github.com/agrinman/wormhole@eb4fb89d5c

@agrinman commented on GitHub (Apr 25, 2020): Fixed in https://github.com/agrinman/wormhole/commit/eb4fb89d5c70d1d29895af84a31bbaa0b9662e5f

kerem commented

2026-03-02 23:01:38 +03:00

Author

Owner

@stealthybox commented on GitHub (May 19, 2020):

nice! thanks!

@stealthybox commented on GitHub (May 19, 2020): nice! thanks!

kerem referenced this issue

2026-03-13 19:47:52 +03:00

[GH-ISSUE #1] tunnelto.dev subdomains not working #93