You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
I setup this docker container for the first time today and I am running into some errors. This is also the first time I am using rtorrent/rutorrent so I don't know my way around them yet.
Issues
When I open the web UI I get the following error:
[06.06.2022 14:39:38] WebUI started.
[06.06.2022 14:39:39] Bad response from server: (500 [error,getplugins]) Internal Server Error
[06.06.2022 14:39:47] JS error: [https://<LAN IP>:9080/js/webui.js : 776] TypeError: this.systemInfo is undefined
Another issue I had was that the container was not starting with any PUID and PGID other than 0.
Logs
Before getting the logs, I cleared the config folder and only kept the wireguard/wg0.conf file.
I'm having the same issue with the following error:
[error] 866#866: *1 FastCGI sent in stderr: "PHP message: PHP Warning: require_once(/usr/share/webapps/rutorrent/conf/config.php): Failed to open stream: Permission denied in /usr/share/webapps/rutorrent/php/util.php on line 785PHP message: PHP Fatal error: Uncaught Error: Failed opening required '/usr/share/webapps/rutorrent/conf/config.php' (include_path='.:') in /usr/share/webapps/rutorrent/php/util.php:785
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I setup this docker container for the first time today and I am running into some errors. This is also the first time I am using rtorrent/rutorrent so I don't know my way around them yet.
Issues
Logs
Before getting the logs, I cleared the config folder and only kept the
wireguard/wg0.conf
file.Issue 1. The supervisord.log is here: https://pastebin.com/uTzk9KS3
Issue 2. The supervisord.log is here: https://pastebin.com/AR2u57Nh
Docker Compose file
The text was updated successfully, but these errors were encountered: