⚑
LiteSpeed

Configuring LiteSpeed SSL Offloading in Plesk

πŸ“… 10 October 2026 ✏️ 10 October 2026 ⏱ 5 min leestijd

Learn how to properly set up SSL offloading with LiteSpeed in Plesk, including common mistakes and a step-by-step working configuration guide.

SSL offloading means that SSL traffic is handled by a layer in front of the server (such as a load balancer or proxy), while the web server itself processes unencrypted traffic. With LiteSpeed, you configure this via the correct headers and listener settings, so your application still knows that the original connection was made over HTTPS. This article shows you how to set this up correctly in combination with Plesk, and which pitfalls to avoid.

What is SSL offloading and when do you use it

With SSL offloading, the encryption of traffic is handled by a device or service in front of the web server, such as a load balancer, CDN, or reverse proxy. The web server itself then simply receives HTTP traffic, but must know that the original visitor came in via HTTPS. This is important for correct redirects, cookies, and security headers.

You typically use SSL offloading in situations with multiple servers behind a load balancer, or when an external party (such as a CDN) manages the SSL connection. For a single server with direct SSL via Plesk, offloading is usually not necessary; a regular SSL certificate on the server itself is sufficient.

πŸ’‘ Tip: Not sure whether you need offloading? If you only use one server without an intermediary proxy, you can probably just set up direct SSL without offloading.

Configuring LiteSpeed for SSL offloading

LiteSpeed needs to know that incoming HTTP traffic was actually HTTPS. You arrange this with the X-Forwarded-Proto header, which is sent along by the layer in front of the server. LiteSpeed reads this header and adjusts the protocol internally, so that scripts and redirects work correctly.

In the LiteSpeed WebAdmin console (or via the configuration files), you set the server to trust this header. This is usually done under the listener settings, where you specify which upstream IP addresses are trusted as the source of SSL-offloaded traffic. Only trust the IP addresses of your own load balancer or proxy, never all traffic, to prevent abuse.

In addition, you need to make sure that applications such as WordPress or frameworks recognize the forwarded header. Many CMS systems need a separate setting for this in the configuration file, for example to prevent a redirect loop from occurring between HTTP and HTTPS.

Checking settings in Plesk

In Plesk, you’ll find the SSL/TLS settings of a domain under the website and domain settings. Here you check whether the certificate is correctly linked and whether the redirect to HTTPS is active. With offloading, it’s important that this redirect doesn’t happen twice: both the proxy and the web server should not independently redirect, as this creates a loop.

Also check the Apache and nginx settings (which Plesk can use alongside LiteSpeed) for any conflicting rules. At Tandata, you’ll find these settings clearly laid out in the Plesk panel, including the SSL certificate status per domain.

VisitorHTTPSLoad Balancer(SSL offload)HTTP + headerLiteSpeedweb server

Solving common problems

The most common complaint with SSL offloading is an endless redirect loop. This usually happens because both the proxy and the web server try to redirect to HTTPS, while the web server internally continues to see the traffic as HTTP. First check whether the forwarded header is being correctly passed on and recognized.

Another problem is that cookies marked as “secure” don’t work, because the application thinks the connection is unencrypted. Make sure your application or framework is set up to trust the forwarded header, not just the web server.

A mix of content (images or scripts still loaded via HTTP) can also occur if the application itself generates links based on the wrong protocol. This is usually solved by checking the base URL or site URL setting in your CMS.

1

Check the source of SSL termination

Determine whether SSL is actually handled by a layer in front of the server, and note its IP address.

2

Set trusted IPs in LiteSpeed

Only add the IP of your proxy or load balancer as a trusted source for forwarded headers.

3

Check redirect settings in Plesk

Make sure there’s no double redirect to HTTPS, by both the proxy and the web server.

4

Test the headers and cookies

Use the browser console to check whether the correct headers are coming in and whether cookies are correctly marked as secure.

Do you have a question about your configuration that you can’t figure out yourself? The knowledge base of Tandata contains more articles about SSL and server settings, and via WhatsApp, ticket, or email, the support team is also available at night to help with specific configurations.

Frequently Asked Questions

Do I need SSL offloading with one server?

Usually not. SSL offloading is mainly useful with multiple servers behind a load balancer or when using an external CDN. With one server, a direct SSL certificate is sufficient.

Why do I get a redirect loop after setting up offloading?

This usually happens because the web server still sees the incoming traffic as HTTP and redirects it to HTTPS again, while the proxy has already handled that. Check the forwarded header.

Does SSL offloading work with free SSL certificates?

Yes, the certificate is then installed on the layer in front of the server (proxy or load balancer) instead of on the web server itself.

Do I need to adjust my CMS for SSL offloading?

Often, yes. Many CMS systems need a setting to trust forwarded headers, otherwise problems arise with cookies or redirects.

Conclusion

SSL offloading with LiteSpeed works well once you correctly configure and trust the forwarded headers from the right source. Always check for double redirects and test cookies and headers after every change. For most standard websites with a single server, direct SSL is actually simpler and sufficient.

View web hosting β†’

Was dit artikel nuttig?