-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl-installer fails on systems without either systemd-resovled or resolvconf #1926
Comments
Update: I was able to install nextcloudpi by running apt install systemd-resolved before running the script |
Is also a problem with the curl installation on Debian 12 x86_64. |
In my case, all I had to do was install systemd-resolved, configure the dns server address and then run the script. |
I haven't even configured a dns-server. |
I had to configure the address of the dns server because after installing systemd-resolved I restarted the server and was left without dns. |
right, a restart fixed it for me |
When I tried to install nextcloudpi on my Raspberry Pi OS Lite 64-bit Debian 12 (bookworm) via curl script: So, I manually installed the missing package 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 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
|
It seems "Client Push" app was not installed, so after installing it from appstore and executing |
I have same issue on Proxmox VM with installer |
You can configure the systemd-resolved to have DNS. Edit: You can just set up the DNS |
When trying to install nextcloudpi via the curl-script on a freshly flashed Raspberry Pi OS (Bookworm) i get the following error:
Downloading updates
Performing updates
PHP Warning: Undefined variable $CONFIG in Command line code on line 1
PHP Warning: Trying to access array offset on value of type null in Command line code on line 1
PHP Warning: Undefined variable $CONFIG in Command line code on line 1
PHP Warning: Trying to access array offset on value of type null in Command line code on line 1
Installing clear-php-opcache
Installing dnsmasq
Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://packages.sury.org/php bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libraspberrypi0 libwpe-1.0-1 libwpebackend-fdo-1.0-1
Use 'sudo apt autoremove' to remove them.
Suggested packages:
resolvconf
The following NEW packages will be installed:
dnsmasq
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 32.4 kB of archives.
After this operation, 120 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main arm64 dnsmasq all 2.89-1 [32.4 kB]
Fetched 32.4 kB in 0s (567 kB/s)
Selecting previously unselected package dnsmasq.
(Reading database ... 246159 files and directories currently installed.)
Preparing to unpack .../dnsmasq_2.89-1_all.deb ...
Unpacking dnsmasq (2.89-1) ...
Setting up dnsmasq (2.89-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq.service → /lib/systemd/system/dnsmasq.service.
Applying workaround for dnsmasq bug (compare issue Installation of dnsmasq breaks DNS-resolution #1446)
**Unit systemd-resolved.service could not be found.
Failed to stop resolvconf.service: Unit resolvconf.service not loaded.**
The text was updated successfully, but these errors were encountered: