Originally created by @KamilKleina on GitHub (Mar 3, 2025).
Pangolin does not function when a subdomain is set as the base domain. I do not want to use domain.com as the base because it is already in use across multiple different servers. Instead, I need to set host-01.remote-location-01.domain.com as the base domain and have services like pangolin.host-01.remote-location-01.domain.com work normally.
Expected Behavior
Pangolin should support subdomains as base domains.
Certificates should issue and validate correctly.
Routing should function as expected for services under the subdomain base.
Actual Behavior
Pangolin fails entirely when using a subdomain as the base.
Steps to Reproduce
Set the base domain to host-01.remote-location-01.domain.com.
Originally created by @KamilKleina on GitHub (Mar 3, 2025).
Pangolin does not function when a subdomain is set as the base domain. I do not want to use domain.com as the base because it is already in use across multiple different servers. Instead, I need to set host-01.remote-location-01.domain.com as the base domain and have services like pangolin.host-01.remote-location-01.domain.com work normally.
Expected Behavior
Pangolin should support subdomains as base domains.
Certificates should issue and validate correctly.
Routing should function as expected for services under the subdomain base.
Actual Behavior
Pangolin fails entirely when using a subdomain as the base.
Steps to Reproduce
Set the base domain to host-01.remote-location-01.domain.com.
Hey, this should work; we use a subdomain as as a base domain internally, and I think some of our users in Discord do as well. However, it's possible it's still buggy. Can you provide some more info as to what happens when you attempt this and why it's failing? Are there are errors or anything in the logs that could provide us a hint?
@miloschwartz commented on GitHub (Mar 3, 2025):
Hey, this should work; we use a subdomain as as a base domain internally, and I think some of our users in Discord do as well. However, it's possible it's still buggy. Can you provide some more info as to what happens when you attempt this and why it's failing? Are there are errors or anything in the logs that could provide us a hint?
I think this is a parsing issue in the config. I think it's also an easy fix that I will try to include in the next release for you. Hope to have that out tomorrow.
@miloschwartz commented on GitHub (Mar 3, 2025):
Okay, thanks. This helps narrow down the issue.
I think this is a parsing issue in the config. I think it's also an easy fix that I will try to include in the next release for you. Hope to have that out tomorrow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @KamilKleina on GitHub (Mar 3, 2025).
Pangolin does not function when a subdomain is set as the base domain. I do not want to use domain.com as the base because it is already in use across multiple different servers. Instead, I need to set host-01.remote-location-01.domain.com as the base domain and have services like pangolin.host-01.remote-location-01.domain.com work normally.
Expected Behavior
Actual Behavior
Steps to Reproduce
@miloschwartz commented on GitHub (Mar 3, 2025):
Hey, this should work; we use a subdomain as as a base domain internally, and I think some of our users in Discord do as well. However, it's possible it's still buggy. Can you provide some more info as to what happens when you attempt this and why it's failing? Are there are errors or anything in the logs that could provide us a hint?
@KamilKleina commented on GitHub (Mar 3, 2025):
@miloschwartz
so my config looks like it after running installer.sh (removed section about user and smtp)
and error is like that after running
docker logs pangolin@miloschwartz commented on GitHub (Mar 3, 2025):
Okay, thanks. This helps narrow down the issue.
I think this is a parsing issue in the config. I think it's also an easy fix that I will try to include in the next release for you. Hope to have that out tomorrow.
@KamilKleina commented on GitHub (Mar 3, 2025):
That would be really awesome sir.