Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

subdomain #11

Open
penguine opened this issue Jan 22, 2021 · 1 comment
Open

subdomain #11

penguine opened this issue Jan 22, 2021 · 1 comment

Comments

@penguine
Copy link

penguine commented Jan 22, 2021

Hi have had problems with the subdomain option.
My hostname: aa.bb.cc
my preferred subdomain yyy
so I would call the tunnel http://yyy.aa.bb.cc
actually in server.js the subdomain is yyy.aa so that the website is not accessible
I change in server.js:
// OLD if (options.subdomain) {
// subdomain = subdomain.replace(.${options.subdomain}, '');
debug("subdomain replaced: ", subdomain);
// }

to
if (options.subdomain) {
subdomain = options.subdomain;
debug("subdomain replaced: ", subdomain);
}

now I become the subdomain yyy and the website is accessible
is this a fix? or only a workaround for me?

@penguine penguine changed the title subdomaine subdomain Jan 22, 2021
tuanngocptn added a commit to tuanngocptn/socket-tunnel that referenced this issue Sep 23, 2023
@tuanngocptn
Copy link
Contributor

Hello @penguine

I just checked in source code and the problem in the regex check subdomain
you can check that problem in PR #14

Hope that can help you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants