curl-installer fails on systems without either systemd-resovled or resolvconf

[Schniefel]

curl-installer fails on systems without either systemd-resovled or resolvconf

[vcbranco]

Is also a problem with the curl installation on Debian 12 x86_64.

[darguez]

When I tried to install nextcloudpi on my Raspberry Pi OS Lite 64-bit Debian 12 (bookworm) via curl script:
curl -sSL https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh | sudo bash
I got the same error: Unit systemd-resolved.service could not be found

So, I manually installed the missing package apt install systemd-resolved but I missed DNS with the change and I had to manually add DNS in /etc/systemd/resolved.conf. Also I had to drop the ncp created mysql database sudo mysqladmin drop nextcloud to start over with ncp installation script.

Then the installation went on, but finished with a weird sql error (not sure if the script finished at all): Table "nextcloud.appconfig" doesn't exist

However, I checked ncp installation by accessing https://my-ip/ and the web installer was working, so after the initial setup everything seemed to work fine.

The only thing that wasn't work properly was letsencrypt, because after enabling it (without errors), the certificate was not updated, so I had to edit apache2 site config file to set the correct paths to the certificates in /etc/apache2/sites-enabled/001-nextcloud.conf.

And now everything seems to work fine.

[Schniefel]

Update: I was able to install nextcloudpi by running apt install systemd-resolved before running the script

[vcbranco]

In my case, all I had to do was install systemd-resolved, configure the dns server address and then run the script.
The curl installation was done correctly.

[Schniefel]

I haven't even configured a dns-server.

[vcbranco]

I had to configure the address of the dns server because after installing systemd-resolved I restarted the server and was left without dns.
It probably wouldn't have been necessary to configure the dns if I ran the script without restarting the server after installing the package. But I haven't tested that.

[Schniefel]

right, a restart fixed it for me

[darguez]

And now everything seems to work fine.

Well, I've just realized the HPB service is always down, so something went wrong with installation after all... Also there is no /var/www/nextcloud/apps/notify_push folder and command /occ notify_push:setup returns:

There are no commands defined in the "notify_push" namespace.

[darguez]

And now everything seems to work fine.

Well, I've just realized the HPB service is always down, so something went wrong with installation after all... Also there is no /var/www/nextcloud/apps/notify_push folder and command /occ notify_push:setup returns:

There are no commands defined in the "notify_push" namespace.

It seems "Client Push" app was not installed, so after installing it from appstore and executing occ notify_push:setup HPB service is up now

[ovpc]

I have same issue on Proxmox VM with installer
script ends with: Failed to stop resolvconf.service: Unit resolvconf.service not loaded
When i install resolv.conf it breaks the dns and apt canot connect anymore

[vcbranco]

You can configure the systemd-resolved to have DNS.
https://unix.stackexchange.com/questions/442598/how-to-configure-systemd-resolved-and-systemd-networkd-to-use-local-dns-server-f

Edit: You can just set up the DNS

[ovpc]

Ran curl installer again (on a clean install) to reproduce and get and save full output
System is running in Proxmox VM
I used debian-12.5-amd64-netinst.iso installed basic system tools and ssh. After reboot installed curl net-tools and sudo, before running installer.
ncp-installer-log.txt

Can confirm after installing resolvconf the installer completed fine