[Support] Linuxserver.io - Nextcloud

[PeeBee]

Problem: Internal Server Error When Opening WebUI

 

This problem started a few months ago but it hasn't been a priority to fix because everything still syncs fine to my other computers. 

 

When I open the WebUI I get an Internal Server Error. The error then states "The server was unable to complete your request". I made a video of the problem, shown below. Any thoughts? 

(diagnostics attached)
 

 

tower-diagnostics-20200219-2126.zip

Edited February 19, 2020 by PeeBee

[OsoPolar]

HI Guys

I have been trying for a couple of days to solve a WebDav issue.

My hosting supplier offers via cPanel an app callled Installatron which allows you to schedule backups of your site.

I do this nightly and used to ftp it to my old Win server. But now running Unraid i saw an option to Webdav and Nextcloud had WebDav facility.

I have followed and so have two senior 2 level server tech to make it work.

I have obtained the WebDav link from within NextCloud used the relevant login details and i get the same error every time

We have tried about 30 to 50 different ways of accessing my Nextcloud.

 

We have followed the help guide from nextcloud

 

Please can anybody show some light on the issue

 

[knex666]

Hi @OsoPolar,

 

are you using a second factor for you authentication?

maybe the best way is to create an App Token at settings/security and use this for your WebDAV sync have you tryed this?

Your content seems to be empty and you try to access a path /Backup/... this will not work.

 

Cheers

[OsoPolar]

Hello

We have no 2 factor setup yet.

The folder is empty as we have not managed to get access yet!

The requirement is to place a backup file in there each night.

[knex666]

30 minutes ago, OsoPolar said:

Hello

We have no 2 factor setup yet.

The folder is empty as we have not managed to get access yet!

The requirement is to place a backup file in there each night.

Yes but if the folder does not exist webdav will not create one for you and sync fails.

But before try login with an app token.

 

Cheers

[OsoPolar]

29 minutes ago, knex666 said:

Yes but if the folder does not exist webdav will not create one for you and sync fails.

But before try login with an app token.

 

Cheers

Please check my images the folders are there!!!!!

 

There in place to input app token only have username & password

[knex666]

I have got a very easy idea.
Check out if webdav works on your Windows PC and add the webdav as network drive.
If that works you know where to go.

Cheers

Gesendet von meinem Redmi Note 8 Pro mit Tapatalk

[blaine07]

Anyone else seeing “Warning/Camerarswpreview/You do not have perp globally installed. Using a depreciated built in perl.

In their logs? Is their someway for me to install Perl? Or Update it?

Anything?

[forj]

On 2/19/2020 at 1:05 PM, Kewjoe said:

I'm having an issue with Only Office. I followed spaceinvaderone's video. OnlyOfficeDocumentServer docker is set up. When i go to my "documentserver.mydomain.com" it shows "Document Server is running" with a green checkmark. I install the Only Office app in Nextcloud, i added the "documentserver.mydomain.com" to the Only Office options. It accepts it and saves. I create a document and go inside and i just get a blank screen. No errors (Using Firefox)

 

The only clue I have, using Chrome i notice i get an error message in the middle of the screen only if i hover my mouse over which says "documentserver.mydomain.com refused to connect". I triple checked my nextcloud settings, my letsencrypt settings.. the documentserver subdomain conf file. I've removed and re-added both the docker and the only office app. Nextcloud, Let's Encrypt and the DocumentServer docker are on my proxynet network.

 

Any one got any ideas?

 

 

A number of us are having the same problem and no one has responded with any idea of the reason or a solution. Both containers can connect to each other. proxy is working for both internal and external connections to both containers...

documentserver.domain.com "refused to connect"

[knex666]

2 hours ago, forj said:

 

 

A number of us are having the same problem and no one has responded with any idea of the reason or a solution. Both containers can connect to each other. proxy is working for both internal and external connections to both containers...

documentserver.domain.com "refused to connect"

I got a simple idea you can use the official Image its in the community Apps and has nextcloud integrated. But you will maybe loose your settings. Just try IT out as an other instance. 

[alturismo]

 

2 hours ago, forj said:

 

 

A number of us are having the same problem and no one has responded with any idea of the reason or a solution. Both containers can connect to each other. proxy is working for both internal and external connections to both containers...

documentserver.domain.com "refused to connect"

as this is the nextcloud lsio forum ... not the onlyoffice helpdesk here, may take a look at your reverse proxy config for onlyoffice, if u took just a copy of nextcloud letsencrypt conf and only adjusted the routes that wont work (my experience), u need to adjust the reverse proxy config for onlyoffice as described on their page, then it works, at least thats what i did here after testing the choices (official NC with integrated onlyoffice, lsio NC with external onlyoffice - personal winner).

 

