Last active
June 4, 2025 23:49
-
-
Save Lvdwardt/707d9c3fb4581d38102399f91a21c9c6 to your computer and use it in GitHub Desktop.
Rustdesk + Nginx proxy manager
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
version: '3' | |
networks: | |
rustdesk-net: | |
external: false | |
services: | |
nginx-proxy-manager: | |
image: 'jc21/nginx-proxy-manager:latest' | |
restart: unless-stopped | |
ports: | |
# These ports are in format <host-port>:<container-port> | |
- '80:80' # Public HTTP Port | |
- '443:443' # Public HTTPS Port | |
- '8081:81' # Admin Web Port | |
# Add any other Stream port you want to expose | |
# - '21:21' # FTP | |
# Ports needed for Rustdesk: | |
- '21115:21115' | |
- '21116:21116' | |
- '21116:21116/udp' | |
- '21117:21117' | |
- '21118:21118' | |
- '21119:21119' | |
# Uncomment the next line if you uncomment anything in the section | |
# environment: | |
# Uncomment this if you want to change the location of | |
# the SQLite DB file within the container | |
# DB_SQLITE_FILE: "/data/database.sqlite" | |
# Uncomment this if IPv6 is not enabled on your host/ | |
# DISABLE_IPV6: 'true' | |
volumes: | |
- ./data:/data | |
- ./letsencrypt:/etc/letsencrypt | |
networks: | |
- rustdesk-net | |
hbbs: | |
container_name: hbbs | |
image: rustdesk/rustdesk-server:latest | |
command: hbbs -r rustdesk.yourDomain.com:21117 | |
volumes: | |
- ./data:/root | |
networks: | |
- rustdesk-net | |
depends_on: | |
- hbbr | |
restart: unless-stopped | |
hbbr: | |
container_name: hbbr | |
image: rustdesk/rustdesk-server:latest | |
command: hbbr | |
volumes: | |
- ./data:/root | |
networks: | |
- rustdesk-net | |
restart: unless-stopped |
I wouldn't try to use nginx as per the original post has suggested. Routing traffic through nginx, as shown in this post, means that you dont have a router. Most people have a router. Why route traffic twice before it hits the Rustdesk containers?
Simplify is your friend. Remove useless layers of complexity.
Here's what I got going on my home lab.
After traffic hits my router, my router forwards the rustdesk named opened ports to the rustdesk containers
Since you're running Pi-hole, do this:
Yes, it is that simple.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I
m using pihole, but pihole won
t route the incoming traffic to my container .. nginx will do ... only using traffic internally unbound. I also have local dns setup for but I`m not sure I can setup external FQDNS into my internal instance as from what I know this will screw everything up.my rustdesk.external.com domain points to my wan ip and from there ngnix takes traffic where it needs to go via streams ...
I
m using 2 nginx instances .. the old one I always had which routes https traffic to the required containers and authelia as required and also using nginx for rustdesk where I
m pointing the traffic from my LXC local ip internally to docker bridge network created by rustdesk ...the setup was working fine until recently
so on my main desktop (as I have a few on my lan) when opening rustdesk all history connections show up fine .. if I log in locally it works ... but the remote ones even if shown with green dot, when I try to connect to them it hangs for a while .. and throws a relay problem ... same when i try to connect from one of them remotec desktops into my own desktop ..
I tried so far :
all above looking good, I can connect to all my servers behind the ngnix, I
m using quite a few .. it
s only rustdesk that stopped working