Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No connection to rTorrent #73

Open
paulens12 opened this issue Nov 2, 2019 · 4 comments
Open

No connection to rTorrent #73

paulens12 opened this issue Nov 2, 2019 · 4 comments

Comments

@paulens12
Copy link

paulens12 commented Nov 2, 2019

I'm getting this error in rutorrent log:
No connection to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file.
Here's the docker log:

/usr/lib/python2.7/site-packages/supervisor/options.py:461: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2019-11-02 14:33:25,720 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2019-11-02 14:33:25,729 CRIT Server 'unix_http_server' running without any HTTP authentication checking
/usr/lib/python2.7/site-packages/supervisor/options.py:461: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2019-11-02 14:34:25,400 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2019-11-02 14:34:25,409 CRIT Server 'unix_http_server' running without any HTTP authentication checking

I'm running this on OpenMediaVault through the Docker plugin

@decantur
Copy link

decantur commented Nov 2, 2019

How are you mapping your ports?
I think you may want something like this:

0.0.0.0:5000=>5000/tcp
0.0.0.0:49161=>49161/tcp
0.0.0.0:7878=>80/tcp

5000 is the scgi port that rutorrent uses to communicate with rtorrent. Also, remapping port 80 is required as it conflicts with the OMV management port (you have probably done this already).

@paulens12
Copy link
Author

Hmm, well I hadn't mapped port 5000 because it's not exposed by the docker image.
I just tried mapping it, but that didn't help. Here are my current port mappings:
0.0.0.0:444->443/tcp
49160/tcp (unmapped)
0.0.0.0:51413->49161/tcp
0.0.0.0:5000->5000/tcp
0.0.0.0:180->80/tcp

@decantur
Copy link

decantur commented Nov 2, 2019

Sorry - thought that might help based on the rutorrent log message.

I am out of ideas other than maybe check the OMV forums for help or look at a different image for clues.

@arebokert
Copy link

I am having this issue however it started happening recently. I haven't changed any settings and rutorrent can connect for a while after container is started but after an hour or so it can no longer connect unless I restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants