uncle_BSteve

Hi Folks I'm new to Nextcloud. I've installed successfully and presides behind Nginx Proxy Manager official. I do not have ports forward from router; I use it for convenience only. Nginx proxies from https to http, per recommendation. It seems to work fine. Now I'm trying to add a caldav account to my iphone, but can't get it to work. I use the domain name which works when accessing the webui. https://nextcloud.mydomain.cc/ and the same credentials as I use for my nextcloud account. I receive: "Cannot Connect Using SSL Do you want to try setting up the account without SSL?" BTW, I use a wild card certificate from Lets Encrypt. Everything else seems to work fine ie photos and videos are syncing great. I am rather novice with Nginix Proxy Manager, and proxies in general. My guess is it's something to do with that. Also, I/ve read on forums that SSL is required for my recent version of ios. Would someone please be able to help me configure this? It is one feature I was definitely planning to use. Thanks

Hi. That makes sense given how easy everything was in bridge mode. It's just I can't get nginx proxy manager to work on bridge. The overall object for me is to have qbittorrentvpn/*arrs etc behind NPM. It all worked easily on br0 ewxcept qbittorrentvpn. Damm! I've now connected a second custom bridge to NPM, the same custom bridge I have qbittorrentvpn on. I can curl qbittorrentvpn from the NPM console and works. So my-net is custom bridge... it's subnet = 172.18.0.0/16. qbittorrent running on my-net (assigned ip of 172.18.0.6 and I can access its webui through 192.168.20.21:8080 (unraid host ip). NPM is on br0 and assigned ip of 192.168.20.51. I thought i could point a proxy host to http:172.18.0.6:8080 but no go, despite being able to curl 172.18.0.6:8080 from NPM console. Has anyone got any suggestions... or tutorials etc? I just need qbittorrent to be accessible to *arrs and be behind NPM. Thanks in advance.

Another thing I've noticed. I was digging around in router and noticed that the unraid host and the qbittorrentvpn container appear as different ips with the same mac address. That wouldn't explain why it works when vpn disabled, but thought could be another clue. Thanks in advance. Desperate to get torrents working again. Thanks

)-: I spoke way too early. So I have all my containers on br0 with ip address assigned manually, outside dhcp pool but within subnet. All containers are working except qbittorrentvpn. When vpn disabled, I can access webui. But when enabled, no go. All template settings are identical to what they were when I used bridge mode (and everything worked great). I entered the console of another contained and entered curl http://192.168.20.61:8080 and received this: curl: (56) Recv failure: Connection reset by peer. Not sure why container is refusing connections to http://192.168.20.61:8080 ? Please help! docker-execution supervisord.log

I've managed to get working with a second instance of docker. All I can think that I did wrong with 1st instance was I had changed qbittorrent config settings prior to changing to br0 from bridge. If I comprehend anything new (I don't necessarily understand what's going on LOL) I will post for other's benefit.

Hi there. I'm trying to get qbittorrentvpn working on br0 rather than bridge mode. I'm using PIA with port forwarding. Everything was working when I used bridge network. I need to assign an ip to the container hence why I want to use br0. Docker starts and seems to connect to vpn, and port forwarding seems ok. But can't access webui at http://ip:8080. Please help! docker-execution supervisord.log

wgstarks Thank you! You saved me from pulling rest of my hair out. It works.Cheers heaps

Hi. I've been using qbittorrentvpn for several months and it works great. I've recently purchased a PIA subscription and have been trying since to get an incoming port. Anything I try seems to result in the following log entry: [info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment. I haven't opened any port on router; could this be an issue? Note I've tried over a dozen server locations, but no luck. I keep checking the logs for clues, but only get the above entry. Please help! It's almost certainly something I'm doing wrong given I'm noob at this vpn stuff. Thanks problem_PIA_port_in supervisord.log