-
-
Notifications
You must be signed in to change notification settings - Fork 707
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
Allow listening on multiple HTTPS_PORTs #3619
Labels
Comments
ocdtrekkie
added
install-config
Installation/configuration issues
enhancement
Feature requests
labels
May 19, 2022
Also I would probably offer up like a $100 bounty or something for this one, because it would wildly improve my day-to-day Sandstorm world, personally. |
I'd still like this someday to fix links surely spread randomly across the web, but I did decide to just rip the bandaid off and switch ports for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So the first port vs. alternate port behavior for HTTP_PORT is documented here: https://docs.sandstorm.io/en/latest/administering/config-file/ and HTTP_PORT can be specified as a comma-separated list. However, HTTPS_PORT is specified as a single port, and specifies that the HTTPS_PORT will be treated as the first port if enabled. However, there is no support for HTTPS alternate ports.
The problem is that since Oasis shut down, I have operated my Sandcats server on a nonstandard port (6080, but using HTTPS), because my ISP had an explicit terms of use prohibiting exposing any server software on a well-known port (such as 443). However, that ISP recently sold my geographic area to another ISP with different terms which do not prohibit using well-known ports. Moving my server would solve a lot of problems, like letting me host websites cached via Cloudflare (and other external services which expect normal ports for things). However, that would break all of my existing HTTPS sharing links and API keys out in the world, which would be very sad and frustrating.
The text was updated successfully, but these errors were encountered: