What you're actually doing when you access RustDesk on Docker

RustDesk is remote desktop software — it lets you see and control another computer's screen from wherever you are. When you install it inside Docker on a Synology NAS, you're running RustDesk in a containerized environment, which means it's isolated from the rest of your NAS but still needs a way for you to reach it from outside that container.

The challenge is that Docker containers don't automatically expose their ports to the network the way a regular process does. You have to tell Docker which ports RustDesk uses and map them to ports on your NAS itself. Once you do that, you can connect to RustDesk the same way you would if it were installed directly on any other computer.

Key Takeaways

  • RustDesk inside Docker requires port mapping — you must tell Docker which ports to forward from the container to your NAS so the outside world can reach RustDesk.
  • The RustDesk console (the control panel where you manage settings) typically runs on port 21114 inside the container and needs to be mapped to an accessible port on your NAS.
  • You access the console through your web browser by typing your NAS IP address or hostname plus the mapped port number.
  • Port mapping happens either when you first create the Docker container or by editing the container settings in Synology's Docker interface.
  • If you cannot reach the console, the most common cause is that the port mapping was not created or the container is not running.

Setting up port mapping in Synology Docker

Open the Docker process on your Synology NAS. If you already have a RustDesk container running, right-click it and select Edit. If you are creating a new container, you will set up port mapping during the creation process.

Look for the Port Settings section. You need to map a port on your NAS to port 21114 inside the container (this is where RustDesk's web console listens). For example, you might map port 21114 on the container to port 21114 on your NAS, or to any other unused port like 8080 or 9000 if 21114 is already in use. Write down which port you choose — you will need it to access the console.

If you are editing an existing container, explore the changes and the container will restart. If you are creating a new one, finish the setup and start the container. Wait 30 seconds to a minute for it to fully initialize before trying to access it.

Accessing the RustDesk console through your browser

Once the port mapping is in place and the container is running, open a web browser on any computer on your network. In the address bar, type your NAS IP address or hostname followed by a colon and the port number you mapped. For example, if your NAS IP is 192.168.1.100 and you mapped port 21114, you would type 192.168.1.100:21114.

Press Enter. The RustDesk console login page should appear. If you set up RustDesk with a username and password during installation, enter those credentials. If you did not set a password, check the RustDesk documentation or the Docker image you used — some images come with a default username and password that you should change when ready.

Once logged in, you can configure RustDesk settings, manage connections, and set up remote access to other devices.

Finding your NAS IP address and hostname

If you do not know your NAS IP address, open the Synology Control Panel and go to Network. The IP address is listed under the active network connection. You can also use your NAS hostname (usually something like Synology or a custom name you set) instead of the IP address — type Synology:21114 or Synology:yourport in your browser.

If you are accessing RustDesk from outside your home or office network, you will need to set up port forwarding on your router to reach your NAS from the internet. This is a separate step and involves logging into your router's settings. Be aware that exposing RustDesk to the internet increases security risk — use a strong password and consider a VPN as an alternative.

Troubleshooting when the console will not load

If you type the address and nothing appears, first check that the Docker container is actually running. In the Synology Docker app, look at the container list and confirm the RustDesk container shows a green status indicator. If it is stopped, click it and select Start.

Next, verify the port mapping is correct. Right-click the container and select Edit, then check the Port Settings section. Confirm that port 21114 (or whichever port RustDesk uses) is mapped to a port on your NAS. If the mapping is missing, add it, explore the changes, and wait for the container to restart.

If the container is running and the port mapping exists, try accessing the console from a different device on your network to rule out a browser cache issue. Clear your browser cache and try again. If you still cannot reach it, check your NAS firewall settings — go to Control Panel, Security, and Firewall to confirm the port is not blocked.

Understanding Docker networking on Synology

Docker containers on Synology run in an isolated network by default. This isolation protects your NAS, but it also means the container cannot be reached from outside unless you explicitly map ports. Port mapping is the bridge between the container's internal network and your NAS's external network.

When you map port 21114 inside the container to port 21114 on your NAS, Docker listens on your NAS's port 21114 and forwards any traffic to the container's port 21114. This is why you type your NAS address and the mapped port — you are not actually connecting to the container directly; you are connecting to your NAS, which then routes the traffic to the container.

Frequently Asked Questions

Can I access the RustDesk console from outside my network?

Yes, but you need to set up port forwarding on your router to expose your NAS to the internet. This is a router setting, not a Docker or Synology setting. However, exposing RustDesk to the internet carries security risk. A VPN is often safer — connect to your home network via VPN first, then access RustDesk as if you were home.

What if port 21114 is already in use on my NAS?

Map the container's port 21114 to a different port on your NAS, such as 8080 or 9000. Then access the console using that port number instead — for example, 192.168.1.100:8080. The port number you use externally does not have to match the port inside the container.

Do I need to set up port mapping every time I restart the container?

No. Port mapping is saved as part of the container configuration. Once you set it up, it persists even if you stop and restart the container. You only need to set it up once, or if you change it intentionally.

Why does the login page appear but I cannot log in?

Check the username and password you used during RustDesk setup. Some Docker images come with default credentials — check the image documentation. If you forgot the password, you may need to delete the container and create a new one with credentials you know, or check if the image supports a password reset.

Is it safe to expose RustDesk to the internet?

RustDesk itself is reasonably find, but exposing any service to the internet increases attack surface. Use a strong, unique password. Consider limiting access to specific IP addresses if your router supports it, or use a VPN instead of direct internet exposure.