[Support] Linuxserver.io - Nextcloud

For all linuxserver containers, the best place to ask for help is via their Discord (Click on the container in question and select Discord)

Recommended by Squid

iXNyNe

July 5, 20233 yr

updater.phar has been removed from the latest releases. The update process has been built into the container image, so updating the container will perform the update to nextcloud itself going forward. If you are currently running the latest image without issues, then you don't need to take any action. If you have updated to the latest image and nextcloud is not working this post has all the info you should need https://info.linuxserver.io/issues/2023-06-25-nextcloud/ and if you follo

Recommended by JonathanM

iXNyNe

June 25, 20233 yr

This is expected. Please read https://info.linuxserver.io/issues/2023-06-25-nextcloud/ tldr; no more manual updates

Recommended by JonathanM

First page
Prev
2
3
4
5
6
7
8
9
10
11
12
Next
Last page

August 17, 20169 yr

Any chance of getting Postgres support added to the Docker? I'm running MariaDB just for this container, while everything else can use Postgres. Pretty sure all you need is the php5-pgsql package (Postgres will show up in the setup wizard once the extension is properly enabled).

lol, damnit, it was in, i took it out because i thought i had put two copies in the dependency list, turns out i didn't...

putting it back in again.

Quote

Replies 7.1k
Views 1.7m
Created 10 yr10 yr
Last Reply Jun 27Jun 27

Popular Days

Posted Images

August 22, 20169 yr

Is this and the config from https://www.linuxserver.io/index.php/2016/07/28/installing-nextcloud-on-unraid/ not working for anyone else all of a sudden. A week or so ago it was working just fine, but now it is broken. I have updated and changed several things on my network and system since then (Router firmware, Unraid version, container updates, etc) and I am struggling to figure out what is breaking this for me.

If i try server.com/nextcloud, it just doesn't load period. If I try https://192.168.1.130:444/, it loads, but without CSS, so nothing works and I can't log in.

I know this container is under active development, so if that's what broke it, that's fine. But if something on my end with my config broke it, I'd like to try to solve the problem.

Quote

August 22, 20169 yr

Is this and the config from https://www.linuxserver.io/index.php/2016/07/28/installing-nextcloud-on-unraid/ not working for anyone else all of a sudden. A week or so ago it was working just fine, but now it is broken. I have updated and changed several things on my network and system since then (Router firmware, Unraid version, container updates, etc) and I am struggling to figure out what is breaking this for me.

If i try server.com/nextcloud, it just doesn't load period. If I try https://192.168.1.130:444/, it loads, but without CSS, so nothing works and I can't log in.

I know this container is under active development, so if that's what broke it, that's fine. But if something on my end with my config broke it, I'd like to try to solve the problem.

server.com/nextcloud

suggests to me reverse proxy, something not right there would be my best bet.

Quote

August 22, 20169 yr

Yeah, I thought so too. But all of my troubleshooting has found nothing of relevance. My config hasn't changed since when it was working, and i followed the linked guide exactly.

I was hoping some sort of changes to the nginx built into the nextcloud container itself was causing the issues.

Quote

August 22, 20169 yr

Is this and the config from https://www.linuxserver.io/index.php/2016/07/28/installing-nextcloud-on-unraid/ not working for anyone else all of a sudden. A week or so ago it was working just fine, but now it is broken. I have updated and changed several things on my network and system since then (Router firmware, Unraid version, container updates, etc) and I am struggling to figure out what is breaking this for me.

If i try server.com/nextcloud, it just doesn't load period. If I try https://192.168.1.130:444/, it loads, but without CSS, so nothing works and I can't log in.

I know this container is under active development, so if that's what broke it, that's fine. But if something on my end with my config broke it, I'd like to try to solve the problem.

I actually wonder whether it's your config.php....

Bottom line, without posting your default.conf from Apache and your config.php from nextcloud we're in the dark. I'm using this container without any problems fwiw.

Post the above (remember to edit out any personal info) and I'll take a look.

Quote

August 22, 20169 yr

config.php:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'xxxxxxxxxxxx',
  'passwordsalt' => 'xxxxxxxxxxxxxxxx',
  'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
  'trusted_domains' => 
  array (
    0 => '192.168.1.130:444',
1 => 'XYZ.duckdns.org',
  ),
  'overwrite.cli.url' => 'https://xxx.duckdns.org',
  'overwritehost'     => 'xxx.duckdns.org',
  'overwriteprotocol' => 'https',
  'overwritewebroot'  => '/nextcloud',
  'dbtype' => 'mysql',
  'version' => '9.0.53.0',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.130:3332',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'oc_xxx',
  'dbpassword' => 'GCPEvls3CG97rHIDSlqA9UOiZV9KE2',
  'logtimezone' => 'UTC',
  'installed' => true,
);

