stoatchat/self-hosted
1
0
Fork 0
mirror of https://github.com/stoatchat/self-hosted.git synced 2026-07-21 04:25:24 -04:00
Code Issues 42 Packages Projects Releases Wiki Activity

Need help deploying behing proxy #10

New Issue
Closed
opened 2026-02-16 12:51:02 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 12:51:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @pitininja on GitHub (Oct 21, 2021).

Hello everyone,

Thanks for this project it's awesome and I hope it's gonna grow big.

I'm trying to deploy Revolt on my personal server. To do so I have deployed the Docker containers using the docker-compose on this project.

I'm trying to setup all of this behind a Nginx proxy (on my server domain, with HTTPS) but can't get it to work. For now I have a Nginx proxy that proxies https://revolt.mydomain.com/ to http://local.revolt.chat:5000 but when I go to the Revolt app page, I have network errors since the client is trying to reach the backend on http://local.revolt.chat:8000.

  • Am I on the right track?
  • How can I properly proxy everything (client, backend, other services, etc.)?
  • Is it safe to expose all of these services?

Here is my .env file:

# URL to where the Revolt app is publicly accessible
REVOLT_APP_URL=http://local.revolt.chat:5000

# URL to where the API is publicly accessible
REVOLT_PUBLIC_URL=http://local.revolt.chat:8000
VITE_API_URL=http://local.revolt.chat:8000

# URL to where the WebSocket server is publicly accessible
REVOLT_EXTERNAL_WS_URL=ws://local.revolt.chat:9000

# URL to where Autumn is publicly available
AUTUMN_PUBLIC_URL=http://local.revolt.chat:3000

# URL to where January is publicly available
JANUARY_PUBLIC_URL=http://local.revolt.chat:7000

# URL to where Vortex is publicly available
# VOSO_PUBLIC_URL=https://voso.revolt.chat


##
## hCaptcha Settings
##

# If you are sure that you don't want to use hCaptcha, set to 1.
REVOLT_UNSAFE_NO_CAPTCHA=0

# hCaptcha API key
REVOLT_HCAPTCHA_KEY=******

# hCaptcha site key
REVOLT_HCAPTCHA_SITEKEY=******


##
## Email Settings
##

# If you are sure that you don't want to use email verification, set to 1.
REVOLT_UNSAFE_NO_EMAIL=0

# SMTP host
# REVOLT_SMTP_HOST=smtp.example.com

# SMTP username
# REVOLT_SMTP_USERNAME=noreply@example.com

# SMTP password
# REVOLT_SMTP_PASSWORD=CHANGEME

# SMTP From header
# REVOLT_SMTP_FROM=Revolt <noreply@example.com>


##
## Application Settings
##

# Whether to only allow users to sign up if they have an invite code
REVOLT_INVITE_ONLY=1

# Maximum number of people that can be in a group chat
REVOLT_MAX_GROUP_SIZE=50

# VAPID keys for push notifications
# Generate using this guide: https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid
# --> Please replace these keys before going into production! <--
REVOLT_VAPID_PRIVATE_KEY=******
REVOLT_VAPID_PUBLIC_KEY=******


##
## Autumn configuration
##

# S3 Region
AUTUMN_S3_REGION=minio

# S3 Endpoint
AUTUMN_S3_ENDPOINT=http://minio:9000

# MinIO Root User
MINIO_ROOT_USER=minioautumn

# MinIO Root Password
MINIO_ROOT_PASSWORD=minioautumn

# AWS Access Key ID (auto-filled if present above)
# AWS_ACCESS_KEY_ID=minioautumn

# AWS Secret Key (auto-filled if present above)
# AWS_SECRET_ACCESS_KEY=minioautumn


##
## Vortex configuration
##

# VOSO_MANAGE_TOKEN=CHANGEME

Thanks for any help

Originally created by @pitininja on GitHub (Oct 21, 2021). Hello everyone, Thanks for this project it's awesome and I hope it's gonna grow big. I'm trying to deploy Revolt on my personal server. To do so I have deployed the Docker containers using the docker-compose on this project. I'm trying to setup all of this behind a Nginx proxy (on my server domain, with HTTPS) but can't get it to work. For now I have a Nginx proxy that proxies `https://revolt.mydomain.com/` to `http://local.revolt.chat:5000` but when I go to the Revolt app page, I have network errors since the client is trying to reach the backend on `http://local.revolt.chat:8000`. * Am I on the right track? * How can I properly proxy everything (client, backend, other services, etc.)? * Is it safe to expose all of these services? Here is my `.env` file: ``` # URL to where the Revolt app is publicly accessible REVOLT_APP_URL=http://local.revolt.chat:5000 # URL to where the API is publicly accessible REVOLT_PUBLIC_URL=http://local.revolt.chat:8000 VITE_API_URL=http://local.revolt.chat:8000 # URL to where the WebSocket server is publicly accessible REVOLT_EXTERNAL_WS_URL=ws://local.revolt.chat:9000 # URL to where Autumn is publicly available AUTUMN_PUBLIC_URL=http://local.revolt.chat:3000 # URL to where January is publicly available JANUARY_PUBLIC_URL=http://local.revolt.chat:7000 # URL to where Vortex is publicly available # VOSO_PUBLIC_URL=https://voso.revolt.chat ## ## hCaptcha Settings ## # If you are sure that you don't want to use hCaptcha, set to 1. REVOLT_UNSAFE_NO_CAPTCHA=0 # hCaptcha API key REVOLT_HCAPTCHA_KEY=****** # hCaptcha site key REVOLT_HCAPTCHA_SITEKEY=****** ## ## Email Settings ## # If you are sure that you don't want to use email verification, set to 1. REVOLT_UNSAFE_NO_EMAIL=0 # SMTP host # REVOLT_SMTP_HOST=smtp.example.com # SMTP username # REVOLT_SMTP_USERNAME=noreply@example.com # SMTP password # REVOLT_SMTP_PASSWORD=CHANGEME # SMTP From header # REVOLT_SMTP_FROM=Revolt <noreply@example.com> ## ## Application Settings ## # Whether to only allow users to sign up if they have an invite code REVOLT_INVITE_ONLY=1 # Maximum number of people that can be in a group chat REVOLT_MAX_GROUP_SIZE=50 # VAPID keys for push notifications # Generate using this guide: https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid # --> Please replace these keys before going into production! <-- REVOLT_VAPID_PRIVATE_KEY=****** REVOLT_VAPID_PUBLIC_KEY=****** ## ## Autumn configuration ## # S3 Region AUTUMN_S3_REGION=minio # S3 Endpoint AUTUMN_S3_ENDPOINT=http://minio:9000 # MinIO Root User MINIO_ROOT_USER=minioautumn # MinIO Root Password MINIO_ROOT_PASSWORD=minioautumn # AWS Access Key ID (auto-filled if present above) # AWS_ACCESS_KEY_ID=minioautumn # AWS Secret Key (auto-filled if present above) # AWS_SECRET_ACCESS_KEY=minioautumn ## ## Vortex configuration ## # VOSO_MANAGE_TOKEN=CHANGEME ``` Thanks for any help
yindo closed this issue 2026-02-16 12:51:02 -05:00
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@Mar0xy commented on GitHub (Oct 22, 2021):