here is my nginx config which works fine here (lsio NC and sep onlyoffice docker), adjust domain and reverse of course, reverse address with port (when running onlyoffice in bridge mode) or ip only (when running with own ip), both tested and working, comment, uncomment or remove the not needed parts, i adjusted this from the official onlyoffice site with their nginx config.

 

# Use this example for proxy HTTPS traffic to the document server running at 'backendserver-address'.
# Replace {{SSL_CERTIFICATE_PATH}} with the path to the ssl certificate file
# Replace {{SSL_KEY_PATH}} with the path to the ssl private key file

map $http_host $this_host {
    "" $host;
    default $http_host;
}

map $http_x_forwarded_proto $the_scheme {
     default $http_x_forwarded_proto;
     "" $scheme;
}

map $http_x_forwarded_host $the_host {
    default $http_x_forwarded_host;
    "" $this_host;
}

map $http_upgrade $proxy_connection {
  default upgrade;
  "" close;
}

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

  server_name onlyoffice-domain.*;

  server_tokens off;

  include /config/nginx/ssl.conf;

  add_header Strict-Transport-Security max-age=31536000;
  # add_header X-Frame-Options SAMEORIGIN;
  add_header X-Content-Type-Options nosniff;

  location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $proxy_connection;
		proxy_set_header X-Forwarded-Host $the_host;
		proxy_set_header X-Forwarded-Proto $the_scheme;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#    proxy_pass http://192.168.1.2:8082;
	proxy_pass http://192.168.1.93;
  }
}

 

Edited February 21, 2020 by alturismo

[OsoPolar]

17 hours ago, knex666 said:

I have got a very easy idea.
Check out if webdav works on your Windows PC and add the webdav as network drive.
If that works you know where to go.

Cheers

Gesendet von meinem Redmi Note 8 Pro mit Tapatalk
 

HI

WedDav works fine on my Win Laptop 

[knex666]

7 minutes ago, OsoPolar said:

HI

WedDav works fine on my Win Laptop 

Than it is not a nextcloud issue

[knex666]

On 2/19/2020 at 10:31 PM, PeeBee said:

Problem: Internal Server Error When Opening WebUI

 

This problem started a few months ago but it hasn't been a priority to fix because everything still syncs fine to my other computers. 

 

When I open the WebUI I get an Internal Server Error. The error then states "The server was unable to complete your request". I made a video of the problem, shown below. Any tho 135.38 kB · 0 downloads

To answere your question I would need your nextcloud log files. Your unraid diagnostics will not help to identify the issue

[OsoPolar]

15 minutes ago, knex666 said:

Than it is not a nextcloud issue

Is there not a difference doing a webdav link on an internal network as opposed to linking from an external host providers server?

[knex666]

1 minute ago, OsoPolar said:

Is there not a difference doing a webdav link on an internal network as opposed to linking from an external host providers server?

If you used your local ip than try again with your external domain name. if that fails the issue would maybe be the reverse proxy but there it in fact no difference.

[OsoPolar]

7 minutes ago, knex666 said:

If you used your local ip than try again with your external domain name. if that fails the issue would maybe be the reverse proxy but there it in fact no difference.

If i check my properties on the laptop link it looks external

 

Target  https://nextcloud.daddycloud.co.uk/remote.php/dav/files/thorrrr

Comment \\[email protected]\DavWWWRoot\remote.php\dav\files\thorrrr

 

If you try the https as above you get an error but if you remove remote.php/dav/files/thorrrr it lets you in??

[knex666]

3 minutes ago, OsoPolar said:

If i check my properties on the laptop link it looks external

 

Target  https://nextcloud.daddycloud.co.uk/remote.php/dav/files/thorrrr

Comment \\[email protected]\DavWWWRoot\remote.php\dav\files\thorrrr

 

If you try the https as above you get an error but if you remove remote.php/dav/files/thorrrr it lets you in??

Nope, you are using your external address so if that works it should work at your Backup-system as well. So as I sayed the issue is not nextcloud

[anongum]

I recently installed different apps for the efull text search (all of those available actually) and basically immediately the webui stopped working (error 500 internal server) - so basically, is there a way to remove or disable the app without accessing the webui?
I tried this 
cd /config/www/nextcloud/

sudo -u www-data php occ app:disable NAME_OF_APP

from the shell in the docker tab from the unraid webui, but it gives me this error

sudo: unknown user: www-data
sudo: unable to initialize policy plugin

 

what can I do?

 

[blaine07]