default.conf:

<VirtualHost *:80>
    ServerName xxx.duckdns.org
    ServerAlias xxx.duckdns.org
DocumentRoot /config/www/

Redirect permanent / https://www.xxx.duckdns.org/

</VirtualHost>

<VirtualHost *:443>
    ServerName xxx.duckdns.org
ServerAdmin webmaster@localhost
    DocumentRoot /config/www/

SSLCertificateFile /config/keys/certificate.crt
    SSLCertificateKeyFile /config/keys/decrypted.cert.key
    SSLCertificateChainFile /config/keys/intermediate.crt
Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"

SSLEngine on
    SSLProxyEngine On
    RewriteEngine On
    ProxyPreserveHost Off

    SSLProxyVerify none
    SSLProxyCheckPeerCN off
    SSLProxyCheckPeerName off
    SSLProxyCheckPeerExpire off

    SSLProtocol -All +TLSv1 +TLSv1.1 +TLSv1.2
    SSLCipherSuite ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS
    SSLHonorCipherOrder on

    <Location /nextcloud>
        ProxyPass https://192.168.1.130:444
        ProxyPassReverse https://192.168.1.130:444
    </Location>

</VirtualHost>

All "xxx" and longer strings are edited from the original

Quote

August 22, 20169 yr

Nothing stands out there, you checked the Apache logs?

Quote

August 22, 20169 yr

Yeah, nothing there that wasn't there a few weeks ago.

Error.log

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:31:56.518469 2016] [:notice] [pid 168] FastCGI: process manager initialized (pid 168)
[Mon Aug 22 09:31:56.528012 2016] [core:warn] [pid 167] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Aug 22 09:31:56.529643 2016] [mpm_prefork:notice] [pid 167] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:31:56.529658 2016] [core:notice] [pid 167] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:47:18.645650 2016] [:notice] [pid 154] FastCGI: process manager initialized (pid 154)
[Mon Aug 22 09:47:18.654940 2016] [core:warn] [pid 148] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Aug 22 09:47:18.656730 2016] [mpm_prefork:notice] [pid 148] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:47:18.656758 2016] [core:notice] [pid 148] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:57:26.399929 2016] [:notice] [pid 4423] FastCGI: process manager initialized (pid 4423)
[Mon Aug 22 09:57:26.410817 2016] [mpm_prefork:notice] [pid 4418] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:57:26.410839 2016] [core:notice] [pid 4418] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
[Mon Aug 22 10:44:31.414431 2016] [mpm_prefork:notice] [pid 4418] AH00169: caught SIGTERM, shutting down
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 10:47:51.104184 2016] [:notice] [pid 155] FastCGI: process manager initialized (pid 155)
[Mon Aug 22 10:47:51.116122 2016] [mpm_prefork:notice] [pid 151] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 10:47:51.116148 2016] [core:notice] [pid 151] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'

The ServerName issue has been around since I got it working, so I didn't think that was a problem.

Quote

August 22, 20169 yr

Yeah, nothing there that wasn't there a few weeks ago.

Error.log

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:31:56.518469 2016] [:notice] [pid 168] FastCGI: process manager initialized (pid 168)
[Mon Aug 22 09:31:56.528012 2016] [core:warn] [pid 167] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Aug 22 09:31:56.529643 2016] [mpm_prefork:notice] [pid 167] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:31:56.529658 2016] [core:notice] [pid 167] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:47:18.645650 2016] [:notice] [pid 154] FastCGI: process manager initialized (pid 154)
[Mon Aug 22 09:47:18.654940 2016] [core:warn] [pid 148] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Aug 22 09:47:18.656730 2016] [mpm_prefork:notice] [pid 148] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:47:18.656758 2016] [core:notice] [pid 148] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 09:57:26.399929 2016] [:notice] [pid 4423] FastCGI: process manager initialized (pid 4423)
[Mon Aug 22 09:57:26.410817 2016] [mpm_prefork:notice] [pid 4418] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 09:57:26.410839 2016] [core:notice] [pid 4418] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
[Mon Aug 22 10:44:31.414431 2016] [mpm_prefork:notice] [pid 4418] AH00169: caught SIGTERM, shutting down
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
[Mon Aug 22 10:47:51.104184 2016] [:notice] [pid 155] FastCGI: process manager initialized (pid 155)
[Mon Aug 22 10:47:51.116122 2016] [mpm_prefork:notice] [pid 151] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.19 OpenSSL/1.0.1f configured -- resuming normal operations
[Mon Aug 22 10:47:51.116148 2016] [core:notice] [pid 151] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'

