Nextcloud Snap users, please list the issues you're facing

snap

#42

Not sure, but I think the snap-users should rather use the snap-tools to update (NC 11 not available yet, expected in January). If you can’t shouldn’t use the updater app, it should perhaps be disabled and blocked. @oparoz


#43

Yes, the updater cannot be used and needs to be removed from the snap to avoid confusion.


#44

the above is important information for nextcloud box users, thanks.

another issue, which may or may not fall under the topic of this thread: how to enable letsencrypt on nextcloud box. if i take one step back, i’d say another issue is this: how to share whatever file when you have https enabled (which is to recommend) - because as of now, when the other person clicks the link i provided, he/she is greeted with the certificate warning, which to most people is a blocker, they just get confused and it all stops there.


#45

#46

hi @oparoz is there an option to change default backup location for the OwnBackup app in snap ? for example to second drive ( /mnt/backup/ ) ?


#47

@zahareevici If you can pick from within the app, then pick /media


#48

Cannot delete folders for some reasons. The problem is reproducible:


Cannot change max upload file size:


#49

Unfortunately there is no option to change the way to folder


#50

Well for my efforts. I bought a nextcloud box and was a little miffed that is supposed to only use a RPi2. Well that is why the included card did not boot. Oh well. Not adverse to rolling my own I thought no probs I used the Ubuntu Core build for RPi3 and just install and configure snaps myself. How hard can it be?

Well nextcloud seems to be there

snap find nextcloud
Name       Version      Developer  Notes  Summary
nextcloud  11.0.0snap3  nextcloud  -      Nextcloud Server
spreedme   0.29.2snap1  nextcloud  -      Spreed.ME audio/video calls and conferences feature for the Nextcloud Snap
qownnotes  17.01.4      pbek       -      Plain-text file notepad with markdown support and ownCloud integration

Cool. Just a quick snap install nextcloud then. No errors so I should be able to just login to the web interface right? Umm wrong.

Maybe I need to just get it to listen on an interface ?

snap set nextcloud listen=127.0.0.1
error: cannot perform the following tasks:
- Run configure hook of "nextcloud" snap (snap "nextcloud" has no "configure" hook)

Ouch! That does not look right?

Ahh wait look there are some files in /snap/bin that might help.

ls -la
total 8
drwxr-xr-x  2 root root 4096 Jan 12 20:24 .
drwxr-xr-x 10 root root 4096 Jan 12 20:24 ..
lrwxrwxrwx  1 root root   13 Jan 12 11:31 nextcloud.disable-https -> /usr/bin/snap
lrwxrwxrwx  1 root root   13 Jan 12 11:31 nextcloud.enable-https -> /usr/bin/snap
lrwxrwxrwx  1 root root   13 Jan 12 11:31 nextcloud.mysql-client -> /usr/bin/snap
lrwxrwxrwx  1 root root   13 Jan 12 11:31 nextcloud.occ -> /usr/bin/snap

Ahh well nextcloud.occ is what we use to configure from the command line isn’t it? Done that many times before on server installations.

sudo ./nextcloud.occ 
Cannot write into "config" directory!
This can usually be fixed by giving the webserver write access to the config directory

See https://docs.nextcloud.com/server/11/go.php?to=admin-dir_permissions

Whoops… did I just make a rookie mistake and assume all snaps are root owned?!

sudo -u www-data ./nextcloud.occ 
2017/01/12 22:20:01.270467 cmd_run.go:175: WARNING: cannot create user data directory: cannot create "/var/www/snap/nextcloud/550": mkdir /var/www: read-only file system
failed to create user data directory. errmsg: Read-only file system

Err… WTF? Am I missing something here? How can the snap config be read only to www-data and root does not have permissions to it either?

Well that is as far as I have gotten today. So if anyone want to weigh in what might be wrong I am all ears.

Thanks.


When can we expect to see an Official Raspberry Pi 3 image?
#51

Sounds like your Nextcloud snap did not install properly. Maybe you don’t have enough space on the SD card since you’re not using the HD at all with the image you’ve built.


#52

Sounds like your Nextcloud snap did not install properly. Maybe you don’t have enough space on the SD card since you’re not using the HD at all with the image you’ve built.

Hmmm perhaps. But I am starting to see a pattern.

