Plesk default page after activating cloudflare proxy

Hi, i´m using plesk obsidian with litespeed webserver.
I switched to cloudflare nameserver, but after activating cloudflare proxy instead of my website i just see plesk default page.

When i disable proxy of cloudflare its working again.
Any ideas?


Did your site work fine on HTTPS before? If not, then that’s the issue and you need to fix that first.

Thanks for your answer.
Yes, SSL is working fine.

Not now, if it was working before you used Cloudflare.

1 Like

Yes, before it was working fine too. No problems with SSL. Using let´s encrypt if its important.

All right, what’s the domain?

shorturl .at/bkzPZ

Can you post a screenshot of your DNS screen? You can redact the IP address, but leave the last number.

Alternatively you can also pause Cloudflare.

paused cloudflare.

just checked logs and saw this:
2023-05-23 18:24:11.691487 [INFO] [28022] [T0] [] File not found [/var/www/vhosts/default/htdocs/assets/static/mdz-logo.6d7e5a9.1e92ad05ceea152cf4d146ea17908f3d.webp]
2023-05-23 18:24:11.695133 [INFO] [28022] [T0] [] File not found [/var/www/vhosts/default/htdocs/assets/static/greenstein-logo-font.4f46be4.53fdeb5b54edf0db332a9ca66540ddc4.svg]
2023-05-23 18:27:47.702690 [INFO] [28021] [T0] [] File not found [/var/www/vhosts/default/htdocs/webdesign-hannover/]

it seems after using proxy mode litespeed delivers different directory (/var/www/vhosts/default/htdocs/ instead of /var/www/vhosts/ but i don´t know why

There used to be an issue that a domain was occasionally stuck with another provider, but that should be fixed and I don’t think this is the issue here.

Do you have any Workers in place? Any rules set up on Cloudflare? Verify that your server configuration does not handle requests from the proxies differently.

And you can delete the screenshot at this point. I wanted to verify if you had incorrect DNS settings.

No, its clean cloudflare account without any customizations. I´m not sure how i can tell litespeed to handle it like internal traffic, or what do you mean?

And you can confirm that requests still reach your server when proxied, correct?

Although it should not be the issue, can you also confirm that your encryption mode on Cloudflare is Full Strict?

Yes, exactly. Its the output of my server. I created testfile in /var/www/vhosts/default/htdocs named test_cloudflare. its available:
signatur. greenst /test_cloudflare
this domain is still proxied by cloudflare, so i can also confirm that its loading wrong directory.

SSL was on flexible, but i changed to full strict now

In that case it won’t be said stuck configuration, as that wouldn’t reach your server.

The whole thing is a bit weird and unusual, but at this point my best educated guess is that your server is filtering for Cloudflare proxy addresses and then possibly rewrites the host header. I can’t say that for sure of course, but given the available information I’d would recommend to take a good look at the server configuration, especially anything on security.

It actually does load fine via the proxies at this point. Did you change anything?

It should not have been the change of the encryption mode, but the one you had before was insecure anyhow.

1 Like

Your server does a 301 redirect from to, so it wouldn’t be working on Flexible, as flexible always connects to your server using http. But it is curious that instead of a redirect loop, you webserver displayed the default page.

1 Like