[Support] Linuxserver.io - Nextcloud

CHBMB · February 12, 2017

Should look like this..

Yes, I went past this prompt; however, the original password used during the setup of Mariadb was not accessible. I had to leave the password blank and hit enter to get to this prompt.

Sent from my SM-G935V using Tapatalk

I'm confused, you'd only see this screen if the password was correct when you entered it.

levster · February 12, 2017

Should look like this..

Yes, I went past this prompt; however, the original password used during the setup of Mariadb was not accessible. I had to leave the password blank and hit enter to get to this prompt.

Sent from my SM-G935V using Tapatalk

I'm confused, you'd only see this screen if the password was correct when you entered it.

Well, I guess I'm just as confused. I could not pass it with the original password, and I tried it twice, wiping out the entire Mariadb and Nextcloud containers, including the leftover folders.

Sent from my SM-G935V using Tapatalk

CHBMB · February 12, 2017

Should look like this..

Yes, I went past this prompt; however, the original password used during the setup of Mariadb was not accessible. I had to leave the password blank and hit enter to get to this prompt.

Sent from my SM-G935V using Tapatalk

I'm confused, you'd only see this screen if the password was correct when you entered it.

Well, I guess I'm just as confused. I could not pass it with the original password, and I tried it twice, wiping out the entire Mariadb and Nextcloud containers, including the leftover folders.

Sent from my SM-G935V using Tapatalk

Only other thing I can think of is once you set the MariaDB root password in the template on the initial pull you can't change it afterwards by changing the template. It ONLY works that initial time.

EDIT: The other problem I've seen with this is people not including the semi-colons at the end of the mysql commands here.

levster · February 12, 2017

Should look like this..

Yes, I went past this prompt; however, the original password used during the setup of Mariadb was not accessible. I had to leave the password blank and hit enter to get to this prompt.

Sent from my SM-G935V using Tapatalk

I'm confused, you'd only see this screen if the password was correct when you entered it.

Well, I guess I'm just as confused. I could not pass it with the original password, and I tried it twice, wiping out the entire Mariadb and Nextcloud containers, including the leftover folders.

Sent from my SM-G935V using Tapatalk

Only other thing I can think of is once you set the MariaDB root password in the template on the initial pull you can't change it afterwards by changing the template. It ONLY works that initial time.

EDIT: The other problem I've seen with this is people not including the semi-colons at the end of the mysql commands here.

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

I just checked the MariaDB install and the password is there. I am using "root" as the Database user. Password created during the initial MariaDB install, nextcloud as the Database name. IP as shown on the MariaDB IP:port on the Docker page.

CHBMB · February 12, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

levster · February 12, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

Uh oh.... I feel a little bit embarrassed... I left the string as is...

Sent from my SM-G935V using Tapatalk

CHBMB · February 12, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

Uh oh.... I feel a little bit embarrassed... I left the string as is...

If it makes you feel better, you're not the first....

vurt · February 12, 2017

I started enquiring about this in the Letsencrypt thread but now think it might be a NextCloud issue.

I've installed it and can confirm it runs fine when I access it via its internal IP of 192.168.1.252:444.

But when I reverse proxy it with Letsencrypt, https://server.com/nextcloud/ takes a very long time to open. And when it finally opens and I enter my login, the webpage hangs for a while and eventually returns a 504 Gateway Time-out error.

This was my NextCloud config:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'oc5tpjrjiliz',
  'passwordsalt' => '7iiEZcRX0TmIANc8q1CB1ZO3pRrAhd',
  'secret' => 'xNhed76LWYKrFfde7LL0W0rKz18PBHu62KoXYHmKxQg7YvU8',
  'trusted_domains' => 
  array (
    0 => '192.168.1.252:444',
    1 => 'advurt.net',
  ),
  'overwrite.cli.url' => 'https://advurt.net',
  'overwritehost'     => 'advurt.net',
  'overwriteprotocol' => 'https',
  'overwritewebroot'  => '/nextcloud',


  'dbtype' => 'mysql',
  'version' => '11.0.1.2',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.252:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'oc_ray',
  'dbpassword' => 'V781F3CLEyYO59J6Jc7fJhprhVTzQ5',
  'logtimezone' => 'UTC',
  'installed' => true,
);

And this is Letsencrypt:

# redirect all traffic to https
server {
listen 80;
server_name _;
return 301 https://$host$request_uri;
}