df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            455M     0  455M   0% /dev
tmpfs            93M   14M   79M  15% /run
/dev/mmcblk0p2  3.5G  655M  2.7G  20% /writable
/dev/loop0       64M   64M     0 100% /
/dev/loop1       86M   86M     0 100% /lib/modules
tmpfs           461M  4.0K  461M   1% /etc/fstab
tmpfs           461M     0  461M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           461M     0  461M   0% /sys/fs/cgroup
tmpfs           461M     0  461M   0% /mnt
tmpfs           461M     0  461M   0% /var/lib/sudo
tmpfs           461M     0  461M   0% /tmp
tmpfs           461M     0  461M   0% /media
/dev/loop2      2.0M  2.0M     0 100% /snap/udisks2/11
/dev/loop4       64M   64M     0 100% /snap/core/396
/dev/loop3      3.7M  3.7M     0 100% /snap/snapweb/25
/dev/loop5      4.2M  4.2M     0 100% /snap/spreedme/21
/dev/loop6      5.9M  5.9M     0 100% /snap/pi3/6
/dev/loop7       86M   86M     0 100% /snap/pi2-kernel/22
/dev/loop8      138M  138M     0 100% /snap/nextcloud/550
/dev/loop9       65M   65M     0 100% /snap/core/716
/dev/mmcblk0p1  127M   22M  105M  18% /boot/uboot
cgmfs           100K     0  100K   0% /run/cgmanager/fs
tmpfs            93M     0   93M   0% /run/user/1000`

The nextcloud snap seems to install under /writable/user-data/user/snap

It seems the document is rather misleading saying you should prefix all snap commands with sudo. That installs system snaps in /writable/system-data

I will purge all my snaps and start again just using the user to set things up and see how far I get.


#53

root@SudsHub:~# sudo apt install snapd
Reading package lists… Done
Building dependency tree
Reading state information… Done
snapd is already the newest version (2.20.1ubuntu1).
The following packages were automatically installed and are no longer required:
libappindicator1 libglade2-0 libindicator7 libpango1.0-0 libpangox-1.0-0
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@SudsHub:~# sudo snap install nextcloud
error: cannot communicate with server: Post http://localhost/v2/snaps/nextcloud: dial unix /run/snapd.socket: connect: connection refused
root@SudsHub:~# cat /etc/issue
Ubuntu 16.04.1 LTS \n \l


#54

Is Ubuntu Core still in beta or is it being included in recent images of the NC Box? Here is some output from my NC Box which leads me to belive that it is running Ubuntu Core but other forum users tell me that it is a full Ubuntu Server install on the NC box. :confused:

ubuntu@nextcloud's password: 
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-1017-raspi2 armv7l)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

0 packages can be updated.
0 updates are security updates.


*** System restart required ***
Last login: Fri Jan 13 19:12:27 2017 from 192.168.1.58
ubuntu@nextcloud:~$ snap list
Name         Version      Rev   Developer  Notes
nextcloud    11.0.0snap3  550   nextcloud  -
ubuntu-core  16.04.1      1361  canonical  -
ubuntu@nextcloud:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial
ubuntu@nextcloud:~$

#55

Ok … so cool.

After removing and reinstalling this time as a normal user all seems to work. I even managed to enable-https via the script.

Now I want to know is how do I FORCE https redirection from port 80. Because that is what I do I my normal server installs.

Once that is done then I feel happier putting the nextcloud box on the internet as it is I don’t like plain http anything unless it is on my lan or VPN.

I see .htaccess files in

/var/snap/nextcloud/common/nextcloud/data/.htaccess

and

/var/snap/nextcloud/550/nextcloud/config/.htaccess

But I don’t see a way to enable mod_rewrite for httpd inside the snap. There is no a2enmod or anything.

Ideas?


#56

I can’t access my NC Box over https, http works. I followed these instructions.

I have included output from step 4 Enable HTTPS, it looks like the first command in step 4 worked fine but the second command didn’t. Should I run sudo nextcloud.enable-https again?

ubuntu@nextcloud:~$ sudo nextcloud.enable-https -d

<snip>

Attempting to obtain certificates... done
Looks like you're ready for HTTPS!
ubuntu@nextcloud:~$ sudo nextcloud.enable-https   

<snip>

Attempting to obtain certificates... error running certbot:

Saving debug log to /var/snap/nextcloud/current/certs/certbot/logs/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for *******.****.com
Using the webroot path /var/snap/nextcloud/current/certs/certbot for all domains.
Waiting for verification...
Cleaning up challenges
Generating key (4096 bits): /var/snap/nextcloud/current/certs/certbot/config/keys/0001_key-certbot.pem
Creating CSR: /var/snap/nextcloud/current/certs/certbot/config/csr/0001_csr-certbot.pem
An unexpected error occurred:
There were too many requests of a given type :: Error creating new cert :: Too many certificates already issued for: ****.com
Please see the logfiles in /var/snap/nextcloud/current/certs/certbot/logs for more details.

#57

There were too many requests of a given type :: Error creating new cert :: Too many certificates already issued for: ****.com
Please see the logfiles in /var/snap/nextcloud/current/certs/certbot/logs for more details.

Occurs to me that you already have a letsencrypt cert for that domain. Check the log like it says.


#58

As near as I understand the problem was that letsencrypt was refusing to issue a certificate to mooo.com. I setup ddns with noip.com and then it worked fine. So for whatever reason freedns.afraid.org wouldn’t play nice with letsencrypt. :confused:


#59

There is no need, as it’s already done for you.

This is considered too advanced for this snap. You cannot change any of the Apache or PHP configuration.


#60

Reading through this lengthy thread, I am wondering if the Snap is production ready. I am about to install my first ever Nextcloud and I’m currently looking into the different deployment options. Snap sounded pretty cool, but there seem to be many issues. Or did I get the wrong impression?


#61

Bear in mind that most problems are related to running the snap on the Pis.
If the snap delivers what you needs in terms of features and you are aware of the limitations, then it’s a good solution.