The ServerName issue has been around since I got it working, so I didn't think that was a problem.

What about the Apache docker log? And you 100% sure that your dynamic DNS is being updated correctly?

Quote

August 22, 20169 yr

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

Brought to you by linuxserver.io
We do accept donations at:
https://www.linuxserver.io/donations
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

*** Running /etc/my_init.d/20_apt_update.sh...
finding fastest mirror
Getting list of mirrors...done.
Testing latency to mirror(s)
Getting list of launchpad URLs...done.
Looking up 3 status(es)
1. dist1.800hosting.com
Latency: 15.15 ms
Org: 1-800-hosting
Status: Up to date
Speed: 100 Mbps
2. mirror.lstn.net (current)
Latency: 17.31 ms
Org: Limestone Networks
Status: Up to date
Speed: 2 Gbps
3. www.gtlib.gatech.edu
Latency: 32.75 ms
Org: Georgia Tech. Software Library
Status: Up to date
Speed: 1 Gbps
New config file saved to /defaults/sources.list
We are now refreshing packages from apt repositories, this *may* take a while
Ign http://dist1.800hosting.com trusty InRelease
Get:1 http://dist1.800hosting.com trusty-updates InRelease [65.9 kB]
Get:2 http://dist1.800hosting.com trusty-security InRelease [65.9 kB]
Get:3 http://dist1.800hosting.com trusty Release.gpg [933 B]
Get:4 http://dist1.800hosting.com trusty-updates/main Sources [471 kB]
Get:5 http://dist1.800hosting.com trusty-updates/restricted Sources [5,247 B]
Get:6 http://dist1.800hosting.com trusty-updates/universe Sources [201 kB]
Get:7 http://dist1.800hosting.com trusty-updates/multiverse Sources [6,927 B]
Get:8 http://dist1.800hosting.com trusty-updates/main amd64 Packages [1,106 kB]
Get:9 http://dist1.800hosting.com trusty-updates/restricted amd64 Packages [23.5 kB]
Get:10 http://dist1.800hosting.com trusty-updates/universe amd64 Packages [474 kB]
Get:11 http://dist1.800hosting.com trusty-updates/multiverse amd64 Packages [16.1 kB]
Get:12 http://dist1.800hosting.com trusty-security/main Sources [150 kB]
Get:13 http://dist1.800hosting.com trusty-security/restricted Sources [3,944 B]
Get:14 http://dist1.800hosting.com trusty-security/universe Sources [44.1 kB]
Get:15 http://dist1.800hosting.com trusty-security/multiverse Sources [2,550 B]
Get:16 http://dist1.800hosting.com trusty-security/main amd64 Packages [645 kB]
Get:17 http://dist1.800hosting.com trusty-security/restricted amd64 Packages [20.2 kB]
Get:18 http://dist1.800hosting.com trusty-security/universe amd64 Packages [170 kB]
Get:19 http://dist1.800hosting.com trusty-security/multiverse amd64 Packages [4,850 B]
Get:20 http://dist1.800hosting.com trusty Release [58.5 kB]
Get:21 http://dist1.800hosting.com trusty/main Sources [1,335 kB]
Get:22 http://dist1.800hosting.com trusty/restricted Sources [5,335 B]
Get:23 http://dist1.800hosting.com trusty/universe Sources [7,926 kB]
Get:24 http://dist1.800hosting.com trusty/multiverse Sources [211 kB]
Get:25 http://dist1.800hosting.com trusty/main amd64 Packages [1,743 kB]
Get:26 http://dist1.800hosting.com trusty/restricted amd64 Packages [16.0 kB]
Get:27 http://dist1.800hosting.com trusty/universe amd64 Packages [7,589 kB]
Get:28 http://dist1.800hosting.com trusty/multiverse amd64 Packages [169 kB]
Fetched 22.5 MB in 3s (6,266 kB/s)
Reading package lists...
*** Running /etc/my_init.d/30_set_base_config.sh...
*** Running /etc/my_init.d/40_gen_ssl_keys.sh...
using keys found in /config/keys
*** Running /etc/my_init.d/999_advanced_script.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 134
Aug 22 15:04:40 5294e73ab362 syslog-ng[146]: syslog-ng starting up; version='3.5.3'

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.10. Set the 'ServerName' directive globally to suppress this message
Setting up watches.
Watches established.

The DDNS is definitely working fine. I am able to connect to my VPN without issue with that as the IP. I also verified it was accurate and up to date on the duckdns.org website.

