docker-nextcloud VS Transmission

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"

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Grab this file. Install Transmission on Mac or Deluge on Win. Optional: run a VPN if you're in the US(mostly) and worried about your ISP sending you a cease-and-desist notice. Open the file using the app you installed. Wait. It should start within a minute or two and download progress will be seen. Speed depends on how many people are sharing it. Any issues, let me know.

Why "NO TORRENT"? Just get TransmissionBT and torrent whatever you want

Its intresting you mention that, before reading your reply I went and created a post in the Q n A section, asking for help about this very thing and I linked to the same GitHub issue you linked to here. I have yet to get a reply lol.here

transmission can run as a headless server with a web gui

Get a VPN like Windscribe(set windscribe firewall to on instead of auto), forward your port via their website. Use a good torrent client like https://transmissionbt.com/ set that port in the options, and add a blocklist https://github.com/Naunter/BT\_BlockLists/raw/master/bt\_blocklists.gz