Could would anyone provide assistance in doing this on Nextcloud on Unraid?


https://help.nextcloud.com/t/new-photo-app-in-nextcloud-18/69949/20

[Kewjoe]

On 2/21/2020 at 12:52 AM, alturismo said:

 

as this is the nextcloud lsio forum ... not the onlyoffice helpdesk here, may take a look at your reverse proxy config for onlyoffice, if u took just a copy of nextcloud letsencrypt conf and only adjusted the routes that wont work (my experience), u need to adjust the reverse proxy config for onlyoffice as described on their page, then it works, at least thats what i did here after testing the choices (official NC with integrated onlyoffice, lsio NC with external onlyoffice - personal winner).

 

here is my nginx config which works fine here (lsio NC and sep onlyoffice docker), adjust domain and reverse of course, reverse address with port (when running onlyoffice in bridge mode) or ip only (when running with own ip), both tested and working, comment, uncomment or remove the not needed parts, i adjusted this from the official onlyoffice site with their nginx config.

 

# Use this example for proxy HTTPS traffic to the document server running at 'backendserver-address'.
# Replace {{SSL_CERTIFICATE_PATH}} with the path to the ssl certificate file
# Replace {{SSL_KEY_PATH}} with the path to the ssl private key file

map $http_host $this_host {
    "" $host;
    default $http_host;
}

map $http_x_forwarded_proto $the_scheme {
     default $http_x_forwarded_proto;
     "" $scheme;
}

map $http_x_forwarded_host $the_host {
    default $http_x_forwarded_host;
    "" $this_host;
}

map $http_upgrade $proxy_connection {
  default upgrade;
  "" close;
}

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

  server_name onlyoffice-domain.*;

  server_tokens off;

  include /config/nginx/ssl.conf;

  add_header Strict-Transport-Security max-age=31536000;
  # add_header X-Frame-Options SAMEORIGIN;
  add_header X-Content-Type-Options nosniff;

  location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection $proxy_connection;
		proxy_set_header X-Forwarded-Host $the_host;
		proxy_set_header X-Forwarded-Proto $the_scheme;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
#    proxy_pass http://192.168.1.2:8082;
	proxy_pass http://192.168.1.93;
  }
}

 

 

I tried your config and it still didn't work. I tried different variations, but nothing is working.

Edited February 22, 2020 by Kewjoe

[alturismo]

1 hour ago, Kewjoe said:

 

I tried your config and it still didn't work. I tried different variations, but nothing is working.

may start if your only office is working

 

depending on setup ip:port should bring a welcome page

then nginx reverse onlyoffice domain should bring u also the welcome page

 

if that works NC onlyoffice should also work

[CyberMew]

I already have a 2tb folder on unraid that I want to share. How do I make that folder be shown in nextcloud? And even better yet like a normal folder so I can edit or move files around inside nextcloud?

Edited February 22, 2020 by CyberMew

[JonathanM]

48 minutes ago, CyberMew said:

I already have a 2tb folder on unraid that I want to share. How do I make that folder be shown in nextcloud? And even better yet like a normal folder so I can edit or move files around inside nextcloud?

https://www.techrepublic.com/article/how-to-add-external-storage-on-your-nextcloud-server/

[brotherbeagle]

On 2/20/2020 at 10:30 PM, forj said:

 

 

A number of us are having the same problem and no one has responded with any idea of the reason or a solution. Both containers can connect to each other. proxy is working for both internal and external connections to both containers...

documentserver.domain.com "refused to connect"

I'm in the same boat.   Nginx is passing traffic along as expected to both, both containers are available to each other (pingable, wget pulls an index.html, etc...).

 

That said, the OnlyOffice container is not behaving correctly (it refuses to acknowledge its modified http port and continues to refer to '8080' (hovering above the Webgui link in the dashboard shows it's identifying at 8080, vs my directed 8088) and the log clearly states the refused connection: 

 

2020/02/20 18:12:50 [error] 699#699: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.19.0.6, server: , request: "GET /healthcheck HTTP/1.1", upstream: "http://127.0.0.1:8000/healthcheck", host: "docserver.xxxx.xxx:443")  <-- and that's annoying as connecting directly to https://docserver.xxxx.xxx gives me a big, ol' happy:  Document Server is running.

 

I haven't looked beyond this yet and probably won't have a chance until next week -- but I thought it would be worth it to mention that it doesn't appear to be an issue with the Nextcloud container (which is working fine on my end -- though, it is much slower/less responsive than it was before 18.0.1  and that's on a fresh install with the database housed on my stable, production MariaDB instance over on one of my Proxmox nodes...).