13 hours ago, trurl said:

That's fine. I do the same thing.

 

That's OK too. If you want you can set it to cache-yes, run mover (Main - Array Operations - Move Now) to get it moved to the array, then set it to cache-no.

 

Thanks for confirming that it's ok! I've done your suggestion and run mover, I also deleted the Apple sparse.bundle and hey presto time machine is now doing a new back-up!

 

Now I just need to fix Nextcloud!

Thanks

Tim

3 hours ago, Kaizac said:

 

Regarding your nextcloud it seems like you are running another docker on port 443. So you can change the port on Nextcloud or on the other docker.

Ok, you can obviously see something that I can't as I can't see any other docker on port 443?

5 minutes ago, MothyTim said:

Ok, you can obviously see something that I can't as I can't see any other docker on port 443?

It was in your log:

listen tcp 0.0.0.0:443: bind: address already in use.

So maybe it's your LE docker that is on port 443? Or maybe you have your https WebUI of Unraid on 443? I think if you change the port of Nextcloud to 444 you will find that it will start up fine. You just have to change your nginx config to match the new port.

Edited March 12, 20197 yr by Kaizac

8 minutes ago, Kaizac said:

It was in your log:

listen tcp 0.0.0.0:443: bind: address 

So maybe it's your LE docker that is on port 443? Or maybe you have your https WebUI of Unraid on 443? I think if you change the port of Nextcloud to 444 you will find that it will start up fine. You just have to change your nginx config to match the new port.

Thanks for pointing me in the right direction, it was the Unraid WebUI hadn't thought of that! It seems to be working now, what do I need to change in nginx  config?

5 minutes ago, MothyTim said:

Thanks for pointing me in the right direction, it was the Unraid WebUI hadn't thought of that! It seems to be working now, what do I need to change in nginx  config?

Well depends on your nginx configs. If you pointed to 443 somewhere there and you changed it to 444 you should also change that port in your nginx config for Nextcloud. If you point to your dockername (since you use proxynet) I think you can just leave it as is.

8 minutes ago, Kaizac said:

Well depends on your nginx configs. If you pointed to 443 somewhere there and you changed it to 444 you should also change that port in your nginx config for Nextcloud. If you point to your dockername (since you use proxynet) I think you can just leave it as is.

Ok thanks, all seems to be working, so I'll leave it alone!

 

Cheers,

Tim

1 minute ago, MothyTim said:

Ok thanks, all seems to be working, so I'll leave it alone!

 

Cheers,

Tim

Glad you got it working :).

UnRaid Version: 6.6.7. Just tried a fresh install. Set up a new share called nextcloud, with Use cache disk: Yes. The only application values I changed were to set the Host port to 444 and set the Container path to /mnt/user/nextcloud/

 

The log shows a file error:

 

Thanks, Richard

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
tar: /tmp/nextcloud.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

 

 

 

 

 

7 hours ago, RichardU said:

UnRaid Version: 6.6.7. Just tried a fresh install. Set up a new share called nextcloud, with Use cache disk: Yes. The only application values I changed were to set the Host port to 444 and set the Container path to /mnt/user/nextcloud/

 

The log shows a file error:

 

Thanks, Richard

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
tar: /tmp/nextcloud.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

 

 

 

 

 

Looks like it's not downloading the installation file. 

Post your docker run command. 

4 hours ago, saarg said:

Looks like it's not downloading the installation file. 

Post your docker run command. 

Thanks. I now know where to find the docker run command. Needed to change the port. Cheers.

Hi Everyone, I'm having an odd problem I can't figure out. I'm following Spaceinvaderone's guide to installing Nextcloud and letsencrypt/reverse proxy to connect remotely.

 

I set up the Nextcloud and Mariadb dockers and everything worked fine. But I had to get a new router because my old one wouldn't port forward properly to allow Letsencrypt to generate a certificate. After setting up the new router and getting Letsencrypt to work I can no longer access the Nextcloud WebGUI. The static IPs assigned in the router are the same as before. My other dockers and VMs seem to work fine.

 

When I right click the Nextcloud docker and click WebGUI or when I type in the IP and port manually (https://192.168.1.77:444) I get 'This page isn’t working 192.168.1.77 is currently unable to handle this request. HTTP Error 500'. May not be caused by the router but all the settings seem to be fine.

 

Anyone know what could be causing it and how to fix it? 

1 hour ago, JohnyClassic said:

I can no longer access the Nextcloud WebGUI

what router do you have? for example, in Mikrotik world this feature names Hairpin NAT. Look for similar with your router model. 

Hi Guy's,

Using spaceinvaderone's guide on Nextcloud and Letsencrypt reverse proxy I have things O so close to working but no love! Unraid 6.6.7

 

I have "server ready" in Letsencrypt, using my own domain name with subdomain "nextcloud"

I HAD Nextcloud working via a local connection (ip addy in browser) looking good to there.

 

Ran into trouble where you need to rename letsencrypt/nginx/proxy-config/nextcloud.subdomain.conf.sample to remove 'sample' from the end. Was editing via the CA config editor in unraid. Can not rename with that. I went the route of making the appdata folder public and viewable in smb. Used windows explorer to remove the .sample and saved.

 

Stuck now - trying to access Nextcloud from within the LAN or outside the LAN gives the same "Internal Server error"

 

The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the webserver log.

Letsencrypt log looks good, Nextcloud has the following:

 

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
PHP Fatal error: Uncaught Error: Call to a member function getLogger() on null in /config/www/nextcloud/cron.php:160
Stack trace:

}
thrown in /config/www/nextcloud/cron.php on line 160
PHP Fatal error: Uncaught Error: Call to a member function getLogger() on null in /config/www/nextcloud/cron.php:160

 