# main server block
server {
listen 443 ssl default_server;

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

server_name _;

ssl_certificate /config/keys/letsencrypt/fullchain.pem;
ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
ssl_dhparam /config/nginx/dhparams.pem;
ssl_ciphers 'xxxxxxxxxxxx';
ssl_prefer_server_ciphers on;

client_max_body_size 0;

location / {
	try_files $uri $uri/ /index.html /index.php?$args =404;
}

location ~ \.php$ {
	fastcgi_split_path_info ^(.+\.php)(/.+)$;
	# With php5-cgi alone:
	fastcgi_pass 127.0.0.1:9000;
	# With php5-fpm:
	#fastcgi_pass unix:/var/run/php5-fpm.sock;
	fastcgi_index index.php;
	include /etc/nginx/fastcgi_params;
}

#Config for NextCloud
	location ^~ /nextcloud {
		auth_basic "Restricted";
		auth_basic_user_file /config/nginx/.htpasswd;
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/;
	}

CHBMB · February 12, 2017

I would remove the auth for this actually and allow nextcloud to do it's own thing.

Sent from my LG-H815 using Tapatalk

vurt · February 12, 2017

I would remove the auth for this actually and allow nextcloud to do it's own thing.

Sent from my LG-H815 using Tapatalk

I am trying this but getting the same slow loading and time-out:

#Config for NextCloud
	location ^~ /nextcloud {
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/;
	}

I tried this, which is wrong but the site immediately returns me an error, no lag at all:

#Config for NextCloud
	location ^~ /nextcloud {
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/nextcloud/;
	}

Error:

File not found
The specified document has not been found on the server.
You can click here to return to Nextcloud.

CHBMB · February 12, 2017

Tried this without the trailing slash?

#Config for NextCloud
	location ^~ /nextcloud {
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/nextcloud;
	}

vurt · February 13, 2017

Tried this without the trailing slash?

#Config for NextCloud
	location ^~ /nextcloud {
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/nextcloud;
	}

Just did, same file not found error, but no lag.

CHBMB · February 13, 2017

Tried this without the trailing slash?
#Config for NextCloud
	location ^~ /nextcloud {
		include /config/nginx/proxy.conf;
		proxy_pass https://192.168.1.252:444/nextcloud;
	}
You restarting letsencrypt after all these changes?

Just did, same file not found error, but no lag.

vurt · February 13, 2017

You restarting letsencrypt after all these changes?

Yup, after every change is saved, restarting the dockers and testing.

EDIT:

I'll uninstall and try a fresh start again. I don't think I'm doing anything out of the norm, this is really perplexing.

CHBMB · February 13, 2017

You restarting letsencrypt after all these changes?

Yup, after every change is saved, restarting the dockers and testing.

EDIT:

I'll uninstall and try a fresh start again. I don't think I'm doing anything out of the norm, this is really perplexing.

Try removing the proxy.conf reference

vurt · February 13, 2017

I reinstalled MariaDB, and reinstalled Nextcloud.

I've connected to Nextcloud at https://192.168.1.252:448/ and set up my admin account.

Will attempt reverse proxy again.

CHBMB · February 13, 2017

I reinstalled MariaDB, and reinstalled Nextcloud.

I've connected to Nextcloud at https://192.168.1.252:448/ and set up my admin account.

Will attempt reverse proxy again.

OK, but I think that was unnecessary. FWIW others seem to have it working just using something like this

       location /nextcloud {
                proxy_pass https://192.168.0.190:446/nextcloud;
                }

And although I use nextcloud.server.com I use something simple like this

	location / {
    		proxy_pass https://192.168.0.1:444/;
  }

vurt · February 13, 2017

Currently have:

#Config for Nextcloud
location /nextcloud {
        proxy_pass https://192.168.0.190:448/nextcloud;
    }

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'xxx',
  'passwordsalt' => 'xxx',
  'secret' => 'xxx',
  'trusted_domains' => 
  array (
    0 => '192.168.1.252:448',
1 => 'advurt.net',
  ),
  'overwrite.cli.url' => 'https://advurt.net',
  'overwritehost'     => 'advurt.net',
  'overwriteprotocol' => 'https',
  'overwritewebroot'  => '/nextcloud',
  'dbtype' => 'mysql',
  'version' => '11.0.1.2',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.252:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'xxx',
  'dbpassword' => 'xxx',
  'logtimezone' => 'UTC',
  'installed' => true,
);

Getting a 504 Gateway Time-out.

I don't understand the errors I'm getting. Initially it took forever to get to the login page, and then logging in would time out.

Now I can't get to the login page at all, it simply times out.

So my other reverse proxies are working, can't be Letsencrypt that's not working. It's either Nextcloud or the way I'm setting up the reverse proxy.

Removing all the reverse proxy stuff from Nextcloud and Letsencrypt, gets me back into Nextcloud with 192.168.1.252:448.

I'm just trying to let a friend download files from an unraid share. Is there a simpler option that uses a web interface without installing a client the way VPN would require?

levster · February 13, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

Uh oh.... I feel a little bit embarrassed... I left the string as is...

If it makes you feel better, you're not the first....

OK, so I removed both MariaDB and NC. Reinstalled MD with the correct parameters, and a new password. When running the

CREATE DATABASE IF NOT EXISTS nextcloud;
GRANT ALL PRIVILEGES ON nextcloud.* TO 'root'@'localhost' IDENTIFIED BY '$MARIADB-ROOT-PASSWORD';

