How to make AIO work with self-signed certificate?

Hello, actually the question is quite relevant. I faced the same problem.

I made self-signed certificates (because that’s what I want), set up a reverse proxy on Nginx, made the necessary security settings on the virtual machine where it runs, made a separate dedicated subnet in Docker to which only the Nginx server from this machine has access. I’m not even talking about global security protection in the local network.

And now after all this I am facing the problem Domaincheck container is not running
which I can’t get around in any adequate way. I wanted to make my own private cloud to be used the way I want, without playing along with your security requirements. I’m glad you’re trying to make the environment secure, but there must be a way to make the installation ‘unsafe’ in your vision. I spent 4 days of my life to come here and see that SKIP_DOMAIN_VALIDATION does not work, and you need to do it as written in your instructions. Why? Your instructions do not suit me; they are not relevant for me.

What should I do now?

Hi, see GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

Hmm, there was no need to separate the topic. After all, the essence of my answer in that topic was specifically about Domaincheck container is not running.

In a nutshell, it would be great to make an env parameter that specifically makes the installation ‘unsafe’.

It will disable domain verification and certificate verification.

Have you read my link?

nwm, аpparently we don’t hear each other, I’m talking about round and you’re talking about warm. Question closed, thank you for your time.

1 Like

I have linked to this section in the readme:

It is indeed the thing you were asking for iirc

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.