Nextcloud update

[ver151set]

I use a reverse proxy and a single certificate that covers all my subdomains

The default installation now uses https and causes too many redirect errors unless I disable https in nextcloud which is fine for me as the proxy handles https anyway

My issue is the new nextcloud update changes the files in conf.d in a way I cant figure out how to disable https but it was pretty easy on previous versions so I had to roll back, gotta love snapshots

Anyone know a quick and easy way to get rid of the built in https the plugin dev has implemented on the new version? Also if so a way to make it persist through upgrades? TIA

 

[ddaenen1]

I have the same issue and no solution. I don't want the https and the letsencrypt certs as i have that already set up in pfsense with ACME and HAproxy. I upgraded the plugin from 21 to 23 today and cannot access nextcloud anymore due to too many redirects. Also had to rollback.

 

[ver151set]

I have the same issue and no solution. I don't want the https and the letsencrypt certs as i have that already set up in pfsense with ACME and HAproxy. I upgraded the plugin from 21 to 23 today and cannot access nextcloud anymore due to too many redirects. Also had to rollback.

Its a little work but what I ended up doing was installing Nextcloud via Danbs script and enabling the NO_CERT=1 option to disable ssl in caddy

Much more of a professional install and stays up to date. Dumped sql database from plugin and imported it into the new installation and moved files into the new nextcloud/files dataset

GitHub - danb35/freenas-iocage-nextcloud: Script to create an iocage jail on FreeNAS for the latest Nextcloud 28 release, including Caddy, MariaDB or PostgreSQL, and Let's Encrypt

Script to create an iocage jail on FreeNAS for the latest Nextcloud 28 release, including Caddy, MariaDB or PostgreSQL, and Let's Encrypt - danb35/freenas-iocage-nextcloud

github.com

 

[ddaenen1]

Well, i guess that will also be my long term solution. Still need to find out first how to dump and import the sql database as i don't have any experience with that. I must say, i rolled back twice and credits to TrueNAS as this feature makes a huge difference and saved me from doing a new install of NC and uploading all the files once again like i did the previous time.

 

[bmf7777]

I have the same issue and no solution. I don't want the https and the letsencrypt certs as i have that already set up in pfsense with ACME and HAproxy. I upgraded the plugin from 21 to 23 today and cannot access nextcloud anymore due to too many redirects. Also had to rollback.

i just started using truenas with nextcloud ... i already have a nextcloud instance on a intel nuc running ubuntu ... i too wanted to run nextcloud with http and host behind my haproxy ...
i have a few hosts that i pass through the https without decrypting for things like stunnel & openvpn etc ... see below for segment of haproxy .cfg
this haproxy runs on a ubuntu nuc with a pfsense router (XG-1537) forwarding all 443 to this proxy ... i don't think this script will run on haproxy on pfsense as i looked at it ... because the stream is first parsed for for sni prior to decrypt then cycled via another socket to decrypt using lets encrypt and sent to the device backend or server as http stream ... this seemed very difficult to do with the canned form pfsense has for haproxy (at least i couldn't figure it out and stuck with my haproxy which is working fine for many years)

frontend https
bind *:443
mode tcp
tcp-request inspect-delay 5s
tcp-request content accept if { req.ssl_hello_type 1 }
use_backend stunnel-openvpn-backend if { req.ssl_sni -i foo }
use_backend stunnel-synology-backend if { req.ssl_sni -i bar}
use_backend openvpn-synology-backend if { req.ssl_sni -i foobar}
use_backend truenas-nextcloud-backend if { req.ssl_sni -i nextcloud-blah-blah }
default_backend https-back

frontend https-front
bind 127.0.0.1:9001 ssl crt /etc/letsencrypt/live/blah-blah/haproxy.pem accept-proxy
mode http
use_backend home-assistant-backend if { ssl_fc_sni -i blah }
use_backend nextcloud-backend if { ssl_fc_sni -i blah-blah }
use_backend genmon-backend if { ssl_fc_sni -i blah-blah }
use_backend blueiris-backend if { ssl_fc_sni -i blah-blah }
use_backend password-pusher-backend if { ssl_fc_sni -i blah-blah }
use_backend ipswitch-backend if { ssl_fc_sni -i blah-bla }
use_backend haproxy-backend if { ssl_fc_sni -i blah-blah }


frontend http
bind *:80
acl letsencrypt-acl path_beg /.well-known/acme-challenge/
use_backend letsencrypt-backend if letsencrypt-acl

backend letsencrypt-backend
server letsencrypt 127.0.0.1:8888

backend https-back
mode tcp
server https-front 127.0.0.1:9001 send-proxy-v2

...