mirror of
https://github.com/nextcloud/all-in-one.git
synced 2025-01-31 01:48:24 +08:00
some more adjustments
Signed-off-by: Simon L. <szaimen@e.mail.de>
This commit is contained in:
parent
ac54fce522
commit
a07b3b8ccb
3 changed files with 6 additions and 4 deletions
|
@ -2,13 +2,13 @@
|
||||||
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.
|
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
|
### Content
|
||||||
- [1. Tailscale network](#1-tailscale-network)
|
- [1. Tailscale](#1-tailscale)
|
||||||
- [2. The normal way](#2-the-normal-way)
|
- [2. The normal way](#2-the-normal-way)
|
||||||
- [3. Use the ACME DNS-challenge](#3-use-the-acme-dns-challenge)
|
- [3. Use the ACME DNS-challenge](#3-use-the-acme-dns-challenge)
|
||||||
- [4. Use Cloudflare](#4-use-cloudflare)
|
- [4. Use Cloudflare](#4-use-cloudflare)
|
||||||
- [5. Buy a certificate and use that](#5-buy-a-certificate-and-use-that)
|
- [5. Buy a certificate and use that](#5-buy-a-certificate-and-use-that)
|
||||||
|
|
||||||
## 1. Tailscale network
|
## 1. Tailscale
|
||||||
This is the recommended way. For a reverse proxy example guide for Tailscale, see this guide by @flll: https://github.com/nextcloud/all-in-one/discussions/5439
|
This is the recommended way. For a reverse proxy example guide for Tailscale, see this guide by @flll: https://github.com/nextcloud/all-in-one/discussions/5439
|
||||||
|
|
||||||
## 2. The normal way
|
## 2. The normal way
|
||||||
|
|
|
@ -28,7 +28,7 @@ Included are:
|
||||||
- A+ security in Nextcloud security scan
|
- A+ security in Nextcloud security scan
|
||||||
- Ready to be used behind existing [Reverse proxies](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md)
|
- Ready to be used behind existing [Reverse proxies](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md)
|
||||||
- Can be used behind [Cloudflare Tunnel](https://github.com/nextcloud/all-in-one#how-to-run-nextcloud-behind-a-cloudflare-tunnel)
|
- Can be used behind [Cloudflare Tunnel](https://github.com/nextcloud/all-in-one#how-to-run-nextcloud-behind-a-cloudflare-tunnel)
|
||||||
- Can be used inside [Tailscale network](https://github.com/nextcloud/all-in-one/discussions/5439)
|
- Can be used inside [Tailscale](https://github.com/nextcloud/all-in-one/discussions/5439)
|
||||||
- Ready for big file uploads up to 10 GB on public links, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-upload-limit-for-nextcloud) (logged in users can upload much bigger files using the webinterface or the mobile/desktop clients since chunking is used in that case)
|
- Ready for big file uploads up to 10 GB on public links, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-upload-limit-for-nextcloud) (logged in users can upload much bigger files using the webinterface or the mobile/desktop clients since chunking is used in that case)
|
||||||
- PHP and web server timeouts set to 3600s, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-max-execution-time-for-nextcloud) (important for big file uploads)
|
- PHP and web server timeouts set to 3600s, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-max-execution-time-for-nextcloud) (important for big file uploads)
|
||||||
- Defaults to a max of 512 MB RAM per PHP process, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-php-memory-limit-for-nextcloud)
|
- Defaults to a max of 512 MB RAM per PHP process, [adjustable](https://github.com/nextcloud/all-in-one#how-to-adjust-the-php-memory-limit-for-nextcloud)
|
||||||
|
@ -249,7 +249,7 @@ Since Cloudflare Proxy/Tunnel comes with a lot of limitations which are listed b
|
||||||
### How to run Nextcloud behind a Cloudflare Tunnel?
|
### How to run Nextcloud behind a Cloudflare Tunnel?
|
||||||
Although it does not seems like it is the case but from AIO perspective a Cloudflare Tunnel works like a reverse proxy. So please follow the [reverse proxy documentation](./reverse-proxy.md) where is documented how to make it run behind a Cloudflare Tunnel. However please see the [caveats](https://github.com/nextcloud/all-in-one#notes-on-cloudflare-proxytunnel) before proceeding.
|
Although it does not seems like it is the case but from AIO perspective a Cloudflare Tunnel works like a reverse proxy. So please follow the [reverse proxy documentation](./reverse-proxy.md) where is documented how to make it run behind a Cloudflare Tunnel. However please see the [caveats](https://github.com/nextcloud/all-in-one#notes-on-cloudflare-proxytunnel) before proceeding.
|
||||||
|
|
||||||
### How to run Nextcloud inside a Tailscale network?
|
### How to run Nextcloud via Tailscale?
|
||||||
For a reverse proxy example guide for Tailscale, see this guide by @flll: https://github.com/nextcloud/all-in-one/discussions/5439
|
For a reverse proxy example guide for Tailscale, see this guide by @flll: https://github.com/nextcloud/all-in-one/discussions/5439
|
||||||
|
|
||||||
### Disrecommended VPS providers
|
### Disrecommended VPS providers
|
||||||
|
|
|
@ -2,6 +2,8 @@
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Please note that AIO comes secured with TLS out-of-the-box. So you don't need to necessarily set up your own reverse proxy if you only want to run Nextcloud AIO which is much easier. See [the normal readme](https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-use-this) in that case. However if port 443 should already be used because you already run a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else), you need to follow this reverse proxy documentation to set up Nextcloud AIO.
|
> Please note that AIO comes secured with TLS out-of-the-box. So you don't need to necessarily set up your own reverse proxy if you only want to run Nextcloud AIO which is much easier. See [the normal readme](https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-use-this) in that case. However if port 443 should already be used because you already run a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else), you need to follow this reverse proxy documentation to set up Nextcloud AIO.
|
||||||
|
> [!TIP]
|
||||||
|
> If you don't have a domain yet, [Tailscale is recommended](https://github.com/nextcloud/all-in-one/discussions/5439). If you don't have a reverse proxy yet, [Caddy is recommended](https://github.com/nextcloud/all-in-one/discussions/575).
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
In order to run Nextcloud behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else), you need to:
|
In order to run Nextcloud behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else), you need to:
|
||||||
|
|
Loading…
Reference in a new issue