Common Issues
Deploying bots
Section titled “Deploying bots”If you are deploying bots, ensure that in bot’s env or config you’re using local mode. In that case you can simply enter http://remnawave:3000 to avoid problems with accessing panel.
Lost cookie-header to access the panel
Section titled “Lost cookie-header to access the panel”If you’ve lost cookie-header to access the panel, you can retrieve it by following these steps:
-
Navigate to the Remnawave directory
root@server: ~ cd /opt/remnawave -
Open the nginx configuration in a text editor:
root@server: ~ nano nginx.conf # or any other editor -
In the beginning, we encounter sections about cookie-paths to the panel:
nginx.conf map $arg_rEmnaprx $set_cookie_header {"aBCDefgh" "rEmnaprx=aBCDefgh; Path=/; HttpOnly; Secure; SameSite=Strict; Max-Age=31536000";default "";} -
Copy the value
rEmnaprx=aBCDefghfrom themapsection and use it as the cookie-path to the panel.Thus, the link will look like this:
https://domain.com/auth/login?rEmnaprx=aBCDefgh
Alias doesn’t work in my terminal
Section titled “Alias doesn’t work in my terminal”In case you’ve installed script in different terminal (e.g. bash) and now e.g. zsh can’t execute the rr command you need to:
-
Open zsh config (root or user or even both)
root@server: ~ nano ~/.zshroot@server: ~ nano /root/.zsh -
Add the following strings
root@server: ~ source /home/YOURUSERNAME/.bash_profileroot@server: ~ source /root/.bash_profile # or source /etc/bash.bashrc -
Restart your terminal or run the command
root@server: ~ exec zsh
Unlisted issue
Section titled “Unlisted issue”Feel free to report any related to our project issues in the GitHub repository or Telegram chat.
