Html headers preventing Simply Static from working

  • Resolved mountbest

    (@mountbest)


    4 months, 3 weeks ago

    Html headers like SCP request in .htaccess file seem to prevent Simply Static from working.

    Is this expected? If so it should be diagnosed as error. At present Simply Static reports memory problems…

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter mountbest

    (@mountbest)

    4 months, 3 weeks ago

    Done some debugging and I saw that the plugin was instantly attempting to use more than 756MB of memory (exceeding the PHP memory_limit) resulting in the error.

    I’ve manually configured PHP memory limit via .htatccess file to utilise the maximum available memory of my hosting service (2GB), along with some timeout rules:

    php_value post_max_size 2048M
    php_value memory_limit 2048M
    php_value max_execution_time 0
    php_value max_input_time 0

    It now appears that the plugin is running successfully.

    P.S. This issue occurred only with LiteSpeed server. There is no such a problem on AlmaLinux , Apache and Nginx servers

    BTW, the error triggered by Simply Static was

    PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 172032 bytes) in /home/…/public_html/wp-includes/class-wpdb.ph

    • This reply was modified 4 months, 3 weeks ago by mountbest.
    Plugin Author patrickposner

    (@patrickposner)

    4 months, 2 weeks ago

    Hey @mountbest,

    thanks for spending the time digging into the problem!

    We are indeed not officially supporting LiteSpeed servers (only Apache and NGINX).

    Our background processing uses 90% of available memory by default to make the process as fast as possible, while still leaving enough capacity to navigate the admin area. I assume that was the problem here and what ultimately led to memory exhaustion.

    I’m not sure if we are going to officially support LiteSpeed anytime soon because there are other problems here as well (no full cache control, the delay for 301 redirects, etc), but I’ll add a ticket for this specific issue in our ticket system, so we can at least solve that one!

    Thread Starter mountbest

    (@mountbest)

    4 months, 2 weeks ago

    Hey Patrick

    My LiteSpeed server account has a cPanel utility that can disable LiteSpeed WordPress caching. So, if users have access to cPanel on their LiteSpeed server accounts – there should be no problems using Simply Static with LiteSpeed servers.

    I use Simply Static for at least 2 years with WordPress Elementor website on a LiteSpeed server and this was the first time I encountered a problem. I was tempted to try older versions of Simply Static…

    With 301 redirects – you can offer users a choice: to ignore these redirects or suggest that they reorganize their website to avoid redirects. But I suspect that delay in 301 redirects can be avoided by properly disabling all caching.

    BTW. Elementor image carousels do not work in Simply Static generated website. They are frozen on the first image, Manual links to next and previous images are shown, but they do not work.

    Tom

    • This reply was modified 4 months, 2 weeks ago by mountbest.
    Thread Starter mountbest

    (@mountbest)

    4 months, 2 weeks ago

    I have upgraded Simply Static plugin to v 3.5..5 and its processing time jumped from 46 seconds to over 8 minutes. Is this normal?

    [2026-01-12 11:50:16] Setting up

    [2026-01-12 11:50:25] Fetched 1504 of 1504 pages/files

    [2026-01-12 11:56:22] 404 Page generated

    [2026-01-12 11:58:27] ZIP archive created: Click here to download

    [2026-01-12 11:58:27] Wrapping up

    [2026-01-12 11:58:27] Done! Finished in 00:08:11

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.