Remzona54/Remnawave_Panel
1
0
Fork 0
mirror of https://github.com/remnawave/panel.git synced 2026-10-22 03:32:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update remnawave-node.md

Browse source
This commit is contained in:
PentiumB 2025-07-24 12:30:57 +05:00 • committed by GitHub
parent 6114fcbe4b
commit 2dcfe5dae4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/install/remnawave-node.md
View file

@ -71,7 +71,7 @@ docker compose up -d && docker compose logs -f -t
:::info
WARNING!
1. This manual does not contain mandatory instructions, it is only an example of implementation without reference to the file `zapret.dat` used in it. In your implementation, it will not be appropriate to blindly repeat the call ext:zapret.dat:zapret, since in reality the categories `:zapret` will be different. If you blindly, without understanding what is happening, repeat what is described, you will break your Xray configuration and get an error connecting to the node.
1. This manual does not contain mandatory instructions, it is only an example of implementation without reference to the file `*-zapret.dat` used in it. In your implementation, it will not be appropriate to blindly repeat the call ext:*-zapret.dat:zapret, since in reality the categories `:zapret` will be different. If you blindly, without understanding what is happening, repeat what is described, you will break your Xray configuration and get an error connecting to the node.
2. If you imagine that you will configure this routing on your server, and this will mean that client connections will be guided by this routing - you are mistaken.
For example: If you configure so that the sites of your country go directly from your Internet (Direct). This will not mean that the client application will work this way, the client routing is responsible for this.