Enhance v12.0.0 Released 🎉: Page 33 - Enhance Control Panel

Enhance v12.0.0 Released 🎉

cPFence

wav3front

Try this
https://community.enhance.com/d/2541-tailscale-and-v12/3

wav3front

cPFence

I just tried.
now I cannot connect to ssh (cli). I get connection refused.

wav3front

cPFence I have access to KVM. Should I revert those changes?

cPFence

alenguav

Most likely a permissions or ownership issue. I’d start by checking the .htaccess file and the public_html directory first.

If you have cPFence, you can try this

cpfence --fix-permissions-dry

Adam

wav3front I just tried.
now I cannot connect to ssh (cli). I get connection refused.

Enhance doesn't touch your ssh server, I think that's unrelated. Check sshd is running:

systemctl status ssh

cPFence

wav3front

Not related. You probably got temporarily blocked by cPFence brute force protection for failed login attempts. Try changing your IP and connect again. After you log in, make sure to whitelist your original IP.

Adam

wav3front Status: Using username "**@57...*".
Status: Access denied
Error: Authentication failed.
Error: Critical error: Could not connect to server
Command: PWD
Response: 257 "/" is your current location
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PASV
Response: 227 Entering Passive Mode (57,129,49,111,118,42)
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing

Try this:

iptables -F DOCKER
iptables -t nat -F DOCKER

wav3front

Adam this worked!

iptables -F DOCKER
iptables -t nat -F DOCKER

wav3front

cPFence no, my IP was not blacklisted by CPFence.

@Adam

looks like sshd is running?

● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/usr/lib/systemd/system/ssh.service; disabled; preset: enabled)
Active: active (running) since Wed 2025-03-05 17:21:47 EET; 1 day 4h ago

wav3front

I restared ssh and now it works.

wav3front

I've opened a ticket about this, but this is urgent because the website in question is offline:

I tried to migrate some websites to a new node.
but the migration has frozen for more than 1 hour now:

The last log entry is:

[11:47:10 03/07/2025] Updating backup config on destination server

This website is offline, database is not migrated.

Any idea what to do?

broiniac

Krikke Old files can still be found in/var/local/enhance/nginx/vhost_includes/

Damn it man, this line was a real live saver for me! THANKS!!

DracoBlue

12.0.28
12th March 2025

Enhanced

Improved logic for error handling in backups to the Enhance backup target.

DracoBlue

12.0.29
12th March 2025

Enhanced

Automatic rebuild of resolv.conf within postfix chroot.

alenguav

10 days since the last Enhance v12 update. Can we consider it stable now?

gmakhs

alenguav nop there are many issues to be addressed still, they just can't get backups right yet

cPFence

alenguav 10 days since the last Enhance v12 update. Can we consider it stable now?

V12 is definitely stable now and performs noticeably better than v11 in terms of resource usage. It also provides a much cleaner architecture for developers to build on and extend the platform more easily. You’re better off getting yourself out of the Docker cage, it’s a perfect time to upgrade.

adil

gmakhs

The only thing that holds me back from the upgrade to v12.

cPFence

adil

Backups are working flawlessly in v12 on EXT4, we’ve tested them across several production clusters without any issues. The only known issue is that the “allowed backup hours” setting isn’t being respected, but aside from that, everything runs smoothly. If that feature is critical for you, it’s better to wait. But if you’re waiting on BTRFS fixes, your wait might be a long one, if it even happens at all.

DracoBlue

cPFence "Maximum backup retention" and "Allowed backup hours" are not working correctly.

adil

cPFence

There is also the missing logs, which is the main important thing for us.
Also saw other issues reported from other members here on the forum, they are niche but still ...

cPFence

DracoBlue "Maximum backup retention" and "Allowed backup hours" are not working correctly.

That's specific to S3 backups only, we're not using S3 backups since they're slower, less efficient, and more costly. The built-in backup system (using ext4) has been working perfectly.

« Previous Page Next Page »