Search results

Hello, php -m lists the modules so when I ran /usr/local/bin/php -m|grep ionCube it showed that ionCube is installed and active. When I flush the cache and wait for 10 minutes without visiting the site the command : find . | grep LITEMAGE gives no result. I waited 12 minutes (cron running...

Thanks, I've juste checked and it's not that. We use Cloudlinux's CageFS and phpselector and which php run as that user responds : /usr/local/bin/php and : /usr/local/bin/php -m|grep ionCube ionCube Loader the ionCube PHP Loader

Hello, We are trying litemage 1.0.1 since last night and I'm under the impression that the cache warm up feature isn't working. I set up the following cron : */5 * * * * /bin/sh /home/magentouser/public_html/cron.sh and set : Enable Cache Warm Up to Yes Only Run When Load Is Less Than : 7...

When a new version comes out they wait a few weeks before pushing it to the web interface. You should be able to update from command line if you want to.

We reverted to LS 4 because we got quite a few coredumps with LS 5 build 1. Have forwarded email to your supbug e-mail.

Hello, I was testing on a website with piwik, this doesn't seem to happen on other websites. I found this : http://forum.piwik.org/read.php?2,121502 But it doesn't give any information about why just confirms that it also happens with nginx + SPDY

Thanks, it works on everything except Safari Version 8.0.5 (10600.5.17)

SSLv3 now shows as correctly disabled with nmap but the pages still don't show. ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY in chrome and NSPOSIXErrorDomain:100 in Safari.

The people who manage basic forum support are at a Magento conference at the moment. From what I understand the first line adds a redirect header allows it to pass to the next line which adds a 403 error. It does seem correct according to the following Apache documentation that your code shoud...

Thanks for the update. We will try to be patient ;) (but it won't be easy as LS 5.0 brings so many good things !)

Hello, I didn't know about the nmap script to test available ciphers, very handy thanks ! :) I've just tested on our server and we have exactly the same result. SSLv3 is enabled with LS 5.0 (I've just force updated it) and not on LS 4.2. On LS 4.2 : | SSLv3: No supported ciphers found On...

Any news about this ? While I guess your developpers are working hard to reproduce and fix this issue, it would be nice to have some confirmation that it is being worked apon. Something like "thanks for the info, we have forwarded the info to our developpers…" would have been nice. And sorry...

Hopefully now the specification says http/2 works with both some will start supporting it. Google want's all sites to go full SSL, I can't see that happening in the short time though.

Which browser ? The page shows up fine here but I see nginx and not litespeed… are you behind a CDN ?

I'm not sure that this is even technicaly possible at the moment… but HTTP/2 will exist in the future with and without SSL. If all the routers and the browser were compatible with this, is litespeed 5.0 currently compatible with HTTP/2 without SSL ? Thanks :)

I've just tried changing ciphers for the same ones I use on a nginx server with spdy enabled but I get the same error so I don't think it's a cipher issue.

I've got a bit more info. Just tried 5.0 with latest version of Chrome. I get : ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY Does this mean I'm missing a cipher or something like that ?

Safari is Version 8.0.5 (10600.5.17), Firefox is 37.0.1 Both on mac os Yosemite. I haven't tested on other browsers as both Firefox and Safari both seemed to find a protocol error I presumed this would affect all browsers.

Do we have to set specific ciphers for http/2 to work ? Could it be because I'm using a SPDY compatible browser that HTTPS isn't working with litespeed 5.0 ?

Hello, Just switched to LS 5.0 but SSL sites stopped working giving a protocol error in Safari 8.05 and redirecting to http version in Firefox. The error shown in the browser was : NSPOSIXErrorDomain:100 I've switched back to 4.2 while waiting for this to be fixed.