Help Us Understand Your Persistent Config Needs on OpenLiteSpeed

cPFence

Hello everyone,

We are currently developing a new module for our software to allow persistent configurations in OpenLiteSpeed (OLS) on Enhance servers. Our software currently only supports the great Enhance CP, as we have moved all our servers and clients' servers to Enhance lately. As part of this development, I'd love to gather insights from the community on what persistent configurations are most important for you. Specifically, I'm interested in understanding:

1- Essential configurations: What settings or features do you always configure in OLS?
2- Persistence needs: Which configurations do you think should persist across updates?

Your feedback will be invaluable in ensuring that the module meets the needs of users like yourselves.

Thank you in advance for sharing your experiences and suggestions!

Looking forward to your thoughts and ideas.

Edit : We are aware that this feature is already on the roadmap of the Enhance team; however, since we are currently utilizing this module on our own servers, we believe it would be beneficial to include it in our software, even as a temporary addition.

MediaServe

cPFence We're newer to OLS (As well as LS but we can manage those settings.)

For OLS I'd love do see good PCI configs, i.e. removing cyphers that fail PCI or what not. That's what I'm currently working on with a client on OLS which might require us to go back to Apache for shared hosting until the OLS config can be persistent.

ronald

It's hard to pick just some of the options, why not offer the complete config? Both server wide limits and virtual host limits have important settings to optimize performance, security and better tailor the server to whatever hardware it's running on.

JohnB

Nothing like a partially working feature. If the whole config can't be persisted just wait for Enhance to do it.

cPFence

Thank you all for your valuable feedback and suggestions. Unfortunately , incorporating a full configuration feature would deviate from our current scope and expertise.

ecknz

cPFence currently testing out your software on a test VPS deployed today, so far it uses the least amount of resources compared to other similar options.

No specific requirements other than an integration of your software into the panel would be nice rather than just CLI

cPFence

ecknz
Thank you for trying out our software and sharing your feedback! We're glad to hear it's performing well on your test VPS. I wanted to let you know that a major update, version 3, is already out, featuring even more speed and resource optimizations, especially for high-traffic busy servers.

Since this is a major update from version 2 , please do a full uninstall using cpfence --uninstall or /opt/cpfence/app/setup/stop_all, and then reinstall the new version.

As for the panel UI integration, this will be available once the Enhance team releases the API for it.

kyzoeadmin

@cPFence would you consider implementing other payment gateways as Paypal is not available to us, and maybe with more people around (have send you a ticket about it)

cPFence

kyzoeadmin

Other payment options will be available soon. Currently, only PayPal is supported. I have already replied to your ticket. Thank you.

Peertje

It would be nice to have the ability to add bots to the blacklist quick and easy. There are a lot of bad bots blocked but there are so many 'good' bots that misbehave (amazon etc) that it would be nice to just add them serverwide as easy as possible.

cPFence

Peertje
Thanks for the suggestion. This feature is already built into cPFence WAF. These bots are already blocked server-wide for our users. There are many "not-so-bad" bots that exhaust resources with little to no benefit.

cPFence

MediaServe

This feature isn't production ready yet since we're tied up with other important updates and changes. But can you share the config file before and after your changes?

Here’s how you can do it:

1- Grab a copy of the current config:

docker cp openlitespeed:/usr/local/lsws/conf/httpd_config.conf /opt/httpd_config_before.conf

2- Make the changes in the UI.

3- Then, take another copy after the changes:

docker cp openlitespeed:/usr/local/lsws/conf/httpd_config.conf /opt/httpd_config_after.conf

Once you’ve got both files, drop them in the ticket system, and I'll check if a temporary workaround is doable. Hopefully, we can sort something out.

MediaServe

cPFence The problem PCI client just opened the ticket, so I haven't tweaked the OLS config at all. It'll be lost after update anyway (although I have thought about locking it down with "chattr -i" but I haven't asked if that would break Enhance in some fashion with an update. I'll wait until Enhance or you guys provide persistence for OLS. Can't really spend the time to weak the OLS config until it can be persisted.

For now I'll leave OLS for cPanel migration alone and for newer clients I'll upgrade OLS to commercial LiteSpeed until OLS has a persistent config on Enhance.

Martijndort

Would be nice if changes in TLS versions used are persistent.