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

allow custom ports for webserver and le #111

Merged
merged 1 commit into from
Jul 24, 2021
Merged

allow custom ports for webserver and le #111

merged 1 commit into from
Jul 24, 2021

Conversation

tsmethurst
Copy link
Contributor

This PR allows custom ports to be selected for both the GTS webserver/API, and the letsencrypt certificate challenge.

For LE:

# Config pertaining to the automatic acquisition and use of LetsEncrypt HTTPS certificates.
letsEncrypt:

[...]

  # Int. Port to listen for letsencrypt certificate challenges on.
  # If letsencrypt is enabled, this port must be reachable or you won't be able to obtain certs.
  # If letsencrypt is disabled, this port will not be used.
  # This *must not* be the same as the webserver/API port specified above.
  # Examples: [80, 8000, 1312]
  # Default: 80
  port: 80

And for the webserver/api port:

# Int. Listen port for the GoToSocial webserver + API. If you're running behind a reverse proxy and/or in a docker,
# container, just set this to whatever you like (or leave the default), and make sure it's forwarded properly.
# If you are running with built-in letsencrypt enabled, and running GoToSocial directly on a host machine, you will
# probably want to set this to 443 (standard https port), unless you have other services already using that port.
# This *MUST NOT* be the same as the letsencrypt port specified below, unless letsencrypt is turned off.
# Examples: [443, 6666, 8080]
# Default: 8080
port: 8080

These values can also be set by the cli flags --port and --letsencrypt-port or by env vars GTS_PORT and GTS_LETSENCRYPT_PORT

Closes #43

@tsmethurst tsmethurst merged commit bc1d8a9 into main Jul 24, 2021
@tsmethurst tsmethurst deleted the custom_ports branch July 24, 2021 17:02
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

Successfully merging this pull request may close these issues.

Can't listen webserver on custom port
1 participant