extern/doc.rustdesk.com
1
0
Fork 1
mirror of https://github.com/rustdesk/doc.rustdesk.com.git synced 2025-06-25 12:12:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

<YOUR_DOMAIN> to avoid confusion

Browse Source
This commit is contained in:
rustdesk 2025-06-24 23:30:20 +08:00
parent a734c98f70
commit 1f4d49ce32
9 changed files with 166 additions and 166 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/self-host/rustdesk-server-pro/faq/_index.de.md
View File

@ -368,7 +368,7 @@ Hinweis: Führen Sie `sudo service nginx restart` aus, wenn Sie die `rustdesk.co
### 8. WebSocket Secure (WSS) Unterstützung für den ID-Server und Relay-Server hinzufügen, um sichere Kommunikation für alle Plattformen zu ermöglichen
Fügen Sie die folgende Konfiguration zum ersten `server`-Abschnitt der Datei `/etc/nginx/.../rustdesk.conf` hinzu und starten Sie dann den `Nginx`-Dienst neu.
Der Web-Client kann über `https://<YOUR_DOMAIN>/web` aufgerufen werden. Benutzerdefinierte Clients können WebSocket verwenden, indem sie in den erweiterten Optionen `allow-websocket=Y` einstellen. Wenn der benutzerdefinierte Client mit aktiviertem WebSocket verwendet wird, wird er kein TCP/UDP nutzen und kann nur über ein Relais (außer bei direkten IP-Verbindungen) verbunden werden. Wenn nur dieser WebSocket-aktivierte Client verwendet wird, kann der Server die Ports 21114 bis 21119 schließen und nur Port 443 offen halten.
Der Web-Client kann über `https://YOUR_DOMAIN/web` aufgerufen werden. Benutzerdefinierte Clients können WebSocket verwenden, indem sie in den erweiterten Optionen `allow-websocket=Y` einstellen. Wenn der benutzerdefinierte Client mit aktiviertem WebSocket verwendet wird, wird er kein TCP/UDP nutzen und kann nur über ein Relais (außer bei direkten IP-Verbindungen) verbunden werden. Wenn nur dieser WebSocket-aktivierte Client verwendet wird, kann der Server die Ports 21114 bis 21119 schließen und nur Port 443 offen halten.
```
location /ws/id {
@ -400,7 +400,7 @@ Die vollständige Konfiguration lautet:
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -432,18 +432,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.en.md
View File

@ -233,7 +233,7 @@ For example, if you buy a domain name `example.com` from `Namesilo` and your ser
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* It takes some time for DNS to take effect, https://www.whatsmydns.net and check whether the domain name has been resolved to your server's IP address. Step 6 depends on the correct resolve result. In the following steps, replace `<YOUR_DOMAIN>` with your subdomain, e.g. `rustdesk.example.com`.
* It takes some time for DNS to take effect, https://www.whatsmydns.net and check whether the domain name has been resolved to your server's IP address. Step 6 depends on the correct resolve result. In the following steps, replace `YOUR_DOMAIN` with your subdomain, e.g. `rustdesk.example.com`.
### 2. Install Nginx
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -254,11 +254,11 @@ Run `certbot -h` to check whether it has been installed successfully.
### 4. Config Nginx
There are two ways:
* If directory `/etc/nginx/sites-available` and `/etc/nginx/sites-enabled` exists, replace `<YOUR_DOMAIN>` of the following command with your domain name and run it.
* If directory `/etc/nginx/sites-available` and `/etc/nginx/sites-enabled` exists, replace `YOUR_DOMAIN` of the following command with your domain name and run it.
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -271,11 +271,11 @@ Then run `sudo ln -s /etc/nginx/sites-available/rustdesk.conf /etc/nginx/sites-e
Run `cat /etc/nginx/sites-available/rustdesk.conf` to make sure its content is correct.
* If directory `/etc/nginx/sites-available` and `/etc/nginx/sites-enabled` don't exist and directory `/etc/nginx/conf.d` exists, replace `<YOUR_DOMAIN>` of the following command with your domain name and run it.
* If directory `/etc/nginx/sites-available` and `/etc/nginx/sites-enabled` don't exist and directory `/etc/nginx/conf.d` exists, replace `YOUR_DOMAIN` of the following command with your domain name and run it.
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -305,7 +305,7 @@ If it prompts `Enter email address (used for urgent renewal and security notices
Finally, the content of `rustdesk.conf` should be like this:
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -313,18 +313,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -332,11 +332,11 @@ server {
Here are some common errors:
* The console prints `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` rather than `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`.
* The console prints `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` rather than `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`.
The reason may be Certbot doesn't find the `rustdesk.conf` file, you can try one of the following solutions:
- Check the result of the step 5, run `sudo service nginx restart`.
- Copy the server configs `server{...}` which contain `<YOUR_DOMAIN>` to `rustdesk.conf`, and change `location{...}` to the content below.
- Copy the server configs `server{...}` which contain `YOUR_DOMAIN` to `rustdesk.conf`, and change `location{...}` to the content below.
```sh
location / {
@ -348,7 +348,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
Solution: Add another domain name to DNS and change `<YOUR_DOMAIN>` to it, e.g. `rustdesk2.example.com`. Then repeat step 1, 4, 6.
Solution: Add another domain name to DNS and change `YOUR_DOMAIN` to it, e.g. `rustdesk2.example.com`. Then repeat step 1, 4, 6.
* `Error getting validation data`
@ -357,12 +357,12 @@ Solution: it may be caused by firewall, please refer to https://rustdesk.com/doc
Notice: Run `sudo service nginx restart` if you change the `rustdesk.conf` manually.
### 7. Login to the web page
* Open `https://<YOUR_DOMAIN>` in the browser, log in using the default user name "admin" and password "test1234", then change the password to your own.
* Open `https://YOUR_DOMAIN` in the browser, log in using the default user name "admin" and password "test1234", then change the password to your own.
### 8. Add WebSocket Secure (WSS) support for the id server and relay server to enable secure communication for all platforms.
Add the following configuration to the first `server` section of the `/etc/nginx/.../rustdesk.conf` file, then restart the `Nginx` service.
The web client can be accessed via `https://<YOUR_DOMAIN>/web`. Custom clients can use WebSocket by setting `allow-websocket=Y` in the advanced options. If the custom client with WebSocket enabled is used, it will not utilize TCP/UDP and can only connect through a relay (except for direct IP connections). If only this WebSocket-enabled client is used, the server can close ports 21114 to 21119 and only keep port 443 open.
The web client can be accessed via `https://YOUR_DOMAIN/web`. Custom clients can use WebSocket by setting `allow-websocket=Y` in the advanced options. If the custom client with WebSocket enabled is used, it will not utilize TCP/UDP and can only connect through a relay (except for direct IP connections). If only this WebSocket-enabled client is used, the server can close ports 21114 to 21119 and only keep port 443 open.
@ -397,7 +397,7 @@ The full configuration is
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -429,18 +429,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.es.md
View File

@ -233,7 +233,7 @@ Por ejemplo, si compras un nombre de dominio `example.com` de `Namesilo` y la di
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* Toma algún tiempo para que el DNS surta efecto, https://www.whatsmydns.net y verifica si el nombre de dominio se ha resuelto a la dirección IP de tu servidor. El paso 6 depende del resultado correcto de resolución. En los siguientes pasos, reemplaza `<YOUR_DOMAIN>` con tu subdominio, ej. `rustdesk.example.com`.
* Toma algún tiempo para que el DNS surta efecto, https://www.whatsmydns.net y verifica si el nombre de dominio se ha resuelto a la dirección IP de tu servidor. El paso 6 depende del resultado correcto de resolución. En los siguientes pasos, reemplaza `YOUR_DOMAIN` con tu subdominio, ej. `rustdesk.example.com`.
### 2. Instalar Nginx
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -254,11 +254,11 @@ Ejecuta `certbot -h` para verificar si se ha instalado correctamente.
### 4. Configurar Nginx
Hay dos formas:
* Si existen los directorios `/etc/nginx/sites-available` y `/etc/nginx/sites-enabled`, reemplaza `<YOUR_DOMAIN>` del siguiente comando con tu nombre de dominio y ejecútalo.
* Si existen los directorios `/etc/nginx/sites-available` y `/etc/nginx/sites-enabled`, reemplaza `YOUR_DOMAIN` del siguiente comando con tu nombre de dominio y ejecútalo.
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -271,11 +271,11 @@ Luego ejecuta `sudo ln -s /etc/nginx/sites-available/rustdesk.conf /etc/nginx/si
Ejecuta `cat /etc/nginx/sites-available/rustdesk.conf` para asegurarte de que su contenido sea correcto.
* Si los directorios `/etc/nginx/sites-available` y `/etc/nginx/sites-enabled` no existen y existe el directorio `/etc/nginx/conf.d`, reemplaza `<YOUR_DOMAIN>` del siguiente comando con tu nombre de dominio y ejecútalo.
* Si los directorios `/etc/nginx/sites-available` y `/etc/nginx/sites-enabled` no existen y existe el directorio `/etc/nginx/conf.d`, reemplaza `YOUR_DOMAIN` del siguiente comando con tu nombre de dominio y ejecútalo.
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -305,7 +305,7 @@ Si te solicita `Enter email address (used for urgent renewal and security notice
Finalmente, el contenido de `rustdesk.conf` debería ser así:
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -313,18 +313,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -332,11 +332,11 @@ server {
Aquí hay algunos errores comunes:
* La consola imprime `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` en lugar de `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`.
* La consola imprime `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` en lugar de `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`.
La razón puede ser que Certbot no encuentra el archivo `rustdesk.conf`, puedes probar una de las siguientes soluciones:
- Verifica el resultado del paso 5, ejecuta `sudo service nginx restart`.
- Copia las configuraciones del servidor `server{...}` que contienen `<YOUR_DOMAIN>` a `rustdesk.conf`, y cambia `location{...}` al contenido siguiente.
- Copia las configuraciones del servidor `server{...}` que contienen `YOUR_DOMAIN` a `rustdesk.conf`, y cambia `location{...}` al contenido siguiente.
```sh
location / {
@ -348,7 +348,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
Solución: Agrega otro nombre de dominio a DNS y cambia `<YOUR_DOMAIN>` por él, ej. `rustdesk2.example.com`. Luego repite los pasos 1, 4, 6.
Solución: Agrega otro nombre de dominio a DNS y cambia `YOUR_DOMAIN` por él, ej. `rustdesk2.example.com`. Luego repite los pasos 1, 4, 6.
* `Error getting validation data`
@ -357,12 +357,12 @@ Solución: puede ser causado por el firewall, por favor consulta https://rustdes
Aviso: Ejecuta `sudo service nginx restart` si cambias `rustdesk.conf` manualmente.
### 7. Iniciar sesión en la página web
* Abre `https://<YOUR_DOMAIN>` en el navegador, inicia sesión usando el nombre de usuario predeterminado "admin" y contraseña "test1234", luego cambia la contraseña a la tuya.
* Abre `https://YOUR_DOMAIN` en el navegador, inicia sesión usando el nombre de usuario predeterminado "admin" y contraseña "test1234", luego cambia la contraseña a la tuya.
### 8. Agregar soporte WebSocket Secure (WSS) para el servidor de ID y el servidor relay para habilitar comunicación segura en todas las plataformas.
Agrega la siguiente configuración a la primera sección `server` del archivo `/etc/nginx/.../rustdesk.conf`, luego reinicia el servicio `Nginx`.
El cliente web se puede acceder a través de `https://<YOUR_DOMAIN>/web`. Los clientes personalizados pueden usar WebSocket estableciendo `allow-websocket=Y` en las opciones avanzadas. Si se usa el cliente personalizado con WebSocket habilitado, no utilizará TCP/UDP y solo podrá conectarse a través de relay (excepto para conexiones IP directas). Si solo se usa este cliente con WebSocket habilitado, el servidor puede cerrar los puertos 21114 a 21119 y solo mantener abierto el puerto 443.
El cliente web se puede acceder a través de `https://YOUR_DOMAIN/web`. Los clientes personalizados pueden usar WebSocket estableciendo `allow-websocket=Y` en las opciones avanzadas. Si se usa el cliente personalizado con WebSocket habilitado, no utilizará TCP/UDP y solo podrá conectarse a través de relay (excepto para conexiones IP directas). Si solo se usa este cliente con WebSocket habilitado, el servidor puede cerrar los puertos 21114 a 21119 y solo mantener abierto el puerto 443.
@ -397,7 +397,7 @@ La configuración completa es
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -429,18 +429,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.fr.md
View File

@ -233,7 +233,7 @@ Par exemple, si vous achetez un nom de domaine `example.com` de `Namesilo` et qu
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* Il faut du temps pour que le DNS prenne effet, https://www.whatsmydns.net et vérifiez si le nom de domaine a été résolu vers l'adresse IP de votre serveur. L'étape 6 dépend du résultat de résolution correct. Dans les étapes suivantes, remplacez `<YOUR_DOMAIN>` par votre sous-domaine, par exemple `rustdesk.example.com`.
* Il faut du temps pour que le DNS prenne effet, https://www.whatsmydns.net et vérifiez si le nom de domaine a été résolu vers l'adresse IP de votre serveur. L'étape 6 dépend du résultat de résolution correct. Dans les étapes suivantes, remplacez `YOUR_DOMAIN` par votre sous-domaine, par exemple `rustdesk.example.com`.
### 2. Installer Nginx
* Debian/Ubuntu : `sudo apt-get install nginx`
@ -254,11 +254,11 @@ Exécutez `certbot -h` pour vérifier s'il a été installé avec succès.
### 4. Configurer Nginx
Il y a deux façons :
* Si les répertoires `/etc/nginx/sites-available` et `/etc/nginx/sites-enabled` existent, remplacez `<YOUR_DOMAIN>` de la commande suivante par votre nom de domaine et exécutez-la.
* Si les répertoires `/etc/nginx/sites-available` et `/etc/nginx/sites-enabled` existent, remplacez `YOUR_DOMAIN` de la commande suivante par votre nom de domaine et exécutez-la.
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -271,11 +271,11 @@ Puis exécutez `sudo ln -s /etc/nginx/sites-available/rustdesk.conf /etc/nginx/s
Exécutez `cat /etc/nginx/sites-available/rustdesk.conf` pour vous assurer que son contenu est correct.
* Si les répertoires `/etc/nginx/sites-available` et `/etc/nginx/sites-enabled` n'existent pas et que le répertoire `/etc/nginx/conf.d` existe, remplacez `<YOUR_DOMAIN>` de la commande suivante par votre nom de domaine et exécutez-la.
* Si les répertoires `/etc/nginx/sites-available` et `/etc/nginx/sites-enabled` n'existent pas et que le répertoire `/etc/nginx/conf.d` existe, remplacez `YOUR_DOMAIN` de la commande suivante par votre nom de domaine et exécutez-la.
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -305,7 +305,7 @@ S'il vous demande `Enter email address (used for urgent renewal and security not
Finalement, le contenu de `rustdesk.conf` devrait ressembler à ceci :
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -313,18 +313,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -332,11 +332,11 @@ server {
Voici quelques erreurs courantes :
* La console affiche `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` plutôt que `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`.
* La console affiche `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` plutôt que `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`.
La raison peut être que Certbot ne trouve pas le fichier `rustdesk.conf`, vous pouvez essayer l'une des solutions suivantes :
- Vérifiez le résultat de l'étape 5, exécutez `sudo service nginx restart`.
- Copiez les configurations de serveur `server{...}` qui contiennent `<YOUR_DOMAIN>` vers `rustdesk.conf`, et changez `location{...}` vers le contenu ci-dessous.
- Copiez les configurations de serveur `server{...}` qui contiennent `YOUR_DOMAIN` vers `rustdesk.conf`, et changez `location{...}` vers le contenu ci-dessous.
```sh
location / {
@ -348,7 +348,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
Solution : Ajoutez un autre nom de domaine au DNS et changez `<YOUR_DOMAIN>` vers celui-ci, par exemple `rustdesk2.example.com`. Puis répétez les étapes 1, 4, 6.
Solution : Ajoutez un autre nom de domaine au DNS et changez `YOUR_DOMAIN` vers celui-ci, par exemple `rustdesk2.example.com`. Puis répétez les étapes 1, 4, 6.
* `Error getting validation data`
@ -357,12 +357,12 @@ Solution : cela peut être causé par le pare-feu, veuillez vous référer à ht
Notice : Exécutez `sudo service nginx restart` si vous changez le `rustdesk.conf` manuellement.
### 7. Se connecter à la page web
* Ouvrez `https://<YOUR_DOMAIN>` dans le navigateur, connectez-vous en utilisant le nom d'utilisateur par défaut "admin" et le mot de passe "test1234", puis changez le mot de passe vers le vôtre.
* Ouvrez `https://YOUR_DOMAIN` dans le navigateur, connectez-vous en utilisant le nom d'utilisateur par défaut "admin" et le mot de passe "test1234", puis changez le mot de passe vers le vôtre.
### 8. Ajouter le support WebSocket Secure (WSS) pour le serveur d'identifiant et le serveur relais pour activer la communication sécurisée pour toutes les plateformes.
Ajoutez la configuration suivante à la première section `server` du fichier `/etc/nginx/.../rustdesk.conf`, puis redémarrez le service `Nginx`.
Le client web peut être accédé via `https://<YOUR_DOMAIN>/web`. Les clients personnalisés peuvent utiliser WebSocket en définissant `allow-websocket=Y` dans les options avancées. Si le client personnalisé avec WebSocket activé est utilisé, il n'utilisera pas TCP/UDP et ne pourra se connecter que par un relais (sauf pour les connexions IP directes). Si seul ce client activé WebSocket est utilisé, le serveur peut fermer les ports 21114 à 21119 et ne garder que le port 443 ouvert.
Le client web peut être accédé via `https://YOUR_DOMAIN/web`. Les clients personnalisés peuvent utiliser WebSocket en définissant `allow-websocket=Y` dans les options avancées. Si le client personnalisé avec WebSocket activé est utilisé, il n'utilisera pas TCP/UDP et ne pourra se connecter que par un relais (sauf pour les connexions IP directes). Si seul ce client activé WebSocket est utilisé, le serveur peut fermer les ports 21114 à 21119 et ne garder que le port 443 ouvert.
```
location /ws/id {
@ -394,7 +394,7 @@ La configuration complète est
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -426,18 +426,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.it.md
View File

@ -161,7 +161,7 @@ Ad esempio, se acquisti un nome di dominio `example.com` da `Namesilo` e l'indir
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* Ci vuole del tempo perché il DNS abbia effetto, https://www.whatsmydns.net e verifica se il nome di dominio è stato risolto all'indirizzo IP del tuo server. Il passaggio 6 dipende dal risultato corretto della risoluzione. Nei passaggi seguenti, sostituisci `<YOUR_DOMAIN>` con il tuo sottodominio, ad es. `rustdesk.example.com`.
* Ci vuole del tempo perché il DNS abbia effetto, https://www.whatsmydns.net e verifica se il nome di dominio è stato risolto all'indirizzo IP del tuo server. Il passaggio 6 dipende dal risultato corretto della risoluzione. Nei passaggi seguenti, sostituisci `YOUR_DOMAIN` con il tuo sottodominio, ad es. `rustdesk.example.com`.
### 2. Installare Nginx
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -182,11 +182,11 @@ Esegui `certbot -h` per verificare se è stato installato correttamente.
### 4. Configurare Nginx
Ci sono due modi:
* Se esistono le directory `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled`, sostituisci `<YOUR_DOMAIN>` del seguente comando con il tuo nome di dominio ed eseguilo.
* Se esistono le directory `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled`, sostituisci `YOUR_DOMAIN` del seguente comando con il tuo nome di dominio ed eseguilo.
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -199,11 +199,11 @@ Quindi esegui `sudo ln -s /etc/nginx/sites-available/rustdesk.conf /etc/nginx/si
Esegui `cat /etc/nginx/sites-available/rustdesk.conf` per assicurarti che il suo contenuto sia corretto.
* Se le directory `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` non esistono e la directory `/etc/nginx/conf.d` esiste, sostituisci `<YOUR_DOMAIN>` del seguente comando con il tuo nome di dominio ed eseguilo.
* Se le directory `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` non esistono e la directory `/etc/nginx/conf.d` esiste, sostituisci `YOUR_DOMAIN` del seguente comando con il tuo nome di dominio ed eseguilo.
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -233,7 +233,7 @@ Se richiede `Enter email address (used for urgent renewal and security notices)`
Infine, il contenuto di `rustdesk.conf` dovrebbe essere così:
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -241,18 +241,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -260,11 +260,11 @@ server {
Ecco alcuni errori comuni:
* La console stampa `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` invece di `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`.
* La console stampa `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` invece di `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`.
Il motivo potrebbe essere che Certbot non trova il file `rustdesk.conf`, puoi provare una delle seguenti soluzioni:
- Controlla il risultato del passaggio 5, esegui `sudo service nginx restart`.
- Copia le configurazioni del server `server{...}` che contengono `<YOUR_DOMAIN>` in `rustdesk.conf`, e cambia `location{...}` nel contenuto seguente.
- Copia le configurazioni del server `server{...}` che contengono `YOUR_DOMAIN` in `rustdesk.conf`, e cambia `location{...}` nel contenuto seguente.
```sh
location / {
@ -276,7 +276,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
Soluzione: Aggiungi un altro nome di dominio al DNS e cambia `<YOUR_DOMAIN>` con esso, ad es. `rustdesk2.example.com`. Quindi ripeti i passaggi 1, 4, 6.
Soluzione: Aggiungi un altro nome di dominio al DNS e cambia `YOUR_DOMAIN` con esso, ad es. `rustdesk2.example.com`. Quindi ripeti i passaggi 1, 4, 6.
* `Error getting validation data`
@ -285,12 +285,12 @@ Soluzione: potrebbe essere causato dal firewall, consulta https://rustdesk.com/d
Avviso: Esegui `sudo service nginx restart` se modifichi `rustdesk.conf` manualmente.
### 7. Accedere alla pagina web
* Apri `https://<YOUR_DOMAIN>` nel browser, accedi usando il nome utente predefinito "admin" e la password "test1234", quindi cambia la password con la tua.
* Apri `https://YOUR_DOMAIN` nel browser, accedi usando il nome utente predefinito "admin" e la password "test1234", quindi cambia la password con la tua.
### 8. Aggiungere supporto WebSocket Secure (WSS) per il server ID e il server relay per abilitare la comunicazione sicura su tutte le piattaforme.
Aggiungi la seguente configurazione alla prima sezione `server` del file `/etc/nginx/.../rustdesk.conf`, quindi riavvia il servizio `Nginx`.
Il client web può essere accessibile tramite `https://<YOUR_DOMAIN>/web`. I client personalizzati possono utilizzare WebSocket impostando `allow-websocket=Y` nelle opzioni avanzate. Se viene utilizzato il client personalizzato con WebSocket abilitato, non utilizzerà TCP/UDP e potrà connettersi solo tramite relay (tranne che per le connessioni IP dirette). Se viene utilizzato solo questo client con WebSocket abilitato, il server può chiudere le porte da 21114 a 21119 e mantenere aperta solo la porta 443.
Il client web può essere accessibile tramite `https://YOUR_DOMAIN/web`. I client personalizzati possono utilizzare WebSocket impostando `allow-websocket=Y` nelle opzioni avanzate. Se viene utilizzato il client personalizzato con WebSocket abilitato, non utilizzerà TCP/UDP e potrà connettersi solo tramite relay (tranne che per le connessioni IP dirette). Se viene utilizzato solo questo client con WebSocket abilitato, il server può chiudere le porte da 21114 a 21119 e mantenere aperta solo la porta 443.
@ -325,7 +325,7 @@ La configurazione completa è
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -357,18 +357,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.ja.md
View File

@ -161,7 +161,7 @@ https://github.com/rustdesk/rustdesk/discussions/6576
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* DNSが有効になるまでには時間がかかります。https://www.whatsmydns.net でドメイン名がサーバーのIPアドレスに解決されたかどうかを確認してください。ステップ6は正しい解決結果に依存します。以下の手順では、`<YOUR_DOMAIN>`をあなたのサブドメインに置き換えてください。例：`rustdesk.example.com`。
* DNSが有効になるまでには時間がかかります。https://www.whatsmydns.net でドメイン名がサーバーのIPアドレスに解決されたかどうかを確認してください。ステップ6は正しい解決結果に依存します。以下の手順では、`YOUR_DOMAIN`をあなたのサブドメインに置き換えてください。例：`rustdesk.example.com`。
### 2. Nginxをインストール
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -182,11 +182,11 @@ https://github.com/rustdesk/rustdesk/discussions/6576
### 4. Nginxを設定
2つの方法があります：
* `/etc/nginx/sites-available`と`/etc/nginx/sites-enabled`ディレクトリが存在する場合、次のコマンドの`<YOUR_DOMAIN>`をあなたのドメイン名に置き換えて実行します。
* `/etc/nginx/sites-available`と`/etc/nginx/sites-enabled`ディレクトリが存在する場合、次のコマンドの`YOUR_DOMAIN`をあなたのドメイン名に置き換えて実行します。
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -199,11 +199,11 @@ EOF
`cat /etc/nginx/sites-available/rustdesk.conf`を実行して、内容が正しいことを確認します。
* `/etc/nginx/sites-available`と`/etc/nginx/sites-enabled`ディレクトリが存在せず、`/etc/nginx/conf.d`ディレクトリが存在する場合、次のコマンドの`<YOUR_DOMAIN>`をあなたのドメイン名に置き換えて実行します。
* `/etc/nginx/sites-available`と`/etc/nginx/sites-enabled`ディレクトリが存在せず、`/etc/nginx/conf.d`ディレクトリが存在する場合、次のコマンドの`YOUR_DOMAIN`をあなたのドメイン名に置き換えて実行します。
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -233,7 +233,7 @@ sudo ufw --force reload
最終的に、`rustdesk.conf`の内容は次のようになるはずです：
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -241,18 +241,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -260,11 +260,11 @@ server {
よくあるエラー：
* コンソールに`Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default`と表示されるが、`Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`ではない。
* コンソールに`Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default`と表示されるが、`Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`ではない。
理由はCertbotが`rustdesk.conf`ファイルを見つけられないことかもしれません。次のいずれかの解決策を試してください：
- ステップ5の結果を確認し、`sudo service nginx restart`を実行します。
- `<YOUR_DOMAIN>`を含む`server{...}`のサーバー設定を`rustdesk.conf`にコピーし、`location{...}`を以下の内容に変更します。
- `YOUR_DOMAIN`を含む`server{...}`のサーバー設定を`rustdesk.conf`にコピーし、`location{...}`を以下の内容に変更します。
```sh
location / {
@ -276,7 +276,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
解決策：DNSに別のドメイン名を追加し、`<YOUR_DOMAIN>`をそれに変更します。例：`rustdesk2.example.com`。その後、ステップ1、4、6を繰り返します。
解決策：DNSに別のドメイン名を追加し、`YOUR_DOMAIN`をそれに変更します。例：`rustdesk2.example.com`。その後、ステップ1、4、6を繰り返します。
* `Error getting validation data`
@ -285,12 +285,12 @@ location / {
注意：`rustdesk.conf`を手動で変更した場合は、`sudo service nginx restart`を実行してください。
### 7. ウェブページにログイン
* ブラウザで`https://<YOUR_DOMAIN>`を開き、デフォルトのユーザー名「admin」とパスワード「test1234」を使用してログインし、パスワードを自分のものに変更します。
* ブラウザで`https://YOUR_DOMAIN`を開き、デフォルトのユーザー名「admin」とパスワード「test1234」を使用してログインし、パスワードを自分のものに変更します。
### 8. すべてのプラットフォームで安全な通信を有効にするために、IDサーバーとリレーサーバーにWebSocket Secure（WSS）サポートを追加する。
`/etc/nginx/.../rustdesk.conf`ファイルの最初の`server`セクションに以下の設定を追加し、`Nginx`サービスを再起動します。
ウェブクライアントは`https://<YOUR_DOMAIN>/web`経由でアクセスできます。カスタムクライアントは、詳細オプションで`allow-websocket=Y`を設定することでWebSocketを使用できます。WebSocketが有効になったカスタムクライアントを使用する場合、TCP/UDPを使用せず、リレー経由でのみ接続できます（直接IP接続を除く）。このWebSocket対応クライアントのみを使用する場合、サーバーはポート21114から21119を閉じて、ポート443のみを開いたままにすることができます。
ウェブクライアントは`https://YOUR_DOMAIN/web`経由でアクセスできます。カスタムクライアントは、詳細オプションで`allow-websocket=Y`を設定することでWebSocketを使用できます。WebSocketが有効になったカスタムクライアントを使用する場合、TCP/UDPを使用せず、リレー経由でのみ接続できます（直接IP接続を除く）。このWebSocket対応クライアントのみを使用する場合、サーバーはポート21114から21119を閉じて、ポート443のみを開いたままにすることができます。
@ -325,7 +325,7 @@ location / {
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -357,18 +357,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.pt.md
View File

@ -229,7 +229,7 @@ Por exemplo, se você comprar um nome de domínio `example.com` da `Namesilo` e
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* Leva algum tempo para o DNS ter efeito, https://www.whatsmydns.net e verifique se o nome de domínio foi resolvido para o endereço IP do seu servidor. O passo 6 depende do resultado correto da resolução. Nos próximos passos, substitua `<YOUR_DOMAIN>` pelo seu subdomínio, por exemplo, `rustdesk.example.com`.
* Leva algum tempo para o DNS ter efeito, https://www.whatsmydns.net e verifique se o nome de domínio foi resolvido para o endereço IP do seu servidor. O passo 6 depende do resultado correto da resolução. Nos próximos passos, substitua `YOUR_DOMAIN` pelo seu subdomínio, por exemplo, `rustdesk.example.com`.
### 2. Instalar Nginx
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -250,11 +250,11 @@ Execute `certbot -h` para verificar se foi instalado com sucesso.
### 4. Configurar Nginx
Existem duas maneiras:
* Se os diretórios `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` existirem, substitua `<YOUR_DOMAIN>` do seguinte comando pelo seu nome de domínio e execute-o.
* Se os diretórios `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` existirem, substitua `YOUR_DOMAIN` do seguinte comando pelo seu nome de domínio e execute-o.
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -267,11 +267,11 @@ Em seguida, execute `sudo ln -s /etc/nginx/sites-available/rustdesk.conf /etc/ng
Execute `cat /etc/nginx/sites-available/rustdesk.conf` para garantir que seu conteúdo esteja correto.
* Se os diretórios `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` não existirem e o diretório `/etc/nginx/conf.d` existir, substitua `<YOUR_DOMAIN>` do seguinte comando pelo seu nome de domínio e execute-o.
* Se os diretórios `/etc/nginx/sites-available` e `/etc/nginx/sites-enabled` não existirem e o diretório `/etc/nginx/conf.d` existir, substitua `YOUR_DOMAIN` do seguinte comando pelo seu nome de domínio e execute-o.
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -301,7 +301,7 @@ Se solicitar `Enter email address (used for urgent renewal and security notices)
Finalmente, o conteúdo de `rustdesk.conf` deve ser assim:
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -309,18 +309,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -328,11 +328,11 @@ server {
Aqui estão alguns erros comuns:
* O console imprime `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` em vez de `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`.
* O console imprime `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` em vez de `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`.
O motivo pode ser que o Certbot não encontra o arquivo `rustdesk.conf`, você pode tentar uma das seguintes soluções:
- Verifique o resultado do passo 5, execute `sudo service nginx restart`.
- Copie as configurações do servidor `server{...}` que contêm `<YOUR_DOMAIN>` para `rustdesk.conf` e altere `location{...}` para o conteúdo abaixo.
- Copie as configurações do servidor `server{...}` que contêm `YOUR_DOMAIN` para `rustdesk.conf` e altere `location{...}` para o conteúdo abaixo.
```sh
location / {
@ -344,7 +344,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
Solução: Adicione outro nome de domínio ao DNS e altere `<YOUR_DOMAIN>` para ele, por exemplo, `rustdesk2.example.com`. Em seguida, repita os passos 1, 4, 6.
Solução: Adicione outro nome de domínio ao DNS e altere `YOUR_DOMAIN` para ele, por exemplo, `rustdesk2.example.com`. Em seguida, repita os passos 1, 4, 6.
* `Error getting validation data`
@ -353,12 +353,12 @@ Solução: pode ser causado por firewall, consulte https://rustdesk.com/docs/en/
Aviso: Execute `sudo service nginx restart` se você alterar o `rustdesk.conf` manualmente.
### 7. Fazer login na página web
* Abra `https://<YOUR_DOMAIN>` no navegador, faça login usando o nome de usuário padrão "admin" e senha "test1234", depois altere a senha para a sua própria.
* Abra `https://YOUR_DOMAIN` no navegador, faça login usando o nome de usuário padrão "admin" e senha "test1234", depois altere a senha para a sua própria.
### 8. Adicionar suporte WebSocket Secure (WSS) para o servidor de ID e servidor de retransmissão para habilitar comunicação segura em todas as plataformas.
Adicione a seguinte configuração à primeira seção `server` do arquivo `/etc/nginx/.../rustdesk.conf`, depois reinicie o serviço `Nginx`.
O cliente web pode ser acessado via `https://<YOUR_DOMAIN>/web`. Clientes personalizados podem usar WebSocket definindo `allow-websocket=Y` nas opções avançadas. Se o cliente personalizado com WebSocket habilitado for usado, ele não utilizará TCP/UDP e só poderá se conectar através de um retransmissor (exceto para conexões diretas de IP). Se apenas este cliente habilitado para WebSocket for usado, o servidor pode fechar as portas 21114 a 21119 e manter apenas a porta 443 aberta.
O cliente web pode ser acessado via `https://YOUR_DOMAIN/web`. Clientes personalizados podem usar WebSocket definindo `allow-websocket=Y` nas opções avançadas. Se o cliente personalizado com WebSocket habilitado for usado, ele não utilizará TCP/UDP e só poderá se conectar através de um retransmissor (exceto para conexões diretas de IP). Se apenas este cliente habilitado para WebSocket for usado, o servidor pode fechar as portas 21114 a 21119 e manter apenas a porta 443 aberta.
@ -393,7 +393,7 @@ A configuração completa é
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -425,18 +425,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.zh-cn.md
View File

@ -301,7 +301,7 @@ net start rustdesk > null
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* DNS 生效需要一些时间，访问 https://www.whatsmydns.net 检查域名是否已解析到您的服务器 IP 地址。第 6 步取决于正确的解析结果。在以下步骤中，将 `<YOUR_DOMAIN>` 替换为您的子域名，例如 `rustdesk.example.com`。
* DNS 生效需要一些时间，访问 https://www.whatsmydns.net 检查域名是否已解析到您的服务器 IP 地址。第 6 步取决于正确的解析结果。在以下步骤中，将 `YOUR_DOMAIN` 替换为您的子域名，例如 `rustdesk.example.com`。
### 2. 安装 Nginx
* Debian/Ubuntu: `sudo apt-get install nginx`
@ -322,11 +322,11 @@ net start rustdesk > null
### 4. 配置 Nginx
有两种方式：
* 如果存在目录 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled`，将以下命令中的 `<YOUR_DOMAIN>` 替换为您的域名并运行。
* 如果存在目录 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled`，将以下命令中的 `YOUR_DOMAIN` 替换为您的域名并运行。
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -339,11 +339,11 @@ EOF
运行 `cat /etc/nginx/sites-available/rustdesk.conf` 确保其内容正确。
* 如果目录 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 不存在，但目录 `/etc/nginx/conf.d` 存在，将以下命令中的 `<YOUR_DOMAIN>` 替换为您的域名并运行。
* 如果目录 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 不存在，但目录 `/etc/nginx/conf.d` 存在，将以下命令中的 `YOUR_DOMAIN` 替换为您的域名并运行。
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -374,7 +374,7 @@ sudo ufw --force reload
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -382,18 +382,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -401,11 +401,11 @@ server {
以下是一些常见错误：
* 控制台打印 `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` 而不是 `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`。
* 控制台打印 `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` 而不是 `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`。
原因可能是 Certbot 找不到 `rustdesk.conf` 文件，您可以尝试以下解决方案之一：
- 检查第 5 步的结果，运行 `sudo service nginx restart`。
- 将包含 `<YOUR_DOMAIN>` 的服务器配置 `server{...}` 复制到 `rustdesk.conf`，并将 `location{...}` 更改为以下内容。
- 将包含 `YOUR_DOMAIN` 的服务器配置 `server{...}` 复制到 `rustdesk.conf`，并将 `location{...}` 更改为以下内容。
```sh
location / {
@ -417,7 +417,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
解决方案：向 DNS 添加另一个域名并将 `<YOUR_DOMAIN>` 更改为它，例如 `rustdesk2.example.com`。然后重复步骤 1、4、6。
解决方案：向 DNS 添加另一个域名并将 `YOUR_DOMAIN` 更改为它，例如 `rustdesk2.example.com`。然后重复步骤 1、4、6。
* `Error getting validation data`
@ -426,12 +426,12 @@ location / {
注意：如果您手动更改了 `rustdesk.conf`，请运行 `sudo service nginx restart`。
### 7. 登录网页
* 在浏览器中打开 `https://<YOUR_DOMAIN>`，使用默认用户名 "admin" 和密码 "test1234" 登录，然后将密码更改为您自己的密码。
* 在浏览器中打开 `https://YOUR_DOMAIN`，使用默认用户名 "admin" 和密码 "test1234" 登录，然后将密码更改为您自己的密码。
### 8. 为 ID 服务器和中继服务器添加 WebSocket Secure (WSS) 支持，以启用所有平台的安全通信
将以下配置添加到 `/etc/nginx/.../rustdesk.conf` 文件的第一个 `server` 部分，然后重启 `Nginx` 服务。
Web客户端通过 `https://<YOUR_DOMAIN>/web`访问, 自定义客户端通过在高级选项中设置 `allow-websocket=Y`来使用websocket。如果自定义客户端中启用了websocket，该自定义客户端将不会被使用tcp/udp, 只能通过中继连接(除IP直连)。如果只使用这种启用了websocket的客户端, 也可以关闭服务器的21114~21119端口, 只开启443端口。
Web客户端通过 `https://YOUR_DOMAIN/web`访问, 自定义客户端通过在高级选项中设置 `allow-websocket=Y`来使用websocket。如果自定义客户端中启用了websocket，该自定义客户端将不会被使用tcp/udp, 只能通过中继连接(除IP直连)。如果只使用这种启用了websocket的客户端, 也可以关闭服务器的21114~21119端口, 只开启443端口。
```
location /ws/id {
proxy_pass http://127.0.0.1:21118;
@ -462,7 +462,7 @@ Web客户端通过 `https://<YOUR_DOMAIN>/web`访问, 自定义客户端通过
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -494,18 +494,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}

40
content/self-host/rustdesk-server-pro/faq/_index.zh-tw.md
View File

@ -233,7 +233,7 @@ https://github.com/rustdesk/rustdesk/discussions/6576
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-button.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-add-a-record.png)
![](/docs/en/self-host/rustdesk-server-pro/faq/images/namesilo-dns-table.png)
* DNS 生效需要一些時間，https://www.whatsmydns.net 檢查域名是否已解析到您的服務器 IP 地址。步驟 6 取決於正確的解析結果。在以下步驟中，將 `<YOUR_DOMAIN>` 替換為您的子域，例如 `rustdesk.example.com`。
* DNS 生效需要一些時間，https://www.whatsmydns.net 檢查域名是否已解析到您的服務器 IP 地址。步驟 6 取決於正確的解析結果。在以下步驟中，將 `YOUR_DOMAIN` 替換為您的子域，例如 `rustdesk.example.com`。
### 2. 安裝 Nginx
* Debian/Ubuntu：`sudo apt-get install nginx`
@ -254,11 +254,11 @@ https://github.com/rustdesk/rustdesk/discussions/6576
### 4. 配置 Nginx
有兩種方法：
* 如果目錄 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 存在，將以下命令中的 `<YOUR_DOMAIN>` 替換為您的域名並運行。
* 如果目錄 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 存在，將以下命令中的 `YOUR_DOMAIN` 替換為您的域名並運行。
```sh
cat > /etc/nginx/sites-available/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -271,11 +271,11 @@ EOF
運行 `cat /etc/nginx/sites-available/rustdesk.conf` 確保其內容正確。
* 如果目錄 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 不存在且目錄 `/etc/nginx/conf.d` 存在，將以下命令中的 `<YOUR_DOMAIN>` 替換為您的域名並運行。
* 如果目錄 `/etc/nginx/sites-available` 和 `/etc/nginx/sites-enabled` 不存在且目錄 `/etc/nginx/conf.d` 存在，將以下命令中的 `YOUR_DOMAIN` 替換為您的域名並運行。
```sh
cat > /etc/nginx/conf.d/rustdesk.conf << EOF
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
@ -305,7 +305,7 @@ sudo ufw --force reload
最終，`rustdesk.conf` 的內容應該是這樣的：
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -313,18 +313,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}
@ -332,11 +332,11 @@ server {
以下是一些常見錯誤：
* 控制台打印 `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../default` 而不是 `Successfully deployed certificate for <YOUR_DOMAIN> to /etc/nginx/.../rustdesk.conf`。
* 控制台打印 `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../default` 而不是 `Successfully deployed certificate for YOUR_DOMAIN to /etc/nginx/.../rustdesk.conf`。
原因可能是 Certbot 沒有找到 `rustdesk.conf` 文件，您可以嘗試以下解決方案之一：
- 檢查步驟 5 的結果，運行 `sudo service nginx restart`。
- 將包含 `<YOUR_DOMAIN>` 的服務器配置 `server{...}` 復制到 `rustdesk.conf`，並將 `location{...}` 更改為以下內容。
- 將包含 `YOUR_DOMAIN` 的服務器配置 `server{...}` 復制到 `rustdesk.conf`，並將 `location{...}` 更改為以下內容。
```sh
location / {
@ -348,7 +348,7 @@ location / {
* `too many certificates (5) already issued for this exact set of domains in the last 168 hours`
解決方案：向 DNS 添加另一個域名並將 `<YOUR_DOMAIN>` 更改為它，例如 `rustdesk2.example.com`。然後重複步驟 1、4、6。
解決方案：向 DNS 添加另一個域名並將 `YOUR_DOMAIN` 更改為它，例如 `rustdesk2.example.com`。然後重複步驟 1、4、6。
* `Error getting validation data`
@ -357,12 +357,12 @@ location / {
注意：如果您手動更改 `rustdesk.conf`，請運行 `sudo service nginx restart`。
### 7. 登錄到網頁
* 在瀏覽器中打開 `https://<YOUR_DOMAIN>`，使用默認用戶名 "admin" 和密碼 "test1234" 登錄，然後將密碼更改為您自己的。
* 在瀏覽器中打開 `https://YOUR_DOMAIN`，使用默認用戶名 "admin" 和密碼 "test1234" 登錄，然後將密碼更改為您自己的。
### 8. 為 ID 服務器和中繼服務器添加 WebSocket Secure (WSS) 支持，以啟用所有平台的安全通信。
將以下配置添加到 `/etc/nginx/.../rustdesk.conf` 文件的第一個 `server` 部分，然後重啟 `Nginx` 服務。
Web 客戶端可以通過 `https://<YOUR_DOMAIN>/web` 訪問。自定義客戶端可以通過在高級選項中設置 `allow-websocket=Y` 來使用 WebSocket。如果使用啟用 WebSocket 的自定義客戶端，它將不會使用 TCP/UDP，只能通過中繼連接（直接 IP 連接除外）。如果只使用這種啟用 WebSocket 的客戶端，服務器可以關閉端口 21114 到 21119，只保持端口 443 開放。
Web 客戶端可以通過 `https://YOUR_DOMAIN/web` 訪問。自定義客戶端可以通過在高級選項中設置 `allow-websocket=Y` 來使用 WebSocket。如果使用啟用 WebSocket 的自定義客戶端，它將不會使用 TCP/UDP，只能通過中繼連接（直接 IP 連接除外）。如果只使用這種啟用 WebSocket 的客戶端，服務器可以關閉端口 21114 到 21119，只保持端口 443 開放。
```
location /ws/id {
@ -394,7 +394,7 @@ Web 客戶端可以通過 `https://<YOUR_DOMAIN>/web` 訪問。自定義客戶
```
server {
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@ -426,18 +426,18 @@ server {
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/YOUR_DOMAIN/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/YOUR_DOMAIN/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = <YOUR_DOMAIN>) {
if ($host = YOUR_DOMAIN) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name <YOUR_DOMAIN>;
server_name YOUR_DOMAIN;
listen 80;
return 404; # managed by Certbot
}