Keeps repeating the PHP Fatal error. I'm at a loss, anybody have any insight on this?

 

Thanks!

2 hours ago, R2JJS said:

Keeps repeating the PHP Fatal error. I'm at a loss, anybody have any insight on this?

 

Thanks!

Need to post your LE config and config.php

4 hours ago, uldise said:

what router do you have? for example, in Mikrotik world this feature names Hairpin NAT. Look for similar with your router model. 

Hey, thanks for the reply. I hadn't set up nextcloud to be accessible from the internet yet. It's still set to be accessible via the local network IP. But when I call that local network IP or click webGUI it doesn't connect. According to Spaceinvaderone's video, even once it's set up to be accessible from the internet, you should still be able to access the webGUI calling the local network IP. Do you happen to know if there is anything that could cause that? 

CHBMB

 

I am out of my element here.... believe this is the config.php you are looking for. 

Can you help point me to the letsencrypt config?

config.php

6 hours ago, JohnyClassic said:

Do you happen to know if there is anything that could cause that?

sorry, no mind. i have nextcloud docker, but i have Apache web-server that serves reverse proxy for nextcloud too.

Hello Fellow Unraiders,

 

All of a sudden, my Collabora stopped working with Nextcloud. Both work independently. When I try to open a document, Nextcloud gives the following errors:

Error	PHP	Cannot declare class GuzzleHttp\Handler\CurlFactory, because the name is already in use at /config/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php#15		2019-03-20T14:07:30+0300
Error	richdocuments	GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 5001 milliseconds (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)		2019-03-20T14:07:30+0300
Error	PHP	Undefined offset: 0 at /config/www/nextcloud/lib/private/AppFramework/Http.php#150

And a pop up message on Nextcloud UI says "Failed to load Collabora online. Please try again later." All I did just before this problem was to change the static IP of the server and subdomains on Cloudflare DNS. I am not sure if this is any related with the issue. Nextcloud is setup as subdomain behind letsencrypt docker as outlined in this forum.

 

Does this error ring any bell? Pretty cryptic for me.

 

Thanks.

Did you post in the LE thread as well?

If so I stand by my original assessment.

Sent from my Mi A1 using Tapatalk

18 hours ago, CHBMB said:

Did you post in the LE thread as well?

Yes, I did. I go on the LE thread.

A couple of months ago I found a simple guide of upgrading Nextcloud using the CLI, on unRAID.

I really can't find it again, but I'm pretty sure it was on this forum. Any hints/links?

@Razvan Rosca Login into nextcloud with an admin account. Go to settings >> overview and you should see on the right your current installed version and if an upgrade is available. Is this what you're looking for?

1 hour ago, Razvan Rosca said:

A couple of months ago I found a simple guide of upgrading Nextcloud using the CLI, on unRAID.

I really can't find it again, but I'm pretty sure it was on this forum. Any hints/links?

Did you look at the first post of this thread? The link is right there.

https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=493083

 

On 3/17/2019 at 7:04 PM, R2JJS said:

CHBMB

 

I am out of my element here.... believe this is the config.php you are looking for. 

Can you help point me to the letsencrypt config?

config.php

I'm still stuck on my Nextcloud install. I get the feeling its just some little thing but as I said out of my element.... 

Reviewed everything I did but still getting the "php fatal error" listed above in the NC log.

Now getting a "Welcome to our server" website currently being setup under this address page when trying to access NC from the web.

What exact config files do I need to post?

 

Update March 25  9:20PM EST

My mistake was in not closing a quote on 'overwrite host' when adding the 4 lines to the config file! Follow that up with many other minor tweaks and changes working on the install. I reverted the LE proxy-config BACK to .sample at one point (and forgot)! Looks like I am working now.

Edited March 26, 20197 yr by R2JJS
Resolved!!!

Durp...

 

blindly updating the docker from time to time, never knew to do the upgrade from the GUI... Now I get

This version of Nextcloud is not compatible with PHP 7.2.
You are currently running 7.2.14.

My docker containers (mariadb-nextcloud and nextcloud) are up-to-date, but I guess that does not help.

 

Without a gui, how can I proceed?