Jump to content

Second docker image not reachable...


Recommended Posts

Hello all,

 

I am the whole afternoon/evening busy with getting a second image of the same docker template, binhex-qbittorrentvpn, up and running.

I did change all the standard ports to different ports, all folder associations also to new folders, but I still cannot reach my webUI.

 

Here are the template settings, adjusted by me:

 

firefox_y0jLw8zy3k_cropped.thumb.png.ae2abcdd3ba89b1c76bd6204a36fc940.png

 

firefox_YvXQjxgkna_cropped.thumb.png.c0d67a8b6c1059b68ba5e66049392505.png

 

firefox_ndUwZ9Y5Gl_cropped.thumb.png.20a79df3dcd11d21475da46553c5044a.png

 

firefox_ZnPCf2xxlB_cropped.thumb.png.a8a1a27fc26afa6f23acf7de85ed1e1d.png

 

The image is running, openvpn configuration files are supplied in the new folder, and the only thing that doesn't work is the webUI.
I put in <server-ip>:8811 as that is set to the new webUI port.
The docker log of that new image also says "[info] qBittorrent process listening on port 8811".

 

So what is it that I cannot reach the qBittorent webUI on above ip address and port.
FYI; the 1st docker image of qbittorrent does work like a charm...

 

Some help is much appreciated. Thanks!

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...