Search results

As far as I am familiar it supports also redis. Can it be used with redis, instead of varnish ?

Thank's again ;)

I have some php problems. When I run: magento indexer:reindex it says magento supports php5.5.0 or later, when I check php -v it returns php 5.4.16 (cli) How can I run magento indexer:reindex with php 5.6 or php7

Hi, Several days ago reported similar problem https://talk.plesk.com/threads/problems-with-magento-2.338115/ and for me the solution was: chmod 1733 /var/lib/php/session chown root:root /var/lib/php/session It seems like it's related to this problem...

Hi @UFHH01 it seems like the issue is related to this thread: https://talk.plesk.com/threads/pppm-4558-php-session-savepath-error-after-12-5-update-32.338054/

Thanks mate ;) that helped. But what could cause that issue, my plesk install was without any modification.

On my VPS I have two Magento 2 test installs. Both installs begin to return the error below: There has been an error processing your request Exception printing is disabled by default for security reasons. Error log record number: XXXXXXXXXXXXXXX As I said these are some test installs and I...

can we use this redis module with php 7.0.6

I had similar problem, the solution was to add rule in plesk firewall 'allow all' from my ip.

Thanks @Lloyd_mcse I will check that later.

Hi, I have B rating because of: This server supports weak Diffie-Hellman (DH) key exchange parameters. Grade capped to B. What I have to do to have A grade

Try different theme with woocommerce. Sometimes some theme files overide some woocommerce files.

For me it seems works fine.

I have the same issue, standart install, I have tried different PHPs and none of them passed the magento 2 check

Exactly that was the issue. From 10 domains only on 2 domains and 1 subdomain were with that issues. After little bit digging I checked the IPs in fail2ban ban list, two of them were my vps extra IPs. When I added them in trusted list, everything worked.

@custer Thanks for the update.

Strange things happens! I have found the cause of the problem, some of the server IPs were blocked by Fail2Ban. I have moved them to trusted list and now everything is fine.

On some of the domains I have begin to get 502 Bad Gateway error. When I checked the log, there is: 3229#0: *67 connect() failed (111: Connection refused) while connecting to upstream It's pnly on some domains and when I set "FPM application set by nginx" it seems fork fine I saw that, this...

There is no easy workaround. It is a known issue and as far as I know plesk team is working on it. Regards

There are several threads about this topic and there is no solution yet. It was working fine in plesk 12.