search

diameter / rtorrent-rutorrent

Docker container with supervisor/rtorrent/nginx/ruTorrent 64/32 bit
155 stars 72 forks source link

Unable to connect on Ubuntu 16.04 x64 #26

Open sipe opened 8 years ago

sipe commented 8 years ago

Hello, I'm trying your docker image on Ubuntu 16.04 My server is running Ubuntu 16.04 x64 on i5-2400.

When I run your script and try to connect to IP, I get unable to connect. I tried with http://ip, http://ip:80, tried secure option with https://ip, https://ip:443, tried with latest, 64, 64-latest and same result.

Commands that I used for running are from github page.

Docker version Docker version 1.11.2, build b9f10c9

Container running CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ad9a4e564132 diameter/rtorrent-rutorrent:64-latest "supervisord" 38 seconds ago Up 37 seconds 80/tcp, 0.0.0.0:443->443/tcp, 49160/tcp, 0.0.0.0:49161->49161/tcp, 0.0.0.0:49160->49160/udp rtorrent2

Container output when starting root@host:/tmp# docker run -t --name rtorrent2 -p 443:443 -p 49160:49160/udp -p 49161:49161 -v ~/test:/downloads diameter/rtorrent-rutorrent:64-latest /usr/lib/python2.7/dist-packages/supervisor/options.py:295: 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 ' 2016-07-19 13:51:43,205 CRIT Supervisor running as root (no user in config file) 2016-07-19 13:51:43,205 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2016-07-19 13:51:43,228 INFO RPC interface 'supervisor' initialized 2016-07-19 13:51:43,228 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2016-07-19 13:51:43,228 INFO supervisord started with pid 1 2016-07-19 13:51:44,230 INFO spawned: 'nginx' with pid 8 2016-07-19 13:51:44,231 INFO spawned: 'rtorrent' with pid 9 2016-07-19 13:51:44,233 INFO spawned: 'php5-fpm' with pid 10 2016-07-19 13:51:45,743 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-07-19 13:51:45,743 INFO success: rtorrent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-07-19 13:51:45,743 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

If you need more info I will provide.

ghost commented 7 years ago

@sipe It looks like your container is using the default Docker bridge for its networking. If you do a docker inspect <container-name-or-id> and look for the networking block it should confirm that. You should be able to fix it by removing the container and redeploying with the --network=host parameter, making sure that nothing else on your Docker host is using 80/443 as its ports.