19 hours ago, skois said:

Could you please go to /mnt/user/nextcloud and do an "ls -la"  (You can hide the usernames if you want. Seems like you missing the .htaccess file.

 

Also try opening a console in nextcloud dokcer and do "occ maintenance:update:htaccess"
See if that helps
Also post the swag config file if the above don't help.

Hi Skois,

 

I've done occ maintenance:update:htaccess and it's updated it but the problem still persists.

 

To do an ls -la, am I right in saying that I need to use the unraid terminal and navigate to that directory. If so, I apologise but how do I change the directory in the unraid terminal.

 

I don't know if it's of relevance, but when I click on the nextcloud icon on the docker tab and click Web UI it only navigates to localip and not localip:port.

 

Thanks,

 

Myles

6 minutes ago, Myleslewis said:

Hi Skois,

 

I've done occ maintenance:update:htaccess and it's updated it but the problem still persists.

 

To do an ls -la, am I right in saying that I need to use the unraid terminal and navigate to that directory. If so, I apologise but how do I change the directory in the unraid terminal.

 

I don't know if it's of relevance, but when I click on the nextcloud icon on the docker tab and click Web UI it only navigates to localip and not localip:port.

 

Thanks,

 

Myles

Hmm, post a screenshot of your nextcloud docker "edit page"

Open unraid terminal do "cd /mnt/user/nextcloud" and then "ls -la"

 

Hi Skois,

 

Above is my docker template, and I did actually try cd /mnt/user/nextcloud first but realised it's case sensitive my bad !

 

Here is the output:

 

Thanks,

 

Myles

5 minutes ago, Myleslewis said:

 

Hi Skois,

 

Above is my docker template, and I did actually try cd /mnt/user/nextcloud first but realised it's case sensitive my bad !

 

Here is the output:

 

Thanks,

 

Myles

Hmm, permissions seems different from mine, first do again "cd /mnt/user/NextCloud" and now do "cat .htaccess"
Then go to Unraid WebUI -> Tools -> New Permissions -> User Shares (select NextCloud) -> Start. 
Restart docker and try agian.
 

18 minutes ago, skois said:

Hmm, permissions seems different from mine, first do again "cd /mnt/user/NextCloud" and now do "cat .htaccess"
Then go to Unraid WebUI -> Tools -> New Permissions -> User Shares (select NextCloud) -> Start. 
Restart docker and try agian.
 

Hi Skois,

 

This is the output of cat .htaccess:

 

Also I've done the new permissions process and still same issue

 

Which swag config is you want to see ? The one specific to nextcloud subdomain or one of these:

 

 

Thanks, -Myles

 

12 minutes ago, Myleslewis said:

Which swag config is you want to see ? The one specific to nextcloud subdomain or one of these:

 

 

The nextcloud subdomain,

Can you please do a 'ls -la' on nextcloud folder again? After using the permission tool

 

Also open nextcloud docker console an do 'occ integrity:check-core'

Also Go to Docker tab -> Top right corner click advanced -> Right next to nextcloud docker hit force update

Edited March 24, 20215 yr by skois

1 minute ago, skois said:

The nextcloud subdomain,

Can you please do a ls -la on nextcloud folder again? After the permission tool

Hi Skois,

 

 

Here is my log without the commented out text:

 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name nextcloud.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 0;
    }
}

Just now, Myleslewis said:

Hi Skois,

 

 

Here is my log without the commented out text:

 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name nextcloud.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 0;
    }
}

I added some more info on previous post, refresh page and check the rest

7 minutes ago, skois said:

I added some more info on previous post, refresh page and check the rest

 

output of oss integrity:check-core

 

 

Forced update and docker reset, still same issue

1 minute ago, Myleslewis said:

 

output of oss integrity:check-core

 

 

Forced update and docker reset, still same issue

Unraid terminal "cat /mnt/user/appdata/nextcloud/www/nextcloud/.user.ini

9 minutes ago, skois said:

Unraid terminal "cat /mnt/user/appdata/nextcloud/www/nextcloud/.user.ini

 

output of cat /mnt/user/appdata/nextcloud/www/nextcloud/.user.ini

 

1 minute ago, Myleslewis said:

 

output of cat /mnt/user/appdata/nextcloud/www/nextcloud/.user.ini

 

Ok, here for sure something is wrong.
delete everything that starts with php_
You can put those on /mnt/user/appdata/nextcloud/php/php-local.ini

Restart docker and see if that helps

I've done, that and the issue still percists

Just now, Myleslewis said:

I've done, that and the issue still percists

Use other browser please. and preferably in incognito mode.

1 minute ago, skois said:

Use other browser please. and preferably in incognito mode.

 

Heres what I get in chrome in incognito mode.

 

Beginning to think a complete removal and fresh install is going to be needed soon !

1 minute ago, Myleslewis said:

 

Heres what I get in chrome in incognito mode.

 

Beginning to think a complete removal and fresh install is going to be needed soon !

Wait, this domain points to duckdns? 
Does duckdns have your correct public ip?  I'm trying to ping and it doesn't respond.
Also did you port forwarded the ports on your router?

I've got my domain registered with my domain provider and then a CNAME record that points the nextcloud subdomain to a duckdns address, the duckdns address is currently updated with my current IP address.

 

Ports are forwarded correctly also, I was able to connect to nextcloud using my subdomain for a good amount of time, as was a friend of mine who I provide storage to, nothings changed on my router since then, but just to be sure:

 

