Chickweed Posted March 20, 2020 Share Posted March 20, 2020 Hi , i installed a docker qbittorent container , but i haven't acces on this container with this ip 192.168.1.77:8080 how I can install qbittorent or another p2p client on docker, the installation goes well but when I want to access the web page, the connection is refused. I also installed plexmediaserver on a docker container it does the same thing Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 2 hours ago, Chickweed said: 192.168.1.77:8080 Are you entering that in your browser, or is that what results when you click on the icon for the docker and select WebUI? Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 (edited) Oui, j'ai entré l'adresse IP de qbittorrent dans mon navigateur, cette adresse 192.168.1.77:8080 est l'adresse de qbittorrent. when i select in the right click menu, webgui launches a web page and then it tells me that the connection has been refused Edited March 20, 2020 by Chickweed Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 2 minutes ago, Chickweed said: when i select in the right click menu Just to make sure there is no misunderstanding. There is no right-click menu from the Unraid webUI. Many browsers will present a menu if you right-click but that is not related to Unraid. Do you really mean you are doing the normal (left) click? Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 (edited) yes completely done I wanted to say left click it displays the context menu, I share a screenshot Edited March 20, 2020 by Chickweed Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 Your first screenshot shows that neither docker was running. Did you stop them or did they crash? Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 So actually I could download deluge as a p2p client for now, but I prefer qbittorrent or transmission. on the screenshot that I sent you, qbittorrent remains stopped, impossible to launch qbittorrent, when i click on start it launches and then re-extinguishes immediately. after for plex the connection is refused. Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 Mar 20 12:36:35 Tower vsftpd[13356]: [chris] FAIL LOGIN: Client "192.168.1.100" Mar 20 12:38:12 Tower kernel: docker0: port 1(veth3051ad3) entered blocking state Mar 20 12:38:12 Tower kernel: docker0: port 1(veth3051ad3) entered disabled state Mar 20 12:38:12 Tower kernel: device veth3051ad3 entered promiscuous mode Mar 20 12:38:12 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth3051ad3: link is not ready Mar 20 12:38:12 Tower kernel: docker0: port 1(veth3051ad3) entered blocking state Mar 20 12:38:12 Tower kernel: docker0: port 1(veth3051ad3) entered forwarding state Mar 20 12:38:12 Tower kernel: docker0: port 1(veth3051ad3) entered disabled state Mar 20 12:38:14 Tower kernel: eth0: renamed from vethd30ef78 Mar 20 12:38:14 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3051ad3: link becomes ready Mar 20 12:38:14 Tower kernel: docker0: port 1(veth3051ad3) entered blocking state Mar 20 12:38:14 Tower kernel: docker0: port 1(veth3051ad3) entered forwarding state Mar 20 12:38:16 Tower avahi-daemon[2061]: Joining mDNS multicast group on interface veth3051ad3.IPv6 with address fe80::4c64:2eff:fe16:cee6. Mar 20 12:38:16 Tower avahi-daemon[2061]: New relevant interface veth3051ad3.IPv6 for mDNS. Mar 20 12:38:16 Tower avahi-daemon[2061]: Registering new address record for fe80::4c64:2eff:fe16:cee6 on veth3051ad3.*. Mar 20 12:38:29 Tower vsftpd[15901]: connect from 192.168.1.100 (192.168.1.100) Mar 20 12:38:30 Tower vsftpd[15901]: [chris] OK LOGIN: Client "192.168.1.100" Mar 20 12:38:41 Tower vsftpd[16191]: connect from 192.168.1.100 (192.168.1.100) Mar 20 12:38:43 Tower vsftpd[16191]: [chris] OK LOGIN: Client "192.168.1.100" Mar 20 12:43:45 Tower vsftpd[16225]: [chris] OK UPLOAD: Client "192.168.1.100", "/mnt/user/isos/openmediavault_5.3.4-amd64.iso", 119459840 bytes, 720.15Kbyte/sec Mar 20 12:43:47 Tower vsftpd[23701]: connect from 192.168.1.100 (192.168.1.100) Mar 20 12:43:48 Tower vsftpd[23701]: [chris] OK LOGIN: Client "192.168.1.100" Mar 20 12:43:50 Tower vsftpd[23726]: [chris] OK DELETE: Client "192.168.1.100", "/mnt/user/isos/openmediavault_5.3.4-amd64.iso" Mar 20 12:49:27 Tower kernel: docker0: port 2(veth020b9e7) entered blocking state Mar 20 12:49:27 Tower kernel: docker0: port 2(veth020b9e7) entered disabled state Mar 20 12:49:27 Tower kernel: device veth020b9e7 entered promiscuous mode Mar 20 12:49:27 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth020b9e7: link is not ready Mar 20 12:49:27 Tower kernel: docker0: port 2(veth020b9e7) entered blocking state Mar 20 12:49:27 Tower kernel: docker0: port 2(veth020b9e7) entered forwarding state Mar 20 12:49:27 Tower kernel: docker0: port 2(veth020b9e7) entered disabled state Mar 20 12:49:29 Tower kernel: eth0: renamed from veth4792e87 Mar 20 12:49:29 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth020b9e7: link becomes ready Mar 20 12:49:29 Tower kernel: docker0: port 2(veth020b9e7) entered blocking state Mar 20 12:49:29 Tower kernel: docker0: port 2(veth020b9e7) entered forwarding state Mar 20 12:49:31 Tower kernel: veth4792e87: renamed from eth0 Mar 20 12:49:31 Tower kernel: docker0: port 2(veth020b9e7) entered disabled state Mar 20 12:49:31 Tower kernel: docker0: port 2(veth020b9e7) entered disabled state Mar 20 12:49:31 Tower kernel: device veth020b9e7 left promiscuous mode Mar 20 12:49:31 Tower kernel: docker0: port 2(veth020b9e7) entered disabled state Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 diagnostics done tower-diagnostics-20200320-2105.zip Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 I don't use qbittorrentvpn myself, being already familiar with transmission. One thing I notice in your screenshots though, is that your plex doesn't have any mapping for any of your media. That shouldn't really cause the connection refused, but it does mean plex wouldn't be able to access anything on your server even if it was running. Maybe we can try to work through setting up your plex docker correctly and go from there. Post your docker run command for plex as explained in this very first link in the Docker FAQ: Quote Link to comment
Chickweed Posted March 20, 2020 Author Share Posted March 20, 2020 I downloaded the transmission but there is an error, for the plex, it tells me that there is no user, it does not create it automatically? Quote Link to comment
trurl Posted March 20, 2020 Share Posted March 20, 2020 I actually asked for the docker run for plex. But I can see from the one you posted that you must not be doing anything right. It is even telling you what the problem is. Remove all your dockers. After you remove all your dockers, go read all of the Getting Started section of the Docker FAQ: https://forums.unraid.net/topic/57181-docker-faq/ After you have finished studying that, let us know and we will work on a single docker and see if you can get it setup correctly. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.