ERROR "access through untrusted domain"

vichanzo · 19 January 2022 09:55

I am using the Docker image lscr dot io/linuxserver/nextcloud along with SWAG and duckdns

when I go to https mysubdomain dot duckdns dot org/nextcloud I am getting “Access through untrusted domain”


Nextcloud
Access through untrusted domain

Please contact your administrator. If you are an administrator, edit the "trusted_domains" setting in config/config.php like the example in config.sample.php.

Further information how to configure this can be found in the documentation.

Nextcloud – a safe home for all your data

I’ve also tried modifying the /config/config.php file, but I don’t have one.

sudo docker exec -it nextcloud /bin/bash

/config# ls -a
.  ..  .cache  .rnd  crontabs  custom-cont-init.d  custom-services.d  keys  log  nginx	php  www

aptalca · 19 January 2022 14:17

github.com

linuxserver/reverse-proxy-confs/blob/master/nextcloud.subdomain.conf.sample#L3-L14

    
      
          # assuming this container is called "swag", edit your nextcloud container's config
          # located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
          #  'trusted_proxies' => ['swag'],
          #  'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
          #  'overwritehost' => 'nextcloud.your-domain.com',
          #  'overwriteprotocol' => 'https',
          #
          # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
          #  array (
          #    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
          #    1 => 'nextcloud.your-domain.com',
          #  ),

vichanzo · 20 January 2022 07:34

Thanks. I think I have some more playing around to do to get this to work, but this is definitely getting me in the right direction. Now that I know the location of the config.php is actually:

/config/www/nextcloud/config/config.php

driz · 22 January 2022 17:00

It’s amazing what reading will do for you As a side note, barring reading the actual documentation, you can also use find to find where files are. For future reference, something like find <path to config> -type f -name "config.php" would’ve done the trick for you.

system · 27 January 2022 17:00

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