Quote

August 22, 20169 yr

I'm at a complete loss with this.

I normally run mine on nextcloud.server.com but just edited my configs to run it on server.com/nextcloud with no problems.

The fact you can actually access it on your LAN, suggests that it has to be either an Apache problem or a dynamic DNS issue, but I don't know what else to suggest.

Quote

August 24, 20169 yr

Hi, I've got everything setup, but I'm trying to get the docker to play nice with my existing nginx/letsencrypt docker from aptalca. Are there changes I need to make to nextcloud's nginx to have it work? I'd really like to be able to access it via nextcloud.domain.com

Even just implementing a proxypass in my existing setup returns "400 Bad Request - The plain HTTP request was sent to HTTPS port"

I'm pretty new to reverse proxy world and I'm not sure where I'm going wrong.

Quote

August 24, 20169 yr

Without you posting your config it's impossible to say. But you're trying to send a http request to a https port which is a clue. You may have left an "s" out somewhere.

Quote

August 24, 20169 yr

Without you posting your config it's impossible to say. But you're trying to send a http request to a https port which is a clue. You may have left an "s" out somewhere.

Sorry! Attached

default.txt

Quote

August 24, 20169 yr

Without you posting your config it's impossible to say. But you're trying to send a http request to a https port which is a clue. You may have left an "s" out somewhere.

Sorry! Attached

	location /cloud {
	proxy_pass http://172.16.100.5:8443/cloud;	
	}
}

http should be https like the error says. Other than that I can't say anymore as I don't use nginx

Quote

August 24, 20169 yr

Without you posting your config it's impossible to say. But you're trying to send a http request to a https port which is a clue. You may have left an "s" out somewhere.

Sorry! Attached
	location /cloud {
	proxy_pass http://172.16.100.5:8443/cloud;	
	}
}
http should be https like the error says. Other than that I can't say anymore as I don't use nginx

Yeah...no dice with that one. Funny though, I didn't have the s on it for my other locations, but still was presented with basic auth when connecting to them. I'll keep at it! Thank you

Quote

August 24, 20169 yr

Other locations may not connect with https though, which nextcloud does. Also don't try and layer auth on top of what nextcloud is providing.

Quote

August 24, 20169 yr

@noja,

When you enter https://172.16.100.5:8443/cloud in a browser, do you get to the nextcloud login screen?

Quote

August 24, 20169 yr

@noja,

When you enter https://172.16.100.5:8443/cloud in a browser, do you get to the nextcloud login screen?

Actually, it just takes me to a location within nextcloud - not the login screen at all

@CHBMB - I remember I actually left the ssl off as I was thinking about not trying to overlay auth types - same reason i left it off on my library - already had authentication there.

Quote

August 24, 20169 yr

@nojas,

I think you need to enter the URL of the login screen

Quote

August 24, 20169 yr

@noja,

When you enter https://172.16.100.5:8443/cloud in a browser, do you get to the nextcloud login screen?

Actually, it just takes me to a location within nextcloud - not the login screen at all

@CHBMB - I remember I actually left the ssl off as I was thinking about not trying to overlay auth types - same reason i left it off on my library - already had authentication there.

I find sometimes with my Nextcloud that my login is cached and it takes me straight into the app bypassing the login screen.

Quote

August 24, 20169 yr

@chbmb

Did you make any changes to nextcloud's config.php to make it work behind the letsencrypt reverse proxy?

Quote

August 24, 20169 yr

@chbmb

Did you make any changes to nextcloud's config.php to make it work behind the letsencrypt reverse proxy?

I've never used the letsencrypt reverse proxy.....

Quote

August 27, 20169 yr

So not sure what is happening, but I set up Nextcloud and never really messed with it. I just logged into the Nextcloud account through the login screen at home and tried to upload a file. It keeps saying "Upload failed, cannot find the uploaded file". I also tried using the Nextcloud ios app and while I can connect to the server, I cannot upload files. It keeps telling me that I dont have permission or something like that. Should I post my config file? I posted the log from Nextcloud.

owncloud.log.txt

Quote

August 28, 20169 yr

Sure your database is up?

Do these paths exist?

Yes post your config, both docker and config.php

Quote

First page
Prev
2
3
4
5
6
7
8
9
10
11
12
Next
Last page

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.

Followers

Go to topic listing

Replies 7.1k
Views 1.7m
Created 10 yr10 yr
Last Reply Jun 27Jun 27

[Support] Linuxserver.io - Nextcloud

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

CHBMB

Konijntjes

gustomucho

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

CHBMB

Konijntjes

gustomucho

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)