6 minutes ago, Myleslewis said:

I've got my domain registered with my domain provider and then a CNAME record that points the nextcloud subdomain to a duckdns address, the duckdns address is currently updated with my current IP address.

 

Ports are forwarded correctly also, I was able to connect to nextcloud using my subdomain for a good amount of time, as was a friend of mine who I provide storage to, nothings changed on my router since then, but just to be sure:

 

can you ping your subdomain? ping nextcloud.***.net ?
If you can't probably something is off with the whole domain-duckdns thhing.
Check also on your registaar if the he currently have is correct.

Do you remeber what happened when it stopped working?


Just to make sure its the whole domain thing the problem.

Go to /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php

Change 'overwrite.cli.url' to ->                   'overwrite.cli.url' => 'https://192.168.1.139:444', 

comment out using a # infront. the lines overwritehost and overwriteprotocol

Change network from proxynet to bridge
Restart docker and try to access it with local ip:port
 

Edited March 24, 20215 yr by skois

6 minutes ago, skois said:

can you ping your subdomain? ping nextcloud.***.net ?
If you can't probably something is off with the whole domain-duckdns thhing.
Check also on your registaar if the he currently have is correct.

Do you remeber what happened when it stopped working?


Just to make sure its the whole domain thing the problem.

Go to /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php

Change 'overwrite.cli.url' to ->                   'overwrite.cli.url' => 'https://192.168.1.139:444', 

comment out using a # infront. the lines overwritehost and overwriteprotocol

Change network from proxynet to bridge
Restart docker and try to access it with local ip:port
 

I can ping nextcloud.***.net and get a response with my public ip, all okay here.

 

Not sure what you mean by "checking on my registrar if the he currently have is correct", sorry. The CNAME is still as it was previously, nothings changed there.

 

I completed the next steps and still cannot connect using localip:port

14 minutes ago, Myleslewis said:

I can ping nextcloud.***.net and get a response with my public ip, all okay here.

 

Not sure what you mean by "checking on my registrar if the he currently have is correct", sorry. The CNAME is still as it was previously, nothings changed there.

 

I completed the next steps and still cannot connect using localip:port

Sorry meant if registar have the correct ip***

 

Ah also change database to bridge network!

 

Hmmm  Please once again post the config.php file and the docker edit of nextcloud (this time click the advanced on top right corner)

Edited March 24, 20215 yr by skois

16 minutes ago, skois said:

Sorry meant if registar have the correct ip***

 

Hmmm  Please once again post the config.php file and the docker edit of nextcloud (this time click the advanced on top right corner)

Ah right, yeah it definitely gives the correct IP when pinging it.

 

Here is my docker template in advance view:

 

Here is my config.php:

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => '************',
  'passwordsalt' => '*****************************************',
  'secret' => '*************************************************',
  'trusted_domains' =>
  array (
    0 => '192.168.1.139:444',
    1 => 'nextcloud.*********.net',
  ),
  'dbtype' => 'mysql',
  'version' => '20.0.7.1',
  'overwrite.cli.url' => 'https://192.168.1.139:444',
#  'overwritehost' => 'nextcloud.********.net',
#  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.139:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => '*********',
  'installed' => true,
  'trusted_proxies' => ['swag'],
);

 

I did change the webui port to 444 as I noticed it was 443 in the advance mode, but still same issue, cant access via localip:port

Edited March 24, 20215 yr by Myleslewis

1 minute ago, Myleslewis said:

Ah right, yeah it definitely gives the correct IP when pinging it.

 

Here is my docker template in advance view:

 

Here is my config.php:

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => '************',
  'passwordsalt' => '*****************************************',
  'secret' => '*************************************************',
  'trusted_domains' =>
  array (
    0 => '192.168.1.139:444',
    1 => 'nextcloud.*********.net',
  ),
  'dbtype' => 'mysql',
  'version' => '20.0.7.1',
  'overwrite.cli.url' => 'https://192.168.1.139:444',
#  'overwritehost' => 'nextcloud.********.net',
#  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.139:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => '*********',
  'installed' => true,
  'trusted_proxies' => ['swag'],
);

Change database also to bridge from proxynet.

Check if it works.
If not, go to nextcloud docker and click console. do "ping 1.1.1.1 -c4" and "ping 192.168.1.139 -c4" change the local ip to your ip of your pc not your server.
To see if the docker can access internal network and external.

6 minutes ago, skois said:

Change database also to bridge from proxynet.

Check if it works.
If not, go to nextcloud docker and click console. do "ping 1.1.1.1 -c4" and "ping 192.168.1.139 -c4" change the local ip to your ip of your pc not your server.
To see if the docker can access internal network and external.

database is on bridge already when I originally changed nextcloud to bridge, and both pings were successful

 

Just now, Myleslewis said:

database is on bridge already when I originally changed nextcloud to bridge, and both pings were successful

 

If you still can't access nextcloud with 192.168.1.139:444 .
Then i really don't know whats going on there. Sorry

4 minutes ago, skois said:

If you still can't access nextcloud with 192.168.1.139:444 .
Then i really don't know whats going on there. Sorry

I think at this point, all I can do is do a complete removal of nextcloud and reinstall it all from scratch.

 

I would like to say thank you so much for taking so much time in helping me troubleshoot what's happening and why I can't access my nextcloud.

 

You're a credit to the forum !