You need to proxy to localhost:5000, localhost:8000 and etc then change the urls in the .env file to your domain urls as the urls in the .env file are used to set the locations of where the client tries to get the data from.
Look at this file for an example nginx config.

@Mar0xy commented on GitHub (Oct 22, 2021): You need to proxy to localhost:5000, localhost:8000 and etc then change the urls in the .env file to your domain urls as the urls in the .env file are used to set the locations of where the client tries to get the data from. Look at this [file](https://github.com/revoltchat/self-hosted/blob/55f0192a600d41ebaeeee5f4abd5ccd1c1b6fa4f/nginx.conf.example) for an example nginx config.
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@jim3692 commented on GitHub (Oct 29, 2021):

I have a working Revolt configuration with nginx in my repo jim3692/self-hosted
EDIT: I haven't added january yet

@jim3692 commented on GitHub (Oct 29, 2021): I have a working Revolt configuration with nginx in my repo [jim3692/self-hosted](https://github.com/jim3692/self-hosted) EDIT: I haven't added january yet
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@insertish commented on GitHub (Oct 31, 2021):

.env file is used by the server to provide the client with the information it needs to connect to Revolt, hence it needs to be your public endpoints there.

The default configuration is intended for running the stack on the same machine.

@insertish commented on GitHub (Oct 31, 2021): `.env` file is used by the server to provide the client with the information it needs to connect to Revolt, hence it needs to be your public endpoints there. The default configuration is intended for running the stack on the same machine.
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@pitininja commented on GitHub (Oct 31, 2021):

Thank you very much for your answers everyone, it helped me a lot!

I did pretty much like in the example provided by @jim3692 and it works fine 👍

Is it okay (from a security point of view) to publicly expose all these services on my server?

Also (forgive me as this is off topic) is it possible to target my self hosted server when using the desktop application?

@pitininja commented on GitHub (Oct 31, 2021): Thank you very much for your answers everyone, it helped me a lot! I did pretty much like in the example provided by @jim3692 and it works fine 👍 Is it okay (from a security point of view) to publicly expose all these services on my server? Also (forgive me as this is off topic) is it possible to target my self hosted server when using the desktop application?
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@jim3692 commented on GitHub (Nov 1, 2021):

Deploying you own VPN to connect to your server would be much safer, but I don't think it's worth it.

For the desktop application, you need to change the domain in config.ts and rebuild the app.

@jim3692 commented on GitHub (Nov 1, 2021): Deploying you own VPN to connect to your server would be much safer, but I don't think it's worth it. For the desktop application, you need to change the domain in [config.ts](https://github.com/revoltchat/desktop/blob/master/src/lib/config.ts) and rebuild the app.
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@pitininja commented on GitHub (Nov 1, 2021):

Perfect, many thanks again sir 👍

@pitininja commented on GitHub (Nov 1, 2021): Perfect, many thanks again sir 👍
yindo commented 2026-02-16 12:51:03 -05:00
Author
Owner
Copy Link
Copy Source

@insertish commented on GitHub (Jan 5, 2022):

Assuming this was fixed, closing.

Is it okay (from a security point of view) to publicly expose all these services on my server?

There shouldn't be any harm in theory, although:

  • You shouldn't expose your database without configuring authentication.
  • You should generally enable a firewall and only allow things you want to be public through, using something like ufw.
  • You can also use Docker networking to keep all of these containers in their own private network then pointing nginx to those.
@insertish commented on GitHub (Jan 5, 2022): Assuming this was fixed, closing. > Is it okay (from a security point of view) to publicly expose all these services on my server? There shouldn't be any harm in theory, although: - You shouldn't expose your database without configuring authentication. - You should generally enable a firewall and only allow things you want to be public through, using something like `ufw`. - You can also use Docker networking to keep all of these containers in their own private network then pointing nginx to those.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
help wanted
improvement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?