Blackrain

I have upgrade Nextcloud to 16.0.1 and everything is working perfectly with the exception of when I do a security scan I see this below in my next cloud setting. The "Referrer-Policy" HTTP header is not set to "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" or "same-origin". This can leak referer information. I've read through the thread looking for solutions and modifying the ngix config on my letsencrypt reverse proxy but still getting the same thing. I get that it letsencrypt and nextcloud are adding the headers twice hence why I'm getting the issue during the security & setup scan. Anyone else getting this issue with the latest version of nextcloud?

Thanks for the quick reply but really didn't have a chance to download a later versions of the VMDK because I was on vacation. Since I have have time now I tried to download the latest VMDK that was posted on this thread and still the partition is only 100mb. You have a later version of the VMDK or will I have to go with the gparted route?

Hi all, Just wanted to know if there is a way to edit the pre-build vmdk file's partition size. At this point the new version 6.6.7 bizroot file is too big to fit in the 100meg partition the original poster put in. I tried to use some windows based partition editor to increase the partition size in windows but when I ran the vm I get an boot error. Any help would be greatly appreciated.

Ok since I finally got letsencrypts and Nextcloud working I want to move my owncloud files to the new nextcloud directory. When I do move them obviously nextcloud doesn't show the new files. I read about the occ command line and I can do something like occ files:scan command that would basically refresh the folders and show the files in nextcloud on my account. The issues I'm having is when I tried to run the command I get "sudo -u www-data php occ files:scan" in the docker CLI and all I get is unable to initialze policy plugin. Any advice would be appreciated.

I finally got got it working after so many hours. I have multiple dockers that were conflicting with letsencrypt after cleaning up it works like charm. Your documentation was great and help greatly.

I have owncloud and want to use nextcloud now but I'm having an issue on both dockers since my ssl certificate expired for my domain. I got it renewed but still have issues with ssl certs. I searched for quite awhile including these forums but it seems I'm at a stand still. At the moment I'm trying to use let's encrypt as it seem most people are using this in tandem nextcloud to secure their connection. I was able to get the certificate generated by let's encrypted but trying the test site it never comes up. I'll I get is this in the logs on restarting the service. Any help would be appreciated. | |___| (_) ___| / __| | |/ _ \ | \__ \ | | (_) ||_|___/ |_|\___/|_|Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0.[cont-init.d] 30-keygen: executing... generating self-signed keys in /config/keys, you can replace these with your own keys if required[cont-init.d] 30-keygen: exited 1.[cont-finish.d] executing container finish scripts...[cont-finish.d] done.[s6-finish] syncing disks.[s6-finish] sending all processes the TERM signal.[s6-finish] sending all processes the KILL signal and exiting.

I'm trying to update to 9.1.1 owncloud from the gui updater but I get this message. [GuzzleHttp\Ring\Exception\RingException] cURL error 60: SSL certificate problem: unable to get local issuer certificate I know how it has to do with the certificates but the resolution is with a straight install of owncloud and not a docker version. Anyone else have this issue? Any help would be appreciated.