Skip to content

docs: add warnings about IP address and self-signed certificate limitations #7693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tjaadvd wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add warnings about IP address and self-signed certificate limitations #7693

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions local-instance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,10 @@
# Local instance

> [!WARNING]
> AIO requires a **real domain name** and a **valid TLS certificate** to function correctly.
Copy link
Copy Markdown
Member

@pabzm pabzm Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. "real domain name" is not very precise, our requirement is "publicly resolveable domain" (or hostname). That's not as catchy, if you can think of another wording, please let me know. But please replace "real".
  2. Technically a self-signed certificate is also valid. You (probably) correctly mean a publicly verifiable certificate (issued by a well-known, public certificate authority), so please change the phrase accordingly.

Copy link
Copy Markdown
Author

@tjaadvd tjaadvd Mar 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

I'm having trouble coming up with the correct text. What do you think about this?

# Local instance

> [!WARNING]
> AIO requires a **publicly resolvable domain** and a **publicly verifiable certificate** (issued by a well-known, public certification authority).

> Accessing Nextcloud via a plain IP address or a self-signed certificate is **not supported**.
Copy link
Copy Markdown
Member

@pabzm pabzm Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using a local CA is also unsupported.

Copy link
Copy Markdown
Author

@tjaadvd tjaadvd Mar 28, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about this?

Accessing Nextcloud via a **plain IP address**, a **self-signed certificate**, or a **certificate from a local certificate authority (CA)** is **not supported**.

> The options below describe how to satisfy these requirements while keeping Nextcloud local.

It is possible due to several reasons that you do not want or cannot open Nextcloud to the public internet. Perhaps you were hoping to access AIO directly from an `ip.add.r.ess` (unsupported) or without a valid domain. However, AIO requires a valid certificate to work correctly. Below is discussed how you can achieve both: Having a valid certificate for Nextcloud and only using it locally.

### Content
Expand Down
4 changes: 4 additions & 0 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,10 @@ The steps below are written for Linux. For platform-specific guidance see:
> [!IMPORTANT]
> These instructions assume there is no existing web server or reverse proxy (for example Apache, Nginx, Caddy, or Cloudflare Tunnel) that you intend to place in front of AIO. If you plan to run AIO behind an existing web server or reverse proxy, follow the AIO reverse proxy documentation: [Reverse proxy docs](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md)

> [!WARNING]
> AIO does **not** support IP addresses or self-signed certificates for the Nextcloud domain.
> If you want a local-only instance, see [local-instance.md](./local-instance.md) before proceeding.

You're encouraged to skim the attached [FAQ](#faq). While we've tried to make things straightforward, Nextcloud is a large and flexible platform. Reading the FAQ will save you time, particularly if edge cases come up.

> [!TIP]
Expand Down