Wildcard Domains (not SSL)

Great project, thanks for all your time on this.

This feature may already exist, and I just can’t find any documentation for it. I’m happy to create a PR with docs if you can point me in the right direction.

Basically, everything is working perfectly with my new installation. However, I have to put each subdomain in manually. I would like to specify a wildcard domain, and have every subdomain map to a host.

Just to note, this isn’t to do with HTTPS or LetsEncrypt.

Is your feature request related to a problem? Please describe. I would like to be able to map *.mydomain.com to the same IP address.

Describe the solution you’d like The screen below to accept a wildcard domain

Describe alternatives you’ve considered Putting in each domain manually

Additional context Add any other context or screenshots about the feature request here.

Use Case Maybe a use case would help. Imagine I’m hosting GitLab (or a hypothetical GitHub) on my network with pages (GitHub Pages or GitLab Pages).

I want to let my users expose THEIRORG.pages.gitlab.test .

In my mind, the way to do this is have a wildcard entry: *.pages.gitlab.test

So then if the user comes through to http://testorg.pages.gitlab.test/testrepo, the request automaitcally get’s forwarded to the one server.

[chaptergy]

It seems the only issue was the regex pattern. The fix was added in v2.9.5, so from there and up this works. I have tested it on v2.9.6 and both first-level and second-level wildcards for proxy hosts work as expected.

[mantasio]

This would be a really useful feature. Especially if you are working in development with CI/CD and want to have different environments for, let’s say, each git branch. Right now, you would need to add a new entry in NPM each time after deployment is done, which isn’t very handy