Closed skl283 closed 4 months ago
🏁 The script runs without any problems from this end.
_ __ __ ________ ______ _
/ | / /__ _ __/ /_/ ____/ /___ __ ______/ / __ \(_)
/ |/ / _ \| |/_/ __/ / / / __ \/ / / / __ / /_/ / /
/ /| / __/> </ /_/ /___/ / /_/ / /_/ / /_/ / ____/ /
/_/ |_/\___/_/|_|\__/\____/_/\____/\__,_/\__,_/_/ /_/
Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Container ID: 112
Using Hostname: nextcloudpi
Using Disk Size: 8
Allocated Cores: 2
Allocated RAM: 2048
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using APT-Cacher IP Address: Default
Disable IPv6: yes
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a NextCloudPi LXC using the above advanced settings
✓ Using local for Template Storage.
✓ Using thin-pool for Container Storage.
✓ Updated LXC Template List
✓ LXC Container 112 was successfully created.
✓ Started LXC Container
✓ Set up Container OS
✓ Network Connected: 192.168.86.250
✓ IPv4 Internet Connected
✗ IPv6 Internet Not Connected
✓ DNS Resolved github.com to 140.82.113.4
✓ Updated Container OS
✓ Installed Dependencies
✓ Installed NextCloudPi
✓ Customized Container
✓ Cleaned
✓ Completed Successfully!
NextCloudPi Setup should be reachable by going to the following URL.
https://192.168.86.250/
🧐 As this issue is unrelated to the script, it is considered closed.
Thank you for your reply!
It's good to see that this works for you. In my case it doens't. You see in the Verbose log, that there isn't a problem to resolve hostnames. It after this is executed - since this point everything works... i am not sure what these packages do, but if i manually go - after the creation is aborted to the lxc - ping to internet (8.8.8.8) is possible but NO nameserver resolution. There is nothing blocked - it must have to do with these commands (i think) - @tteck do you a a hint to get this fixed?
Reading state information... Done
\The following additional packages will be installed:
libnss-myhostname libnss-resolve
Suggested packages:
polkitd | policykit-1
The following NEW packages will be installed:
libnss-myhostname libnss-resolve systemd-resolved
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 486 kB of archives.
After this operation, 1,245 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 libnss-myhostname amd64 252.22-1~deb12u1 [84.0 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 systemd-resolved amd64 252.22-1~deb12u1 [305 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 libnss-resolve amd64 252.22-1~deb12u1 [97.2 kB]
Fetched 486 kB in 0s (7,869 kB/s)
\Selecting previously unselected package libnss-myhostname:amd64.
(Reading database ... 20059 files and directories currently installed.)
Preparing to unpack .../libnss-myhostname_252.22-1~deb12u1_amd64.deb ...
Unpacking libnss-myhostname:amd64 (252.22-1~deb12u1) ...
|Selecting previously unselected package systemd-resolved.
Preparing to unpack .../systemd-resolved_252.22-1~deb12u1_amd64.deb ...
Unpacking systemd-resolved (252.22-1~deb12u1) ...
Selecting previously unselected package libnss-resolve:amd64.
Preparing to unpack .../libnss-resolve_252.22-1~deb12u1_amd64.deb ...
Unpacking libnss-resolve:amd64 (252.22-1~deb12u1) ...
Setting up libnss-myhostname:amd64 (252.22-1~deb12u1) ...
Setting up systemd-resolved (252.22-1~deb12u1) ...
Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf...
Creating group 'systemd-resolve' with GID 996.
Creating user 'systemd-resolve' (systemd Resolver) with UID 996 and GID 996.
/Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.
|Setting up libnss-resolve:amd64 (252.22-1~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
\Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for libc-bin (2.36-9+deb12u7) ...
/curl: (6) Could not resolve host: raw.githubusercontent.com
/dev/fd/63: line 1: $'\E[?25h': command not found
/dev/fd/63: line 2: $'\E[01': command not found
/dev/fd/63: line 2: $'31m[ERROR]\E[m': command not found
/dev/fd/63: line 2: $'31m31\E[m:': command not found
/dev/fd/63: line 2: $'31m0\E[m:': command not found
That is coming from their install. Has nothing to do with the script in this repo. https://github.com/tteck/Proxmox/blob/8fd1727fa8119ee4685dbf740368df8822cdad25/install/nextcloudpi-install.sh#L31
Do not use SSH
🔁 If I cannot reproduce the problem on my side, I cannot address an issue that appears to be functioning correctly here.
What PVE version are you using?
I'm having serveral VM/Lxc with and without your scripts. Im directly at the webshell of pve and i think it has to with these command (were dns was possible - just after that no dns is working!
I'm using latest Version, no Updates available and fresh rebooted ;-)
\The following additional packages will be installed:
libnss-myhostname libnss-resolve
Suggested packages:
polkitd | policykit-1
The following NEW packages will be installed:
libnss-myhostname libnss-resolve systemd-resolved
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 486 kB of archives.
After this operation, 1,245 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 libnss-myhostname amd64 252.22-1~deb12u1 [84.0 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 systemd-resolved amd64 252.22-1~deb12u1 [305 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 libnss-resolve amd64 252.22-1~deb12u1 [97.2 kB]
with systemd-resolved in the container the container IS NOT using the defined DNS-Server from proxmox. In this case there is a Fallback file, where 8.8.8.8 and 8.8.4.4 is used. This is blocked in my network. In the Script you ask a DNS Server - but this DNS is not inserted into the fallback DNS File inside the LXC. This is a script issue... you write that file with its content here:
This is necessary for their https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh script
As you can see, systemd-resolved
is removed after completing their install script.
Your only option is to unblock 8.8.8.8 and 8.8.4.4 until the installation is complete.
OK! perhaps you could write this for any other People like me, that this is necessary and the provided DNS (from Proxmox) is not used
Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
I'll try to set up a new Nextcloudpi Instance but getting the following error (verbose log)
What settings are you currently utilizing?
Advanced Settings
Which Linux distribution are you employing?
Debian 12
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
Please provide detailed steps to reproduce the issue.
Just create a new Instance