[Resolved] After switch from Apache to LiteSpeed permalinks its not working in Facebook

[Manuel]

Hi,

I'm going crazy after i switched to Litespeed, the permalinks it's not working.

You can see the before-after images, when i paste the link in Facebook Fan Pages, doesn't work.

Do you have any idea how can i fix this issue?

Thanks in advance.

 

[NiteWave]

do you mean the site www.tras...ate.com is powered by litespeed and has problem ?

what's the litespeed version ? we've received bug report relating to facebook and fixed in 4.2.14.
please force-reinstall 4.2.14 or 4.2.15, see if the issue still exists.

ssh to the web server, on command line:
#/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.14
or
#/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.15

 

[Manuel]

Hi Nite,

Let me check with my host and i will let you know.

I also have another issue trying to buy a lease 2-CPU LSWS Enterprise, can you check it?

I will inform you my hosting partner answer,

Thanks.

 

[Manuel]

Hi,

I force-reinstall these versions, and nothing happens,

I will had to use Apache+Nginx meanwhile you fix this issue.

Thanks.

 

[NiteWave]

we'd love to fix bug, but we need reproduce it first. can you give us more information about this "bug".

1. is the website a wordpress site? www.tras...com
2. the "Open Graph Object Debugger" is a facebook tool ?
3. so from the facebook tool, open
http://www.tras....com/cele...-armyland-2014/
has problem? ==> "After Fetch new scrappe info.png" in your first post
when website is served by apache, the facebook can open that URL successfully ? ==>
"Before Fetch new scrappe info.png" in your first post

and just now, I accessed the webpage directly, sometimes it shows normally, sometimes shows
"Error estableciendo una conexión con la base de datos"

since your website is behind cloudflare. you can try serve the page directly instead by cloudflare proxy. see if any difference.

 

[Manuel]

FYR;

This issue is caused by double compressed content. LiteSpeed will compress your site but if you are also compressing within your site code, it will become doubly-compressed. Facebook does not know how to handle this double compression so you see all of that mangled text.

I've updated LiteSpeed to version 5.2.15 now. If this does not fix the issue, I recommend that we disable the compression in LiteSpeed.

When you're testing this issue, I recommend testing using a different post as Facebook may save the shared text for a few hours.

That's why a WiredTree guys told me.

I solve the issue making these changes:

i use *W3 Total Cache*, and i have enabled this option, also i have*
CloudFlare that have thieir HTTP (gzip) compression* , and now *LiteSpeed *you
says that it have too, so, there are 3,

I will disable the W3 Total Cache GZip Compression to check,
http://prntscr.com/4qj7pl

I think this is the issue, i disabled the W3 Total Cache Gzip Compression
and paused CloudFlare and voila! =) the links start to working without any
issues!

I already activate CloudFlare because i use Pro account with WAF to protect
the site, and until now, the links is still working without issues.

I will let you know if the site persists the issue using CloudFlare,

Thanks!

 

[NiteWave]

Thanks for the sharing!
so disable "W3 Total Cache Gzip Compression" has made the magic.

 

[Manuel]

Yes, that's right!