Nextcloud AIO's Mastercontainer certificate on 8080 not valid

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 20.0.5): 24.0.7 on NC AIO 3.0
Operating system and version (eg, Ubuntu 20.04): Ubuntu 22.04 - Linux 5.15.0-52-generic x86_64
Apache or nginx version (eg, Apache 2.4.25): AIO container (apache?)
PHP version (eg, 7.4): 8.0.25

The issue you are facing:

Invalid SSL Certificate → Brave’s Security Exception when loading the AIO interface.

I can load it on Firefox but not on Brave :frowning:

Is this the first time you’ve seen this error? (Y/N): N

Steps to replicate it:

  1. Open your NC instance in Brave Browser
  2. Go to Admin settings
  3. CLick on “Open AIO interface”
2

Port 8080 uses a self-signed certificate by default. So this is expected. You simply need to let the browser accept this.

3

Well, Brave does not allow this for now.
It barely allows self-signed certificates on https://localhost
I wrote on their github, but I’m curious why the certificate is valid for the NC instance but not the AIO admin pane? Or is it because I chose 8080? Is there a way to host both on the same port?
Thanks.

4

I am using brave and able to trust self-signed certificates.

The mastercontainer is completely independent from the other containers. They dont have access to the mastercontainers files and the other way around. So there is no way to reuse the certficiate for the mastercontainer. However you could open port 80 and 8443 and use https://yourdomain.com:8443 to access the AIO interface with a valid certificate.

5

How can I trust self-signed certificates in Brave?

6

Maybe like this? Can't connect to site with self signed certificate - #2 by fanboynz - Desktop Support - Brave Community

7

Thanks.
Well, this link does not provide an answer. I face the same problem as the OP.

8

Can you post a screenshot of that here?

9

Also, can you try this workaround?
https://support.google.com/chrome/thread/10551759?hl=en&msgid=59258560

10

Actually, everything works perfectly fine when I use the 8443 port instead of the 8080 (At least after rolling back to stable 2.1.2 AIO).

So I believe it would be nice that the link to the AIO interface from within the Administration panel of the NC instance would point to 8443 and not 8080.

image

11

See GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.