Fix PrestaShop SSL errors, mixed content warnings, and redirect loops by syncing PrestaShop's own settings with the certificate Flashcloud already issued you. The problem is almost always in PrestaShop's configuration, not the certificate. Flashcloud issues a free Let's Encrypt SSL certificate automatically, about 5 minutes after your domain's DNS points here, and renews it automatically. You don't request it, install it, or renew it yourself.
The most common cause of PrestaShop SSL problems is a mismatch between what PrestaShop thinks its URL is and what's actually being served. PrestaShop stores the shop's base URL and an SSL flag in its own configuration, separate from the certificate itself. Getting those two back in sync fixes almost every case.
Check the certificate is actually issued
Before touching PrestaShop, confirm the certificate is live. In portal.flashcloud.com, go to Services and open your hosting service, then use the cPanel one-click login (see accessing cPanel for how SSO works). In cPanel, open SSL/TLS Certificates and check your domain shows a certificate issued.
If it's missing, the usual cause is DNS: the domain isn't pointing at Flashcloud's nameservers yet, or the A record isn't resolving to your hosting IP. Issuance only fires once DNS resolves correctly. If you recently changed nameservers, give it time to propagate, see changing nameservers for the exact steps at the major registrars.
Force HTTPS inside PrestaShop
Once the certificate shows valid, PrestaShop needs to be told to actually use it. In the back office:
- Go to Shop Parameters > General.
- Set Enable SSL to
Yes. - If available for your PrestaShop version, also enable Enable SSL on all pages, not just checkout, so the whole storefront serves over HTTPS.
- Save.
Older PrestaShop 1.6 installs store this in app/config/parameters.php or the ps_configuration database table as the PS_SSL_ENABLED key. If the back office toggle doesn't stick, that row is the one to check via phpMyAdmin (one-click login from the same Services page in the portal).
Fix mixed content warnings
A padlock warning after enabling SSL almost always means some assets, images, CSS, or JS are still being loaded over http://. This happens when:
- Product images or CMS content have hardcoded
http://URLs from before SSL was enabled. - A theme or module has a hardcoded absolute URL in its templates.
- The shop URL in Shop Parameters > General > Shop URL is still set to
http://.
Update the Shop URL field to https:// first. For hardcoded image or content URLs, PrestaShop's database has a search-and-replace need that's outside the scope of a simple settings change. Run a SQL replace against the relevant tables (ps_product_lang, ps_cms_lang, etc.) via phpMyAdmin, or use a module built for it if you'd rather not write SQL directly.
Redirect loops
If the site loops between http:// and https:// instead of settling on one, you likely have two things fighting: PrestaShop's own SSL redirect logic and an .htaccess rule doing the same thing. Check the root .htaccess file for an existing RewriteCond %{HTTPS} off block. If PrestaShop's SSL setting is already handling the redirect, a duplicate rule in .htaccess is usually the culprit. Remove the duplicate rather than adding a second one. Use cPanel's File Manager to edit .htaccess directly.
Stack notes for PrestaShop
PrestaShop runs fine on Flashcloud's default stack: LiteSpeed with a system default of PHP 8.2, and you can switch a specific PrestaShop install to a different supported version (7.4 through 8.3) from the PHP Version tile in the portal if a theme or module needs an older one. Check your PrestaShop version's documented PHP compatibility before switching. If you installed PrestaShop through Softaculous in cPanel, that's the same environment: switching PHP versions works the same way afterward.
For general speed tuning once SSL is sorted, see how we make your site fast, LiteSpeed and the edge caching layer apply to PrestaShop the same as any other site on the stack.
When to contact support
If SSL/TLS Certificates in cPanel shows no certificate more than a few hours after DNS is confirmed pointing at Flashcloud, or a certificate shows as issued but the browser still reports it as invalid or self-signed, open a ticket from Support in the portal. That's a server-side issuance issue, not a PrestaShop setting, and it's faster for a real person to check directly than to keep testing configuration.