Hi. This problem may appear on some browsers like Firefox. This tells you that the destination IP address hasn’t a certification and may be dangerous. Now, if the IP is in your local network and it is safe from external accesses, you should be able to give your consent and move to the next page. Also consider that some browsers (like, for example, Chrome/ium if I remember correctly) give you a less invasive warning and bring you directly to the following page. To fix this, you can install a certificate. You can search my blog to install let’s encrypt (if your Owncloud is exposed to Internet and has a public IP) or you can install a self signed certificate (also this covered by my blog). Hope this can help you

Try accessing the container (docker execute-it owncloud bash) and applying the following:
https://doc.owncloud.com/server/next/admin_manual/installation/changing_the_web_route.html
It’s not the best way with Docker (you should use docker-compose and enable a reverse proxy behind your docker container) but it could be the faster way

Hi peppe80,

Thanks for the input. I’ll see if I can post what I documented when troubleshooting. I do have a quick question; could you tell me how to connect my owncloud container to my DDNS that I created from your No-IP tutorial so that I may remotely control owncloud from anywhere outside my home LAN where it is set up? Right now I am trying to get this up and running and not just have owncloud accessible from my home network. I know you briefly touched upon it here, and I have already set up port forwarding on my router to have my RPI be accessible from port 8080, but I’d like to know the specific steps. Perhaps we’d need to go into the owncloud container’s hostconfig.json or its config.v2.json file to add my DDNS name to it, but if you could answer my question here that would be awesome.

Thanks for the input. I’ll see if I can post what I documented when troubleshooting. I do have a quick question; could you tell me how to connect my owncloud container to my DDNS that I created from your No-IP tutorial so that I may remotely control owncloud from anywhere outside my home LAN where it is set up? Right now I am trying to get this up and running and not just have owncloud accessible from my home network. I know you briefly touched upon it here, and I have already set up port forwarding on my router to have my RPI be accessible from port 8080, but I’d like to know the specific steps. Perhaps we’d need to go into the owncloud container’s hostconfig.json or its config.v2.json file to add my DDNS name to it, but if you could answer my question here that would be awesome.

Hi Jack,
sure it can be done. But please give me more time to:
-> reproduce the issue (with Raspberry PI OS 32-bit), by identifying what are the errors that people must check before using that fix
-> test the solution
-> write down the solution

Any help in these steps to speed up the process would be welcome 😉

Thank you so so so much for including this! I highly recommend placing jav’s comment in the article for those like me who struggled with this issue.

Hi Jav, thank you for your feedback. This tutorial is based on official Raspberry PI OS 64-bit, but any suggestion shared for other readers is welcome

Had same problem with the container failing after the cron entries, using RPI 3 32bit (MXlinux build)

Found solution here: https://github.com/owncloud-docker/server/issues/219
But you need to find the latest file at the ftp site is now
http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1~bpo10+1_armhf.deb

What RPI model are you using? Your operating system is Raspbian or Raspberry PI OS?