Expectations for Enhance in 2026: Page 3 - Enhance Control Panel

Expectations for Enhance in 2026

gmakhs

@Adam It has been over a year since version 12 was released, and I have raised the same issues multiple times through the forum and support tickets. At this point, it feels like these concerns are not being acknowledged or addressed.

I would appreciate a clear statement on whether Enhance intends to resolve the accumulated technical and developer-related issues, or if the primary focus going forward is mainly on larger providers.

Clear communication and visible action would save time for everyone involved. Knowing the direction Enhance plans to take would also help set realistic expectations and avoid repeated frustration.

Adam

JohnB No good control over things like autorestart, start, stop etc. Like sure technically you have Node implemented but from the interface its so limited I'm better off just setting up pm2 and git on a VPS... Others have pointed out more issues.

You have complete control over those things. If set to automatic, the app will be started and restarted if it exits for any reason. If you want to stop the app which was started by Enhance, set it to manual. When you want Enhance to start/monitor it again, set it to automatic.

Git integration (automatic tracking of a particular branch/tag) is a completely separate feature to Node.js support.

We were able to reproduce the issue with cgroups not being applied to node.js on container restart. It's very intermittent and is caused by a race condition. The fix for this is in 12.14.2.

What other functionality are you looking for and what other problems have you experienced?

JohnB

Adam I'll checkout the NodeJS functionality again in that case and give it another try.

Thanks for your response and already having an update to fix the cgroups issue reported by gmakhs.

themew

DracoBlue We're about to make the move to Enhance, however most if not all the sites we're managing are Nginx with custom nginx.conf files. Can you describe or link to the limitations we can expect with Nginx?

Adam

themew

You have the ability to edit the main nginx.conf including the http {} block. You can also add content to the server {} block for each virtual host using the virtual host includes feature https://enhance.com/docs/application-role/apache-configurations.html#virtual-host-includes. It's not possible to override the Location / block and of course there is no .htaccess support.

nhybgtvfr

Adam You have the ability to edit the main nginx.conf including the http {} block.

by this do you mean the /etc/nginx/nginx.conf file?
will any changes to this file be update safe or would they need to be re-applied after every update?

also to add, for expectations for 2026....

priorities for me are:

fully supported/working redirections.. webservers are basically broken without these.
total mailbox size limit per package, it's ok for a fixed number of mailboxes of a fixed size, but for dynamic mailboxes, need to be able to set a maximum total mailbox size for all mailboxes combined, not an individual mailbox, ie 5 dynamic mailboxes, limit of 50Gb, allows up to 250GB for email. that's just wrong.
domain/dns only packages, email only packages, and domain/dns and email only packages.
not everyone actually wants/needs a website...
dns separated from website servers. being unable to edit dns records because a specific webserver is down is stupid.
especially when i'm running dedicated servers just for the dns service.
arm cpu support.

« Previous Page