[Support] Linuxserver.io - Nextcloud


Recommended Posts

On 12/29/2017 at 2:38 PM, montery said:

First, I would like to thank CHBMB for posting his guide, very well written and informative.

 

My only problem seems to be the nextcloud container logs show this error:


nginx: [emerg] open() "/config/nginx/proxy.conf" failed (2: No such file or directory) in /config/nginx/site-confs/nextcloud:31

Sure enough, I go into the appdata folder for nextcloud and the proxy.conf file is not there.  (Instructions didn't say I should put it there....)

 

My appdata config path for nextcloud points to /mnt/user/appdata/nextcloud

 

I'm wondering if it should instead point to /mnt/user/appdata/letsencrypt?

 

When I put a copy of the proxy.conf file from the letsencrypt container into the nextcloud container, I got 


nginx: [emerg] BIO_new_file("/config/keys/letsencrypt/fullchain.pem") failed (SSL: error:02FFF002:system library:func(4095):No such file or directory:fopen('/config/keys/letsencrypt/fullchain.pem', 'r') error:20FFF080:BIO routines:CRYPTO_internal:no such file)

Should I do this?  Or have I missed a step in my letsencrypt configuration?

LetsEncrypt Unraid Config.PNG

NextCloud Unraid Config.PNG

Having the same issue when I try and move my nextcloud to a subdomain. Same exact error repeating in the logs. Did you find a solution?

Link to comment
19 hours ago, Kash76 said:

***update - apparently my upgrade did not go well. I copied all of the 12.0.5 files over my existing (the new signer certs were missing completely) and now I'm back in business. 

 

I am suddenly getting a "too many redirects" error after login when visiting my instance. I recently upgraded to 12.05 and use LetsEncrypt as a reverse proxy. Any ideas as to what could cause this error?

 

I have the same issue when I disable overwrite.cli.url and overwrite host and access the domain locally without my external LetsEncrypt reverse proxy. 

 

 

Did u upgrade from Docker - via NextCloud web UI?

 

I just wonder if i should upgrade like that ...or there is some new Docker version coming with latest Nextcould release?

 

Thanks

Link to comment

Trying to update to the latest and am getting the following while downloading:

 

Verifying integrity

Parsing response failed. <html> <head><title>504 Gateway Time-out</title></head> <body bgcolor="white"> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.10.1</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
 
any idea how to proceed past this?
Link to comment
9 minutes ago, CHBMB said:

That's because you're not following the guide properly and aren't in the right directory

Sent from my LG-H815 using Tapatalk
 

 

 

Here is the screen capture:

 

root@Tower2:~# docker restart nextcloud
nextcloud
root@Tower2:~# docker exec -it nextcloud bash
root@00091b0a1eca:/$ cd /config/www/nextcloud
root@00091b0a1eca:/config/www/nextcloud$ sudo -u abc php7 occ upgrade
sudo: php7: command not found
root@00091b0a1eca:/config/www/nextcloud$

 

Sorry if I missed a step, but I was trying to follow it... I am sure that I screwed up somewhere but am not sure where...


 

Edited by levster
Link to comment
 
 
Here is the screen capture:
 
root@Tower2:~# docker restart nextcloud
nextcloud
root@Tower2:~# docker exec -it nextcloud bash
root@00091b0a1eca:/$ cd /config/www/nextcloud
root@00091b0a1eca:/config/www/nextcloud$ sudo -u abc php7 occ upgrade
sudo: php7: command not found
root@00091b0a1eca:/config/www/nextcloud$
 
Sorry if I missed a step, but I was trying to follow it... I am sure that I screwed up somewhere but am not sure where...

 
Is your container up to date? We changed from php5 to 7 a long time ago now....

Sent from my LG-H815 using Tapatalk

Link to comment
1 minute ago, CHBMB said:

Is your container up to date? We changed from php5 to 7 a long time ago now....

Sent from my LG-H815 using Tapatalk
 

I am not sure. I always upgraded via the GUI so not sure what that is. How do I update the container to the latest?

 

Edited by levster
Link to comment
2 hours ago, CHBMB said:

Edit the container and change lsiodev to linuxserver....

Sent from my LG-H815 using Tapatalk
 

OK. changed the container to linuxserver. I was able to upgrade via the command line. Great!!! Thank you for the help.

 

Now, the following:

failed.txt

Edited by levster
Link to comment
16 hours ago, daniel329 said:

Having the same issue when I try and move my nextcloud to a subdomain. Same exact error repeating in the logs. Did you find a solution?

Nope, I ended up removing the app and upgraded to 6.4.  Haven't had the opportunity yet to try again.  I'm hoping a new guide will be written with 6.4 in mind. 9_9

Link to comment
Nope, I ended up removing the app and upgraded to 6.4.  Haven't had the opportunity yet to try again.  I'm hoping a new guide will be written with 6.4 in mind. 
It won't as nothing has changed. I installed an instance of Nextcloud yesterday using the guide.

Sent from my LG-H815 using Tapatalk

Link to comment
On 29/01/2018 at 12:15 AM, levster said:

OK. changed the container to linuxserver. I was able to upgrade via the command line. Great!!! Thank you for the help.

 

Now, the following:

failed.txt

 

No idea Lev, I'm afraid, probably remnants of your old install.  Check all your apps are up to date for a start then see what happens.

Link to comment
2 hours ago, uldise said:

i did not install any additional apache - i have one apache server on my ubuntu VM, which hosts all internal subdomains via reverse proxies, including Nextcload, Collabora, and all other domain's i host. 

ok, I tried doing this via Let's Encrypt.  I did a bit of googling and I found a config file that 'works' - I can edit docs in Nextcloud, but I can't access the collabora docker at office.mydomain.com although I can via the docker url.  Happy as I can meet the primary objective, but if anyone can explain why config file for office is wrong please I'll be even happier:

server {
	listen 443 ssl;
	server_name office.mydomain.com;

# SSL settings
	ssl_certificate /config/keys/letsencrypt/fullchain.pem;
	ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
	ssl_dhparam /config/nginx/dhparams.pem;
	ssl_protocols TLSv1.2;
	
	ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
	ssl_prefer_server_ciphers on;

	client_max_body_size 0;
	
# static files
	location ^~ /loleaflet {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# WOPI discovery URL
	location ^~ /hosting/discovery {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# main websocket
	location ~ ^/lool/(.*)/ws$ {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "Upgrade";
		proxy_set_header Host $http_host;
		proxy_read_timeout 36000s;
	}

# download, presentation and image upload
	location ~ ^/lool {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Host $http_host;
	}

# Admin Console websocket
	location ^~ /lool/adminws {
		proxy_pass https://192.168.50.74:9980;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection "Upgrade";
		proxy_set_header Host $http_host;
		proxy_read_timeout 36000s;
	}
}

5a7053ce141d4_FireShotCapture52-Welcometonginx!-https___office.the-shepherds.com_.thumb.png.196a86875c1aa900d3482eaa52c824b2.png

Link to comment
5 minutes ago, DZMM said:

I can edit docs in Nextcloud, but I can't access the collabora docker at office.mydomain.com although I can via the docker url.

if i access my Collabora via docker url, it just display blank page with text "OK" in the left corner :)

so, via Collabora i can edit docs form Nextcloud too, so that it is..

  • Like 1
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.