With Version23: behind a reverse proxy and the overwrite config variables are not set correctly

[JoergHein]

Hello,

I installed my Nextcloud via Docker Image.
With the new version 23, I have the following problem.

"You are accessing your instance over a secure connection, however your instance is generating insecure URLs. This most likely means that you are behind a reverse proxy and the overwrite config variables are not set correctly"

I have the last changes in the Dockerfile and in the docker-compose.yml according to example:

https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/with-nginx-proxy/mariadb/apache

updated on my server.
Nevertheless, the message mentioned above still occurs.

Does anyone have a solution for me?
Thanks and Regards

[anshibanov]

+1 same issue

[BryanEmmerson]

Set the OVERWRITEPROTOCOL environment variable for you Nextcloud service to https (see section Using the apache image behind a reverse proxy and auto configure server host and protocol on the official Nextcloud docker page.

I also set the TRUSTED_PROXIES variable, but I don't think this is strictly necessary for the above issue.

[thomasmerz]

Same problem here with https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/with-nginx-proxy/mariadb/fpm … 🤷🏻‍♂️
Running Nextcloud Hub II (23.0.0) being "up to date" on "stable channel".

[JoergHein]

Shouldn't the error be better fixed in the Docker configuration?
The error did not occur before version 23.0 and I use the default configuration.

[Xanarkan]

Yup, same error since 23.0 and I didn't have it before.
That kind of thing occurring when you use the official Docker image with the official docker-compose file is a bit disturbing.
Isn't possible to fix this directly in the image so we don't have to weak it after install and risk having to do it again when we update the container or when we recreate it ?

[ouankou]

Recently I just deployed NextCloud 23 and MariaDB 10.6 using docker-compose. A similar issue was encountered. My solution is something as follows.

Assume you've set Apache domain proxy on the host properly, requests to yourdomain.com will be forwarded to the actual NextCloud host on 127.0.0.1:8080.

1. Add the following attributes to config.php:

  'trusted_domains' => 
  array (
    0 => 'yourdomain.com',
  ),
  'trusted_proxies' => 
  array (
    0 => 'yourdomain.com',
  ),
  'overwrite.cli.url' => 'https://yourdomain.com',
  'overwriteprotocol' => 'https',

2. Restart docker-compose. The warning should be gone.

[thomasmerz]

I had to fix both "overwrite…" lines (add line overwriteprotocol and fix http to https in line overwrite.cli.url). Both "trusted…" lines were already correct. Now this is also fixed for me. Thank you very much @ouankou 🤗

[donhauser]

I think overwrite.cli.url can be set by the OVERWRITECLIURL environment variable (did not test it though).

The file config/reverse-proxy.config.php contains the following php code, which is also used for other env-variables like OVERWRITEHOST and OVERWRITEPROTOCOL:

$overwriteCliUrl = getenv('OVERWRITECLIURL');
if ($overwriteCliUrl) {
  $CONFIG['overwrite.cli.url'] = $overwriteCliUrl;
}

Setting variables in docker-compose.yml:

nextcloud:
  image: nextcloud:23
  [...]
  environment:
    - TRUSTED_PROXIES=yourdomain.com
    - OVERWRITECLIURL=https://yourdomain.com
    - OVERWRITEPROTOCOL=https
    # I think this hooks in at a slightly different place
    - NEXTCLOUD_TRUSTED_DOMAINS=yourdomain.com
    # maybe you also want this
    - OVERWRITEHOST=yourdomain.com

PS: If you are annoyed by repeatedly entering your domain, you can use an .env file and the VAR=${VAR}- syntax

[JoergHein]

Thanks, that was the solution I was looking for :-)
That worked

[shimulroy842]

'overwrite.cli.url' => 'https://yourdomain.com',

it works thanks. but now I cannot access the nextcloud from the local network(HTTP://192.168.0.245:8080) it says "secure connection failed" in the browser.

[thomasmerz]

@shimulroy842 : Use https:// instead of http:// and it should not fail anymore.

[heinrichmartin]

This issue is closed, and I am on branch master, but I am still seeing this issue in postgres/fpm. With the technical details by @ouankou and the solution by @donhauser, I was able to fix it cleanly.

Has anyone considered a PR? Should this issue be re-opened? Or create another one?

(I am not on a fork, and I came to this setup only today; so I have no clue about other files to be fixed, sorry. Btw, a big thank you for the great work - this is a solid config that is fun to apply! 🥳)

diff --git a/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml b/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml
index 6e41174..6713b2a 100644
--- a/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml
+++ b/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml
@@ -21,6 +21,7 @@ services:
     environment:
       - POSTGRES_HOST=db
       - REDIS_HOST=redis
+      - OVERWRITEPROTOCOL=https
     env_file:
       - db.env
     depends_on:

[HHUBSS]

Recently I just deployed NextCloud 23 and MariaDB 10.6 using docker-compose. A similar issue was encountered. My solution is something as follows.

Assume you've set Apache domain proxy on the host properly, requests to yourdomain.com will be forwarded to the actual NextCloud host on 127.0.0.1:8080.

1. Add the following attributes to config.php:

  'trusted_domains' => 
  array (
    0 => 'yourdomain.com',
  ),
  'trusted_proxies' => 
  array (
    0 => 'yourdomain.com',
  ),
  'overwrite.cli.url' => 'https://yourdomain.com',
  'overwriteprotocol' => 'https',

2. Restart docker-compose. The warning should be gone.

I followed this. I can access nextcloud thru public domain but I can't access it locally using http or https

[sohaib1khan]

Thank you soooo much!! worked for me