Fix LiteSpeed Cache & QUIC
Budget: $10 – $30 USD
LiteSpeed Cache has stopped talking properly to QUIC.cloud on my WordPress site after I tweaked a few settings. Since then the cache simply does not kick in and QUIC.cloud keeps reporting “unexpected WordPress response”. I also need a simple redirect put in place for one login-related URL.
Here is what has to happen:
• Re-establish full connectivity between QUIC.cloud nodes and all WP REST endpoints, making sure the WP API key is recognised.
• Inspect LiteSpeed Cache settings, undo anything I may have mis-configured, and get caching working again.
• Verify that no firewall rule or server security layer is blocking QUIC.cloud requests.
• Optimise final LiteSpeed, CDN and QUIC.cloud settings for performance so the cache actually serves pages.
• Add the quick redirect for the login item and confirm it works without breaking anything else.
I’ll provide full WordPress, cPanel/SSH and QUIC.cloud access as soon as we start. Once you are done I expect to see a green connection status in LiteSpeed Cache, pages served from cache, and the redirect functioning.
Here is what has to happen:
• Re-establish full connectivity between QUIC.cloud nodes and all WP REST endpoints, making sure the WP API key is recognised.
• Inspect LiteSpeed Cache settings, undo anything I may have mis-configured, and get caching working again.
• Verify that no firewall rule or server security layer is blocking QUIC.cloud requests.
• Optimise final LiteSpeed, CDN and QUIC.cloud settings for performance so the cache actually serves pages.
• Add the quick redirect for the login item and confirm it works without breaking anything else.
I’ll provide full WordPress, cPanel/SSH and QUIC.cloud access as soon as we start. Once you are done I expect to see a green connection status in LiteSpeed Cache, pages served from cache, and the redirect functioning.