Search results

It's already pushed. Maybe because the existing package version is higher than the new package on your system? See the packages here https://rpms.litespeedtech.com/debian/pool/main/trixie/

@epionier The MySQL, Memcached, and Redis packages are ready; feel free to give them a try and let me know if you encounter any issues. For imap, I guess it's not compatible with Trixie yet.

Glad to know it works well!

That is for sure, just need some time.

@Mathis Done, please give it a try.

@Mathis Got it, I’m currently working on the amd64 lsphp84 packages, but I’ll switch to the main lsphp84 PHP package for aarch64 as well.

I use your dockerfile, and the build works on my arm server.

Putting "RewriteRule ^\.user\.ini$ - [F,L]" at the top of the .htaccess file should work. You can also set a static context to restrict the file from being accessed.

Hi @Mathis I tried to push some lsphp84 and extension packages to the repo for Trixie, feel free to give it a try and let me know if you have any issues.

Hi @PaulK and @paul_m I tried to push some lsphp84 and extension packages to the repo for trixie, feel free to give it a try and let me know if you have any issues.

@Mathis Ah, I see, you were running Debian 12 with lsphp84 and then upgraded to Debian 13. Since the lsphp packages for Debian 13 aren’t available yet, this issue can occur. For now, please avoid running any updates.

Can you give me some key features content so I can help list it on the page?

@Mathis Packages should be working, confirmed from my local test and other users. Please try "apt clean && apt update" or any similar command in raspberry pi 4

Apologies for the inconvenience, the broken package has been removed. Please run apt clean followed by apt update; this should resolve the issue. As for Trixie, the packages are not yet available, which is why the repository appears empty. Modifying the current build file for Trixie is what led...

Thanks for the report, the broken package has been removed, please try updating it again, and it should fix the issue.

I think it's in the latest repository package build as well.

We are working on it. :)

Need to check the error log. Maybe you can create a support ticket to support@litespeedtech.com with this forum post link appended.

To increase the memory limit, just edit the php.ini file would do it. Please check https://docs.litespeedtech.com/lsws/tuning-dedicated/ for dedicated site optimization.

Hi, Have you considered this one, a similar command, but the restart part is systemctl restart lsws https://docs.openlitespeed.org/panel/directadmin/#using-the-cron