nextcloud compose.yml question

Well, to begin with PUID=998 is wrong. You need to create a user in the Users tab of OMV. It will have a PUID of 1000 if you haven’t created one already. You can find out what your user’s id is by ssh into your server and enter id <user-name>

Did you get a cert from Swag when you ran docker logs -f swag?

Zitat von HackitZ

Thanks, I'm not sure where i got 998 from, but i have updated it to my docker user id.

i restarted docker in the cli.

i was then able to load the page to finish setup but it looked like a text page. tried to reload but it was the same.

i went ahead and filled in the fields, now the page wont load. the url, I had to use was my local as the 192.168.1.2:450

i was unable to use my own url mine.media

I've tried another browser and the page tries to load while using 192.168.1.2:450, page instantly says err_too_many_redirects

I also still have this error in the nextcloud logs, it's the last item listed.

Code

Stack trace:
#0 /config/www/nextcloud/lib/base.php(649): OC::checkInstalled()
#1 /config/www/nextcloud/lib/base.php(1087): OC::init()
#2 /config/www/nextcloud/cron.php(43): require_once('/config/www/nex...')

Alles anzeigen

LOL, it's OK, we all know where you got it.

Zitat von HackitZ

yes

Code

dns validation via cloudflare plugin is selected
Certificate exists; parameters unchanged; starting nginx
[cont-init.d] 50-config: exited 0.
[cont-init.d] 60-renew: executing...
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
[cont-init.d] 60-renew: exited 0.
[cont-init.d] 70-templates: executing...
[cont-init.d] 70-templates: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Server ready

Alles anzeigen

That doesn't necessarily say you got a cert

Also, if you just signed up for Cloudflare and added it to your domain, it can take up to 24hrs for it to become active.

I'm assuming you've added your cloudflare API to the dns-conf file (I think that's where it is)?

Zitat von HackitZ

Thanks for the help.

i've had cloudflare for about 2 days, it says active.

yes i added my api to dns-conf.

Yeah I'm not that familiar w/ how cloudflare works to give you much help on it... The swag documentation has it pretty well documented I do believe...

https://docs.linuxserver.io/general/swag

Zitat von HackitZ

so i'm to the point where i can get to the nextcloud page but it says

"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."

i have checked my config.php and have tried removing my local ip, but at this point my url wont work. so i'm focused on getting my local ip to work. when i edit my confog.php, before i check i stop, nextcloud, nexctclouddb then swag. i then start swag, nextclouddb then nextcloud. in that oder.

but i still get the access through untrusted domain.

here is my config.php, does it look right?

Code

$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'trusted_proxies' =>
  array (
    0 => 'swag',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://my.media/nextcloud',
  'trusted_domains' =>
  array (
    0 => '192.168.1.100:443',
    1 => 'my.media:443',
  ),
  'instanceid' => 'ocbh3m89lwti',
  'passwordsalt' => 'cPTj7Ft1lsy4DgYg1RXQLG9EshrXbL',
  'secret' => 'AqNXodL3ZoyuJuT++xLgAyhQxhWvWSvP1OhbYkUWBHuYAIVG',
  'dbtype' => 'mysql',
  'version' => '23.0.0.10',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_my name',
  'dbpassword' => 'xPeqSX9mWO8dNasCS8QZBJJ0d5SKRq',
  'installed' => true,
);

Alles anzeigen

Alles anzeigen

Well, you need to add your domain under trusted domain... it should look something like this. You seem to have a port on the end, which shouldn't be necessary. Here's mine (obviously I use subdomains, but I think it should be similar)

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ochk7l124gww',
  'passwordsalt' => 'lKd6k35sjqRW/byfQsjH113hRSy7Cc',
  'secret' => 'bIsiyEvwcZ7AoI+e268wzhRQe6bk19SjEsPUIuAZ0EieNaB3',
  'trusted_domains' => 
  array (
    0 => '192.168.1.166:450',
    1 => 'nextcloud.mydomain.xyz',
  ),
  'dbtype' => 'mysql',
  'version' => '23.0.0.10',
  'overwrite.cli.url' => 'https://nextcloud.mydomain.xyz',
  'overwritehost' => 'nextcloud.mydomain.xyz',
  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextclouddb',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => 'sTYIhUClvA12kJxUfQAtIjHkqiy1PY',
  'installed' => true,
  'default_phone_region' => 'US',
  'app_install_overwrite' => 
  array (
    0 => 'documentserver_community',
    1 => 'rainloop',
  ),
  'trusted_proxies' => 
  array (
    0 => '192.168.1.166:450',
    1 => 'nextcloud.mydomain.xyz',
  ),
  'maintenance' => false,
);

Zitat von Soma

KM0201

Saw this some time ago and wanted to ask you about this snippet, although I think I already know the answer:

Why you don't have swag as trusted proxy?!? Is it because you use swag outside the composer stack?

Code

  'trusted_domains' => 
  array (
    0 => '192.168.1.166:450',
    1 => 'nextcloud.mydomain.xyz',
  ),
.................................
  'trusted_proxies' => 
  array (
    0 => '192.168.1.166:450',
    1 => 'nextcloud.mydomain.xyz',
  ),

Alles anzeigen

As per instructions on linuxserver/docker-swag, you only need:

Code

# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
#  'trusted_proxies' => ['swag'],

And, as I see it, if you're using a external network on docker stacks to point other services to swag, they will see it as hostname==swag so:

Doesn't it work (nextcloud config.php) if you do it as per the conf.sample, instead of how you do it?

Alles anzeigen

Yes (but I set it up like that even when I used swag inside the nextcloud stack). I set it up like that for the first time years ago and it worked fine... so I've just always set it up like that and it continues to work.

Zitat von Soma

Yep, one more case of:

There's too many ways to kill flies...

Couldn't agree more.

Hell just look at installing Nextcloud. You can install on the host, install with snap, install in docker w/ docker compose, install in docker w/ a stack... probably some other way I'm missing..

And the end result is essentially all the same... You have Nextcloud

Zitat von HackitZ

so i'm thinking it's easier to see what everyone else is using.

I use my own domain. With this container I solve the dynamic IP problem.

[How-To] Install DuckDNS. Automatic dynamic IP update.

I then set up subdomains of my domain by setting the Cname to mydomain.duckdns.org. For example nextcloud.mydomain.com or jellyfin.mydomain.com pointing to mydomain.duckdns.org