docker-jackett VS docker-nextcloud

I can't get this container to launch, in the logs the access error in repeatedly printed:

Where did you get the docker-compose.yml from? Post the link. Also, why are you not using the one from the linuxserver if you are using their container? https://github.com/linuxserver/docker-jackett

So I'm running docker with portainer and I'm having issues getting the port number right. I set up my VPN in a container then I set up jackett and qBitTorrent. I want jackett and qBitTorrent to run through my VPN but I'm having issues with the port numbers jackett needs port 9117 and qBitTorrent needs 8080 how do I set my VPN up so they both go through it?

# https://github.com/linuxserver/docker-jackett jackett: container_name: jackett environment: PGID: $PLEX_PGID PUID: $PLEX_PUID TZ: $TZ image: lscr.io/linuxserver/jackett networks: smarthome: ipv4_address: 172.18.0.16 restart: always volumes: - $USERDIR2/jackett:/config

I always sort of assumed it was related to my set up, but it looks like some folks have had a similar problem with Jackett docker images on their own here. Gonna try the suggested alternative image and see if that helps.

https://github.com/linuxserver/docker-jackett/issues/72#issuecomment-468859532

I am trying to setup a Nextcloud Docker using the LSIO image(NC LSIO) as I need to have SMB/CIFS external storage support along with simplified docker-compose. I have also setup my own CA using the Step-CA ACME provisioner (Self CA using Step-CA) & use certbot on all my devices to generate the certs for all the devices & services as needed.

I did so that wasn't the solution. Found this which is similar to what you said to do, and I found out that half way through the steps it worked again but then when I went back to the latest public release it broke again. Returning to using nextcloud:24.0.6-ls204 fixed the issue so I guess I'm sticking with that from now on.

If you are running into this issue as of recent, you're probably also running NC with this container.

Since you're using the linuxserver.io docker container it should be very likely that someone else is or will be having the same problem. Like maybe this "[BUG] SMB in external storage doesn't work since the last update #303 " https://github.com/linuxserver/docker-nextcloud/issues/303

Issue

Seems that there is already an opened Bug for this one.

--- version: '3' services: app: # https://github.com/linuxserver/docker-nextcloud/releases image: lscr.io/linuxserver/nextcloud:${NEXTCLOUD_VERSION:-latest} container_name: nextcloud_app environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} volumes: - ${NEXTCLOUD_PATH}/config:/config - ${NEXTCLOUD_PATH}/data:/data - /etc/localtime:/etc/localtime:ro ports: - 3443:443/tcp # Can be commented out once cloudflare working security_opt: - no-new-privileges:true restart: unless-stopped depends_on: - mariadb - redis labels: - "com.centurylinklabs.watchtower.enable=true"