April 6, 201511 yr unRAID OS Version: 6.0-beta14b Description: It seems that when a docker container is added, removed and then re-added...I can't access the webgui for that container. I just had this problem with this repo that I got from a template: https://registry.hub.docker.com/u/binhex/arch-delugevpn/ . I experienced this problem before, but I was able to work around it by using another container that had the same software (in that case it was plex. In this case what I did was I installed the Deluge container, but then I want to use the Deluge + VPN container. The deluge gui was working fine before stopping it and deleting it. But then I started getting the "This webpage is not available" error message after installing Deluge + VPN. How to reproduce: Install a container. Verify webgui works. Stop and delete container. Re-add the same container. You should get the "This webpage is not available" error. My gut feeling here is that there is some kind of conflict with the ports. But I'm really not sure what is going on. Any ideas in how I can fix?
April 7, 201511 yr unRAID OS Version: 6.0-beta14b Description: It seems that when a docker container is added, removed and then re-added...I can't access the webgui for that container. I just had this problem with this repo that I got from a template: https://registry.hub.docker.com/u/binhex/arch-delugevpn/ . I experienced this problem before, but I was able to work around it by using another container that had the same software (in that case it was plex. In this case what I did was I installed the Deluge container, but then I want to use the Deluge + VPN container. The deluge gui was working fine before stopping it and deleting it. But then I started getting the "This webpage is not available" error message after installing Deluge + VPN. How to reproduce: Install a container. Verify webgui works. Stop and delete container. Re-add the same container. You should get the "This webpage is not available" error. My gut feeling here is that there is some kind of conflict with the ports. But I'm really not sure what is going on. Any ideas in how I can fix? Did you try clicking the "log" for the container on the Docker page?
April 7, 201511 yr Author Yes, I did. Here is the log entry: /usr/bin/docker logs --tail=350 -f binhex-delugevpn 2>&1 2015-04-08 11:04:19,144 CRIT Set uid to user 0 2015-04-08 11:04:19,144 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2015-04-08 11:04:19,146 INFO supervisord started with pid 1 2015-04-08 11:04:20,148 INFO spawned: 'deluge' with pid 8 2015-04-08 11:04:20,148 INFO spawned: 'setip' with pid 9 2015-04-08 11:04:20,149 INFO spawned: 'start' with pid 10 2015-04-08 11:04:20,149 INFO spawned: 'webui' with pid 11 2015-04-08 11:04:20,150 INFO spawned: 'privoxy' with pid 12 2015-04-08 11:04:20,151 INFO spawned: 'setport' with pid 13 2015-04-08 11:04:20,163 DEBG 'start' stdout output: [info] VPN provider defined as custom 2015-04-08 11:04:20,163 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-04-08 11:04:20,163 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-04-08 11:04:20,163 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-04-08 11:04:20,163 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-04-08 11:04:20,163 DEBG 'start' stdout output: [crit] VPN provider defined as custom, no files with an ovpn extension exist in /config/openvpn/ please create and restart delugevpn 2015-04-08 11:04:20,163 DEBG fd 15 closed, stopped monitoring (stdout)> 2015-04-08 11:04:20,163 DEBG fd 19 closed, stopped monitoring (stderr)> 2015-04-08 11:04:20,163 INFO exited: start (exit status 1; not expected) 2015-04-08 11:04:20,163 DEBG received SIGCLD indicating a child quit 2015-04-08 11:04:21,164 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-04-08 11:04:21,164 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) I did put the ovpn file in the /config/openvpn directory and that seems to make that error go away and I think it is able to connect to the vpn. However, the deluge admin page does not load for me. When I install a deluge docker separate from this repo, it comes up without a problem. I noticed that in this case though, there aren't any config files in the config repo. I'm starting to think this might be an issue with the repo I am using? I posted a new issue on that repo page: https://github.com/binhex/arch-delugevpn/issues/3 I tried creating the docker via the command and the same thing happens. Could this be a file permission issue with the config files not being written? Any direction to help me debug this would be helpful.
Archived
This topic is now archived and is closed to further replies.