I used the correct, matching password. Installed NC. Now, when I try to go to the WebUI, I get "This site can’t be reached 192.168.1.131 refused to connect." I see the correct NC logo on the tab, but the page does not load.

I am confused. I did not really change anything else.

CHBMB · February 13, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

Uh oh.... I feel a little bit embarrassed... I left the string as is...

If it makes you feel better, you're not the first....

OK, so I removed both MariaDB and NC. Reinstalled MD with the correct parameters, and a new password. When running the

CREATE DATABASE IF NOT EXISTS nextcloud;
GRANT ALL PRIVILEGES ON nextcloud.* TO 'root'@'localhost' IDENTIFIED BY '$MARIADB-ROOT-PASSWORD';

I used the correct, matching password. Installed NC. Now, when I try to go to the WebUI, I get "This site can’t be reached 192.168.1.131 refused to connect." I see the correct NC logo on the tab, but the page does not load.

I am confused. I did not really change anything else.

I really do not know what else to suggest. I just did a fresh install to check the instructions inside of five minutes. Definitely working. Have you checked the logs of both containers and cleared your browser cache?

CHBMB · February 13, 2017

Currently have:
#Config for Nextcloud
location /nextcloud {
        proxy_pass https://192.168.0.190:448/nextcloud;
    }
<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'xxx',
  'passwordsalt' => 'xxx',
  'secret' => 'xxx',
  'trusted_domains' => 
  array (
    0 => '192.168.1.252:448',
1 => 'advurt.net',
  ),
  'overwrite.cli.url' => 'https://advurt.net',
  'overwritehost'     => 'advurt.net',
  'overwriteprotocol' => 'https',
  'overwritewebroot'  => '/nextcloud',
  'dbtype' => 'mysql',
  'version' => '11.0.1.2',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.252:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'xxx',
  'dbpassword' => 'xxx',
  'logtimezone' => 'UTC',
  'installed' => true,
);
Getting a 504 Gateway Time-out.

I don't understand the errors I'm getting. Initially it took forever to get to the login page, and then logging in would time out.

Now I can't get to the login page at all, it simply times out.

So my other reverse proxies are working, can't be Letsencrypt that's not working. It's either Nextcloud or the way I'm setting up the reverse proxy.

Removing all the reverse proxy stuff from Nextcloud and Letsencrypt, gets me back into Nextcloud with 192.168.1.252:448.

I'm just trying to let a friend download files from an unraid share. Is there a simpler option that uses a web interface without installing a client the way VPN would require?

To be honest this is exactly why I recommend setting up nextcloud on a subdomain like nextcloud.server.com

I don't run nextcloud as server.com/nextcloud so hopefully someone who does will chime in with what's working for them,

If however you want to get it working as server.com/nextcloud then first get it working as https://192.168.1.252:448/nextcloud before you tackle the proxy

EDIT: Figured it out go to your NEXTCLOUD appdata and edit /config/site-confs/default and change line 30 from

root /config/www/nextcloud/;

to

root /config/www;

then that should work with the above. Don't forget to clear your browser cache and cookies.

levster · February 13, 2017

I copied the entire prompt, including the ";". I saw that as an issue in one of the previous posts...

When you say you copied the entire prompt, you did edit it before using right? Changing $MARIADB-ROOT-PASSWORD to your actual password?

EDIT: Also there's an error in my instructions should be chmod rather than chown, which I've now changed.

Uh oh.... I feel a little bit embarrassed... I left the string as is...

If it makes you feel better, you're not the first....

OK, so I removed both MariaDB and NC. Reinstalled MD with the correct parameters, and a new password. When running the

CREATE DATABASE IF NOT EXISTS nextcloud;
GRANT ALL PRIVILEGES ON nextcloud.* TO 'root'@'localhost' IDENTIFIED BY '$MARIADB-ROOT-PASSWORD';

I used the correct, matching password. Installed NC. Now, when I try to go to the WebUI, I get "This site can’t be reached 192.168.1.131 refused to connect." I see the correct NC logo on the tab, but the page does not load.

I am confused. I did not really change anything else.

I really do not know what else to suggest. I just did a fresh install to check the instructions inside of five minutes. Definitely working. Have you checked the logs of both containers and cleared your browser cache?

I guess I just needed to wait a few minutes, because subsequently I was able to get to the create admin screen. Now, new error message

CHBMB · February 13, 2017

You haven't enabled binlogging in custom.cnf

Did you remove the # as well as change it to mixed?

Sent from my LG-H815 using Tapatalk

levster · February 13, 2017

You haven't enabled binlogging in custom.cnf

Did you remove the # as well as change it to mixed?

Sent from my LG-H815 using Tapatalk

I changed the binlog format to mixed, but did not remove the "#" in front of it. Did not notice that. Thank you. I'll redo all now.

CHBMB · February 13, 2017

Don't forget to remove the # in front of the other line as well.

Sent from my LG-H815 using Tapatalk

[Support] Linuxserver.io - Nextcloud

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

linuxserver.io

CHBMB

Konijntjes

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation