Repository navigation
ipv6 only vps debian12 setup ends here always, it just get back to bash promt #123
Description
ℹ Applying new Fail2Ban configuration...
ℹ Enabling and restarting Fail2Ban to apply new rules...
Synchronizing state of fail2ban.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable fail2ban
✓ Fail2Ban is active with the new configuration.
Status
|- Number of jail: 2
`- Jail list: sshd, ufw-probes
Show instructions for adding IPs later? [y/N]:
▓▓▓ SSH Hardening ▓▓▓
═════════════════════════════════════════════════════════════════
ℹ Using SSH service: ssh.service
ℹ Backing up original SSH config...
⚠ SSH Key Authentication Required for Next Steps!
Test SSH access from a SEPARATE terminal now.
Activity
buildplan commentedon Aug 12, 2026
I had tested this on IPv6 only VPS on Scaleway and it worked fine. I will check again and try to reproduce and fix whatever is breaking this.
GuinnessDublin commentedon Aug 12, 2026
GuinnessDublin commentedon Aug 12, 2026
If you need some logs etc, just ask.
buildplan commentedon Aug 12, 2026
Would you mind checking this verion in
fix_ipv6branch - i think i know what happened and have tried to fix it but i dont have access to ipv6 only vps right now. You can pull this script and run to see if this works for you...wget https://raw.githubusercontent.com/buildplan/du_setup/refs/heads/fix_ipv6/du_setup.shbuildplan commentedon Aug 12, 2026
Could I also ask which provider did you test on? I maybe able to get a VPS from the same provider to test.
GuinnessDublin commentedon Aug 12, 2026
Leap status : Normal
▓▓▓ Secure DNS Configuration (DNS-over-TLS) ▓▓▓
═════════════════════════════════════════════════════════════════
Configure secure, encrypted DNS (Quad9 + Cloudflare fallback) and disable local tracking protocols? [y/N]: y
⚠ systemd-resolved is not installed on this system.
Install and enable systemd-resolved to handle encrypted DNS? [y/N]: y
(Reading database ... 46025 files and directories currently installed.)
Removing openresolv (3.12.0-3) ...
Selecting previously unselected package libnss-myhostname:amd64.
(Reading database ... 46009 files and directories currently installed.)
Preparing to unpack .../libnss-myhostname_252.39-1
deb12u2_amd64.deb ...deb12u2) ...Unpacking libnss-myhostname:amd64 (252.39-1
Selecting previously unselected package systemd-resolved.
Preparing to unpack .../systemd-resolved_252.39-1
deb12u2_amd64.deb ...deb12u2) ...Unpacking systemd-resolved (252.39-1
Selecting previously unselected package libnss-resolve:amd64.
Preparing to unpack .../libnss-resolve_252.39-1
deb12u2_amd64.deb ...deb12u2) ...Unpacking libnss-resolve:amd64 (252.39-1
Setting up libnss-myhostname:amd64 (252.39-1
deb12u2) ...deb12u2) ...Setting up systemd-resolved (252.39-1
Configuration file '/etc/systemd/resolved.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** resolved.conf (Y/I/N/O/D/Z) [default=N] ?
Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf...
mv: cannot move '/etc/resolv.conf' to '/etc/.resolv.conf.systemd-resolved.bak': Operation not permitted
Cannot take a backup of /etc/resolv.conf.
ln: failed to create symbolic link '/etc/resolv.conf': Operation not permitted
Cannot install symlink from /etc/resolv.conf 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.39-1
deb12u2) ...deb12u1) ...Processing triggers for dbus (1.14.10-1
Processing triggers for libc-bin (2.36-9+deb12u14) ...
ℹ Backing up current resolved config (if exists)...
ℹ Applying secure DNS settings (Quad9 with Cloudflare Fallback)...
ℹ Enabling and restarting systemd-resolved...
ℹ Symlinking /etc/resolv.conf to the secure stub resolver...
rm: cannot remove '/etc/resolv.conf': Operation not permitted
GuinnessDublin commentedon Aug 12, 2026
it went much longer. this was no vanilla installed debian 12, it was running and two times before tryied du_setup.sh when got that error.
GuinnessDublin commentedon Aug 12, 2026
https://panel.nolimitcloud.eu/billing/checkout_page.php?checkout=85 its this one
buildplan commentedon Aug 12, 2026
Ah i think this is because VPS provider might not be allowing to change the DNS settings - i will push the update to same branch with a fall-back to deal with this.
buildplan commentedon Aug 12, 2026
Would you mind testing one more time remove the old version and pull it again
wget https://raw.githubusercontent.com/buildplan/du_setup/refs/heads/fix_ipv6/du_setup.sh && chmod +x du_setup.shbuildplan commentedon Aug 12, 2026
couldn't find the ipv6 only servers on nolimitcloud website.
GuinnessDublin commentedon Aug 13, 2026
did test this last one. It works ok now. Thanks
And again this was not vanilla install. did try it in same machine every time.
buildplan commentedon Aug 13, 2026
Thanks for this. It's good that you tested on same machine that also confirms that script is working as it was intended to be idempotent and this confirms that it can handle repeated runs on same system and also now the error is sorted.
GuinnessDublin commentedon Aug 13, 2026