ivan-pinatti / docker-torrent-box-with-vpn Goto Github PK

Hi,
I currently have 1 20TB Share mounted to the /media folder.
How is it possible to add another share to be used by the containers?

Describe the Feature

Support the use of Prowlarr as a meta-indexer instead of/in addition to Jackett.

Expected Behavior

The docker stack would include a pre-configured Prowlarr configuration which can be used in place of, or with Jackett.

Use Case

Prowlarr works better with the *arr indexers and requires less configuration than Jackett.

Describe Ideal Solution

It would be great if one/both of Prowlarr and Jackett could be run, with the unused one uninstalled and any config settings removed/commented out.

Alternatives Considered

Installing Prowlarr manually and removing Jackett and any configuration files.

Additional Context

Haven't really used this docker configuration yet, so I might be missing something :)

Describe the Bug

LazyLibrarian has an extra Docker layer (through Docker Mods) due to Calibre/FFMPEG and this requires additional downloading of packages. However, on the first run the ProtonVPN is still loading and connecting, therefore, the connection is not fully operational, resulting for the LazyLibrarian container to get stuck.

Expected Behavior

LazyLibrarian should add the Docker Mods without problems and load normally afterwards.

Steps to Reproduce

1. Download repo
2. Follow instructions in README
3. Check LL on the logs though docker logs -f lazylibrarian
4. See error

Environment (please complete the following information):

Linux Ubuntu

Describe the Bug

After running docker compose all containers are up but after 20-30 mins, all web ui fail to load (Sonarr ,Radarr, Qbit) mainly these three stop responding as in they dont load.
using protonVPN and Configured Correctly, tried the logs but nothing there to show me what could be, it's like the containers connected to the protonVPN network service are crashing/timing out, it just happened

Expected Behavior

they shouldn't crash

Steps to Reproduce

for me i just run the docker compose and it happens after some time

Screenshots

Logs of proton VPN Container

all containers are still running

this is what is showing

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

Linux Kubuntu
Docker version 20.10.23, build 7155243

Additional Context

the only way for the web ui to come back online is to docker compose down the containers and up them again while keeping ProtonVPN Running

Describe the Feature

The current implementation is using the network_mode: service:protonvpn method. However, this method actually shares the network from the ProtonVPN container. It does not route the other containers through it. Therefore, if the container is not connected to the VPN, the other containers will continue to access the Internet without the tunnel.

Expected Behavior

The proper way to implement it is to have the other containers being routed through the VPN container and only through the VPN tunnel. If the VPN tunnel is down, no packet to the outside world is transferred.

Use Case

Guarantee 100% that no packets are sent to the Internet without being encrypted/obfuscated by the VPN tunnel.

Describe Ideal Solution

ProtonVPN container routes the packets only through the VPN Tunnel

Describe the Bug

nzbget error with unpack.
Downloading the file works flawlessly. Files are in the directory.
The unpack does not work. It always fails.

Expected Behavior

After download, unpack and move to downloaded folder.

Steps to Reproduce

Steps to reproduce the behavior:
/

Screenshots

/

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• OS: Ubuntu Server 20.04. LTS

Additional Context

/

I am getting this error in my nordvpn docker log.

[custom-init] No custom files found, skipping... services-up: info: copying legacy longrun nordvpn (no readiness notification) [ls.io-init] done. FATAL: iptables is not functional. Ensure your container config adds --cap-add=NET_ADMIN,NET_RAW --- Due to errors, routing has been disabled ---

I am not able to access any of the services using reverse proxy or direct port access.
I have the options added.

HostConfig CapAdd 0 NET_ADMIN 1 NET_RAW

Describe the scenario

Can not access apps or nginx https from external ip

What is your question?

Hi i can seem to access anything on a external network, i have installed this on a dedicated server and dont have access to desktop, i am using protonvpn wireguard and the protonvpn docker says its connected to wireguard but i dont get any pages

Describe the Feature

When a PR is approved, generate a new release with release notes automatically.

Expected Behavior

Merged PRs generate new releases.

Use Case

When there is a contribution to code, after the PR approval a new release is published so users can updated it.

Describe Ideal Solution

GHA using templates readily available on the Internet.

Alternatives Considered

For now, manual publish releases.

Describe the Feature

Add a reverse proxy with strong authentication methods to be able to expose the services to the Internet.

Expected Behavior

Expose to the Internet with strong security features

Use Case

Some users/people might want to expose their app stack to the Internet. However, most of the apps lack strong security features, therefore, another method for exposing it is required.

Describe Ideal Solution

Nginx, Apache, or some other reverse proxy with if possible a 2-step verification method.

Alternatives Considered

Having an inbound VPN container exposed to access the services internally within the Docker network.

Hi!

I have several docker containers installed and some ports including 8080 are already taken. But when I tried to change them in docker-compose:

  - 8084:8084 # calibre
  - 8085:8085 # calibre-web (from calibre)
  - 8086:8086 # qbittorrent
  - 8088:8088 # calibre-web (from calibre-web container)

My home network 192.168.1.0/24
./configs/protonvpn/.env
PROTONVPN_EXCLUDE_CIDRS=192.168.0.0/24

None of them were available.

All ports are accessible through the protonvpn network

Port configuration (from portainer)

0.0.0.0:8084 8084/tcp
:::8084 8084/tcp
0.0.0.0:8085 8085/tcp
:::8085 8085/tcp
0.0.0.0:8086 8086/tcp
:::8086 8086/tcp
0.0.0.0:8088 8088/tcp
:::8088 8088/tcp

Tell me please how to correctly forward ports from containers?
Thanks/

Describe the scenario

With the >7 releases of protonvpn there are some breaking changes.
Do you think you can integrate it?

Describe the Feature

Have a script that can backup the config files and update the codebase without loosing custom configs and databases.

Expected Behavior

One command to update codebase and maintain current configurations/databases.

Use Case

When there is a newer version, users are able to update it without losing anything.

Describe Ideal Solution

A command like make update would suffice.

Alternatives Considered

Adding Taskfile instead of Makefile