You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are the following requirements to use AccelerateWP:
1463
1462
* the server must have CloudLinux Shared PRO license;
1464
-
* the server must be powered with cPanel.
1463
+
* the server must be powered with cPanel or Plesk.
1465
1464
1466
1465
1467
1466
### Administrator interface
@@ -1474,7 +1473,7 @@ To provide best experience,
1474
1473

1475
1474
1476
1475
By toggling the `Enable AccelerateWP for all users` an administrator provides end-users with AccelerateWP feature.
1477
-
Once the feature suite is enabled by administrator, end-users will see an AccelerateWP tab in their cPanel interface and be able to activate the optimization feature.
1476
+
Once the feature suite is enabled by administrator, end-users will see an AccelerateWP tab in their control panel interface and be able to activate the optimization feature.
1478
1477
1479
1478
#### Suites usage statistics
1480
1479
Once at least one feature suite is enabled, the AccelerateWP usage statistics is shown.
@@ -1566,7 +1565,7 @@ If you would like to stop using AccelerateWP, toggle the `Enable AccelerateWP fo
1566
1565

1567
1566
1568
1567
This operation will:
1569
-
* disable AccelerateWP tab in users' cPanel interface
1568
+
* disable AccelerateWP tab in users' control panel interface
1570
1569
* disable all AccelerateWP optimization suites
1571
1570
* deactivate all optimization features for all users
1572
1571
@@ -1583,21 +1582,14 @@ In case if AccelerateWP Premium is active, the auxiliary monitoring daemon `clwp
1583
1582
### FAQ
1584
1583
1585
1584
#### With which panel can I use AccelerateWP?
1586
-
Currently AccelerateWP is compatible with cPanel only.
1585
+
Currently AccelerateWP is compatible with cPanel and Plesk.
1587
1586
1588
-
If you are interested in supporting Plesk or DirectAdmin control panels, please record your demand on our feature portal respectively:
1589
-
* [AccelerateWP for Plesk](https://features.cloudlinux.com/c/13-acceleratewp-for-plesk?utm_medium=social&utm_source=portal_share)
1590
-
* [AccelerateWP for DirectAdmin](https://features.cloudlinux.com/c/15-acceleratewp-for-directadmin?utm_medium=social&utm_source=portal_share)
1591
-
1592
-
#### Does WP Accelerate tool support the DirectAdmin control panel? Do you plan to integrate it with Plesk?
1593
-
Currently AccelerateWP is compatible with cPanel only.
1587
+
If you are interested in supporting DirectAdmin control panel, please record your demand on our feature portal:
1594
1588
1595
-
If you are interested in supporting Plesk or DirectAdmin control panels, please record your demand on our feature portal respectively:
1596
-
* [AccelerateWP for Plesk](https://features.cloudlinux.com/c/13-acceleratewp-for-plesk?utm_medium=social&utm_source=portal_share)
1597
1589
* [AccelerateWP for DirectAdmin](https://features.cloudlinux.com/c/15-acceleratewp-for-directadmin?utm_medium=social&utm_source=portal_share)
1598
1590
1599
1591
#### Is it possible to use AccelerateWP on a non-control panel server?
1600
-
No, AccelerateWP is compatible with cPanel only.
1592
+
No, AccelerateWP is compatible with cPanel and Plesk.
1601
1593
1602
1594
#### Do you plan to enable support of Nginx server?
1603
1595
This is a part of our very long term plans, thus not expected in the nearest future.
@@ -1624,7 +1616,7 @@ Check daemon status using `service clwpos_monitoring status` and its main log: `
1624
1616
In order to make use of AccelerateWP Premium Object Caching feature, the loaded Redis extension is required for the end-user's website.
1625
1617
End-users will not be able to activate the Object Caching feature until Redis extension configuration is incomplete.
1626
1618
1627
-
Corresponding incompatibility warning will be displayed in cPanel User interface:
1619
+
Corresponding incompatibility warning will be displayed in control panel's User interface:
1628
1620
1629
1621

1630
1622
@@ -1634,7 +1626,7 @@ The Redis extensions are configured for all installed and supported PHP versions
1634
1626
1635
1627
or you can trigger the utility manually:
1636
1628
```
1637
-
/usr/sbin/enable_redis_for_ea_php
1629
+
/usr/sbin/enable_redis_for_panel_php
1638
1630
```
1639
1631
1640
1632
All errors will be displayed in standard output and logged into `/var/log/clwpos/main.log`.
@@ -1656,7 +1648,7 @@ All errors will be displayed in standard output and logged into `/var/log/clwpos
1656
1648
rpm -q ea-php74-php-redis
1657
1649
yum install ea-php74-php-redis
1658
1650
```
1659
-
8. Check Redis `ini` file is present by running the following command:
1651
+
2. Check Redis `ini` file is present by running the following command:
1660
1652
```
1661
1653
ls /opt/cpanel/ea-phpXY/root/etc/php.d/ | grep 50-redis
1662
1654
```
@@ -1665,7 +1657,7 @@ All errors will be displayed in standard output and logged into `/var/log/clwpos
1665
1657
ls /opt/cpanel/ea-php74/root/etc/php.d/ | grep 50-redis
1666
1658
```
1667
1659
Try reinstalling the package if `ini` file is missing.
1668
-
13. Make sure Redis module is loaded under specific user by running the following command:
1660
+
3. Make sure Redis module is loaded under specific user by running the following command:
1669
1661
```
1670
1662
su -c "php -m | grep redis" <username>
1671
1663
```
@@ -1682,24 +1674,26 @@ All errors will be displayed in standard output and logged into `/var/log/clwpos
1682
1674
ls /opt/alt/php74/usr/lib64/php/modules | grep redis.so
1683
1675
redis.so
1684
1676
```
1685
-
6. If the Redis module is missing:
1686
-
7. install the `alt-phpXY-pecl-ext` package manually
1687
-
8. run the Redis configuration script `/usr/share/cloudlinux/wpos/enable_redis_for_alt_php.py`
1677
+
2. If the Redis module is missing:
1678
+
1679
+
a. Install the `alt-phpXY-pecl-ext` package manually
1680
+
b. Run the Redis configuration script `/usr/share/cloudlinux/wpos/enable_redis_for_alt_php.py`
1688
1681
1689
-
All errors will be displayed in standard output and logged into `/var/log/clwpos/main.log`.
1690
-
10. If the Redis module is present for a particular php version, but the incompatibility issue persists, re-check the following:
1691
-
11. make sure the Redis module is loaded under user:
1682
+
All errors will be displayed in standard output and logged into `/var/log/clwpos/main.log`.
1683
+
3. If the Redis module is present for a particular php version, but the incompatibility issue persists, re-check the following:
1684
+
1685
+
a. Make sure the Redis module is loaded under user:
1692
1686
```
1693
1687
su -c "php -m | grep redis" <username>
1694
1688
```
1695
-
13. check the required extensions are enabled in `php.ini`:
1689
+
b. Check the required extensions are enabled in `php.ini`:
1696
1690
```
1697
1691
cat /opt/alt/phpXY/etc/php.ini | grep redis.so
1698
1692
cat /opt/alt/phpXY/etc/php.ini | grep json.so
1699
1693
cat /opt/alt/phpXY/etc/php.ini | grep igbinary.so
1700
1694
```
1701
1695
1702
-
Enable missing extensions manually.
1696
+
c. Enable missing extensions manually.
1703
1697
1704
1698
1705
1699
#### End-users of AccelerateWP encounter PHP-related issues during feature activation
@@ -1709,7 +1703,7 @@ End-users may encounter PHP-related errors while activating the AccelerateWP fea
1709
1703
1710
1704
The general examples of possible reasons are:
1711
1705
* broken PHP binaries
1712
-
* missed PHP files
1706
+
* missing PHP files
1713
1707
* etc.
1714
1708
1715
1709
To check that this issue is caused by PHP itself, call any PHP command, for example:
0 commit comments