Spent half the day trying to setup the appliance.
I really feel itās a bad jokeā¦
Very few info/howtos on the subject matter. Are there users out there?
Install on an intel NUC (reference listed in ubuntuās compatibility list).
First time, mysql crash.
Reinstall.
Waiting for PHP.
Reinstall : the same.
Log :
2022-02-12T17:34:46Z nextcloud.mdns-publisher[7276]: 2022/02/12 17:34:46 gmx: unable to open local socket: listen unix /tmp/.gmx.7292.0: bind: operation not permitted
2022-02-12T17:34:46Z nextcloud.mdns-publisher[7276]: 2022/02/12 17:34:46 Failed to listen 224.0.0.251:5353: listen udp4 224.0.0.251:5353: socket: permission denied
2022-02-12T17:34:56Z systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
2022-02-12T17:34:56Z systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result āexit-codeā.
2022-02-12T17:34:57Z systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
2022-02-12T17:34:57Z systemd[1]: snap.nextcloud.mdns-publisher.service: Scheduled restart job, restart counter is at 23.
2022-02-12T17:34:57Z systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
2022-02-12T17:34:57Z systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
2022-02-12T17:34:57Z nextcloud.mdns-publisher[7349]: 2022/02/12 17:34:57 gmx: unable to open local socket: listen unix /tmp/.gmx.7366.0: bind: operation not permitted
2022-02-12T17:34:57Z nextcloud.mdns-publisher[7349]: 2022/02/12 17:34:57 Failed to listen 224.0.0.251:5353: listen udp4 224.0.0.251:5353: socket: permission denied
Afaik, nextcloud.redis-server is down and canāt be restarted.
I expected some OOB solution and wonder if itās indeed maintained/tested.
Such things should never happen form the very start.
I would avoid the appliance entirely if I were you, I donāt think anyone maintains it. You can just install normal Ubuntu and install the snap there if you like, which is maintained. Still gives you a fairly good OOB experience (since itās what the appliance relies on).
Hello!
Thks for your answer.
I successfully installed alpine linux standard base + their nextcloud .apk (good wiki). āThat amounts for a mere 1,2G installā¦
Will need further testing but thatās impressive!
Might also test clear linux + docker-compose but the alpine build seems closer to my goal which is limited maintenance for a one purpose server.
Have a nice week!
Sorry i do not like Snap. Perhaps it is better to not use it. I was not able to set two Nextcloud DNS names and two Lets Encrypt certificates without nginx to one Nextcloud (need it for migration to another name). On normal systems this is no problem.
Please post your hardware and your operating system.
Glad you settled on a setup that you like, @lemascaret!
You donāt need to apologize, itās not for everyone. However, please stop trolling on every thread that asks a snap-related question to share that you donāt like it. It doesnāt help the discussion at all.
It is not really trolling.
But perhaps you can solve my trivial problem with two simultaneous Nextcloud server names. But perhaps no Snap user need it for soft migrations like me for changing the Nextcloud server name. I think this must be a standard feature like on other Nextcloud installations. And yes i can use a reverse proxy like nginx. But i do not want use it. I also do not need nginx on other installations.
Hello!
Thks for your answer.
I successfully installed alpine linux standard base + their nextcloud .apk (good wiki). āThat amounts for a mere 1,2G installā¦
Will need further testing but thatās impressive!
Might also test clear linux + docker-compose but the alpine build seems closer to my goal which is limited maintenance for a one purpose server.
Have a nice week!
Really? Oh dear
I thought you maintained it (sorry if I am wrong)
Mine is still working perfectly,
but for when it doesnt, what would you recommend for a RPi3?
I maintain the Nextcloud snap, which covers (2). The Ubuntu appliance uses Ubuntu Core, which covers (1), and it happens to include the Nextcloud snap, so it also covers (2). If it works for you, excellent, please donāt sweat. Ubuntu Core is entirely snap-based and will update itself. But if you run into issues, you will have trouble finding help because of a few things:
Ubuntu Core is very different from standard Ubuntu, and has a learning curve. This means that the community of users youād normally have giving you advice doesnāt exist there.
In reality, Ubuntu Core is barely supported by Canonical, much less images that build on top of it. Theyāve lost a huge percentage of the engineers working on it, including the people bootstrapping the Appliance story. Itās possible more people have picked it up, but it would surprise me.
Again, if youāre running Ubuntu Core/the Appliance image, I donāt say this to worry you. The snaps youāre using are well-maintained as far as Iām aware. Itās just the tech behind Ubuntu Core itself and the Appliance images themselves that Iām talking about, here.
As far as what I would recommend instead: a standard Ubuntu Server install. SSH in there, run sudo snap install nextcloud, and you have exactly what the Ubuntu Appliance gives you without any of the hassle. I could even put together a cloud-init script that would do this for you if you wanted to use a cloud image. Then the OOTB experience would be more or less identical. Let me know if that sounds interesting.
Thanks, and Sorry for late reply - life etc!
It says, 'The Nextcloud VM (virtual machine appliance), Home/SME Server and scripts for RPi (4). Community developed and maintained. ā
My box only has a RPi 3 and I have as much chance of buying a RPi4 as I do Rocking horse Poo at the moment
On another note - I have now moved to ArchLabs from Manjaro and after regenerating the key for Archlabs and adding it to my Ubuntu account, the RPi box is still asking me for a password when I try to SSH from AL (on Manjaro it still works). Any ideas on this? is it something to do with the passkey?
Welcome to a good example of why I recommend avoiding Ubuntu Core these days. Thatās an issue thatās been known and unfixed since 2016. Use your Manjaro box to add your Arch key (probably into /home/<username>/.ssh/authorized_keys).
Not sure what you mean by still having my old key? I still have the one for Manjaro and that still works when I boot into Manjaro - I can access via ssh that way
So I boot into AL on laptop and run cat ~/.ssh/id_rsa.pub
Then copy paste the result somewhere and reboot laptop into Manjaro and then ssh into RPi and copy paste that result into /home/<username>/.ssh/authorized_keys(probably )?
Yes. /home/<username>/.ssh/authorized_keys contains one public key per line. Add a new line for the new key, paste it in, and you should be able to SSH from both places.
I forgot I had use vi in Ubuntu Core, so it took me ages to do that simple addition of one line - I find that such a non-intuitive editor, and always end up swearing
Edit: I just noticed that the password prompt on this new ubuntu server version on a different SD card is using my Ubuntu SSO account name - how is this possible? My Ubuntu SSO account password doesnt work tho