[Support] Linuxserver.io - Nextcloud


Recommended Posts

On 2018-02-11 at 8:33 PM, CHBMB said:

 

As much as you can post.  config.php nextcloud file as starters.

 

Basically any file that you edit during the setup and the mariadb docker logs

Hello!

So I found this errors in the nextcloud log. The MariaDB log did not show anything interesting.

error.PNG

mariadb.PNG

custom.cnf

Edited by Prokie
Link to comment

So far, all I can give you is this:

Quote

500 Internal Server Error = A generic error message, given when an unexpected condition was encountered and no more specific message is suitable

 

So having the "same error" means nothing, unless people start posting some config files as requested there's nothing anyone can do to help.

Link to comment
17 hours ago, Sturluson said:

 

Based on the post time, I think Snipe3000 and I had this issue at about exactly the same time - finally gave up and went to bed. My Nextcloud log looks identical. I didn't check the nginx logs, but I did take a look in the Unraid filesystem and the /appdata/nextcloud/config folder never got created. This is also a brand new install, for whatever that's worth.

I think the repo was updated. I tried it again today and it installed properly.

Does anyone know if Nextcloud can be used to access the shares? Thats really what I want to use it for.

Link to comment
3 hours ago, CHBMB said:

So far, all I can give you is this:

 

 

So having the "same error" means nothing, unless people start posting some config files as requested there's nothing anyone can do to help.

 

Turns out it was actually a problem with the mariadb container. I think the database got corrupted with an unclean shutdown of the container. Restored from backup and all is well again including upgrade to v13.0 withing GUI.

Link to comment

Hi

Tonight I installed and configured nextcloud with duckdns and everything works almost perfectly

Here my 3 issues : 

I spent the last 2 hours to read about these problems on forums but no solutions help.

 

Can someone help me ?

Thanks !

 

Edited by deadnote
Link to comment
Hi
Tonight I installed and configured nextcloud with duckdns and everything works almost perfectly
Here my 3 issues : 
I spent the last 2 hours to read about these problems on forums but no solutions help.
 
Can someone help me ?
Thanks !
 
Probably because the URL is wrong for the Windows version. Also I don't recommend using a subfolder setup.

Sent from my LG-H815 using Tapatalk

Link to comment

Would you expect there to be a problem accessing a Nextcloud docker from a windows VM also running on the same host but on a different VLAN and subnet?

 

I have latest NextCloud docker on unRAID 6.3.5. I have changed the access port from 443 to 4437 in the docker config. I have not added any certificates to Nextcloud. I have not tried to add any VLANs to the docker.

 

https://tower:4437 works fine from PCs on the same subnet as Tower. It also works fine from a windows VM running on the same host and in the same vlan and subnet as Tower.

 

It does not work from a windows VM running on Tower, but on a different subnet and VLAN. in Firefox, I get a rapid succession of TLS handshake message in the bottom left status bar, and then a "Secure connection failed The connection to the server was reset while the page was loading." The routing and default gateway for both VLANs are done by an external router. No firewall rules currently restricting traffic between either VLAN.

 

Not sure whether this is a problem in my own network, a general docker/network restriction on 6.3.5, or a problem with Nextcloud.

 

How do I enable non-https access to the docker? I tried just adding a mapping from 8089 to port 80 on the docker container but I don't think http is enabled by default.

 

Link to comment
Would you expect there to be a problem accessing a Nextcloud docker from a windows VM also running on the same host but on a different VLAN and subnet?
 
I have latest NextCloud docker on unRAID 6.3.5. I have changed the access port from 443 to 4437 in the docker config. I have not added any certificates to Nextcloud. I have not tried to add any VLANs to the docker.
 
https://tower:4437 works fine from PCs on the same subnet as Tower. It also works fine from a windows VM running on the same host and in the same vlan and subnet as Tower.
 
It does not work from a windows VM running on Tower, but on a different subnet and VLAN. in Firefox, I get a rapid succession of TLS handshake message in the bottom left status bar, and then a "Secure connection failed The connection to the server was reset while the page was loading." The routing and default gateway for both VLANs are done by an external router. No firewall rules currently restricting traffic between either VLAN.
 
Not sure whether this is a problem in my own network, a general docker/network restriction on 6.3.5, or a problem with Nextcloud.
 
How do I enable non-https access to the docker? I tried just adding a mapping from 8089 to port 80 on the docker container but I don't think http is enabled by default.
 
I would expect it to work providing your network is configured correctly.

http isn't recommended and would require manually editing the nginx config in the appdata and also editing config.php

Sent from my LG-H815 using Tapatalk

  • Like 1
Link to comment
On 8.2.2018 at 6:54 AM, alturismo said:

Hi, just would like to know where i could look for to get following security and setup warnings corrected.

 

happening here when i change from apache reverse proxy to letsencrypt reverse proxy (apache i cant get the ssl certs renewed so i switched to letsencrypt ...)

 

simple reverse rule in letsencrypt

 

    location / {
       auth_basic off;
       allow all; # Allow all to see content 
        include /config/nginx/proxy.conf;
        proxy_pass http://192.168.1.2:447;
    }

 

its all working as it should, bu i get this security warnings while behind apache simple reverse rule theres all good, may a hint where to look for ?

 

following errors inside nextcloud since then

  • Der „X-XSS-Protection“-HTTP-Header ist nicht so konfiguriert, dass er „1; mode=block“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
  • Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
  • Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
  • Der „X-Frame-Options“-HTTP-Header ist nicht so konfiguriert, dass er „SAMEORIGIN“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.

 

I've got the same problem. Can you tell me how you fixed this problem? I read and followed the guide on Linuxserver.io but I can't find the problem for this error. Also, I can only open the nextcloud URL with the server.com/nextcloud instead of nextcloud.server.com.

 

I used nextcloud on my old server with openmediavault and I'm new on unraid so I'm sorry for asking so many questions :D.

 

Link to comment
8 hours ago, CreZo said:

 

I've got the same problem. Can you tell me how you fixed this problem? I read and followed the guide on Linuxserver.io but I can't find the problem for this error. Also, I can only open the nextcloud URL with the server.com/nextcloud instead of nextcloud.server.com.

 

I used nextcloud on my old server with openmediavault and I'm new on unraid so I'm sorry for asking so many questions :D.

 

 

@aptalca has changed the LE container a little to keep things up to date.

 

Try changing the Nextcloud letsencrypt server config to:

 

server {
        listen 80;
        server_name nextcloud.server.com;
        return 301 https://nextcloud.server.com$request_uri;
}

server {

	listen 443 ssl;
	server_name nextcloud.server.com;

	root /config/www;
	index index.html index.htm index.php;

	include /config/nginx/ssl.conf;

	client_max_body_size 0;

	location / {
    	proxy_pass https://192.168.0.1:444/;
	proxy_max_temp_file_size 2048m;
	include /config/nginx/proxy.conf;
  	}
}

 

Link to comment

Thank you CHBMB for your help! I think the problem is my DNS provider. I can't point to the domain nextcloud.mydns.com (just an example). It only works with mydns.com/nextcloud.

So can you recommend a good (maybe free) DNS provider?

 

Edit: the problem (headers) in my old post are fixed, thanks! Now I'm only not able to install apps like the calendar for example :-/.

Edited by CreZo
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.