Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
Reached out to support and OAuth steps were created to fill in the missing pieces for a successful install :)
- How to install OAuth PHP extension?
Much appreciated!
Hello,
When proceeding to install Oauth for PHP7 on Debian using the following steps a make error follows at the end.
/opt/plesk/php/7.0/bin/pecl install oauth
install starts and finishes with....
compilation terminated.
Makefile:181: recipe for target 'oauth.lo' failed
make: *** [oauth.lo]...
Hi Anthony,
Okay, I see where the problem is - I updated one node to try out the Premium Email as a test and have since removed. So, what is the best way to correct this now? Rolled back the license to be as it was matching across nodes, but for some reason still in this scenario. What I...
Hello,
When updating a service plan, the following error appears and does not allow the plan to properly sync on one node.
- Reason of failure: The limits on outgoing email messages are switched off
Outgoing mail settings are taken care of by the management node, yet the service node is...
Hi Anthony,
I appreciate your follow-up, basically the log shows the same - such as taking the field (pleskmultiserver_createaccount) shows the following request/response.
Request
<?xml version="1.0" encoding="UTF-8"?><packet version="1.6.8.0"><request-settings>
<setting>...
Hello,
I have Multi-Server all setup and running quite nicely, added the new multi-server module to WHMCS and connection tests to the management node are all good. Now, after the product is all setup and proceed to create for a client the following error appears.
- Error code: 1023. Error...
Indeed a similar error, just on nginx.
Not sure if it was enabled, no changes and from the information in that link - it looks that disabled mode is the only way this will work. Which should mean we are good here, as the feature is disabled - similar but different, what could be causing this...
Okay, after looking through the logs all errors related to nginx.
When proceeding to apache & nginx settings and turning off smart static files processing - all errors cleared, site performs beautifully now.
What could be causing nginx permission errors?
Using repair with fs or web both come back with no errors, mentioning all is 'ok'.
Only the logs show the permission error, what could be causing the repair tool to see all is good yet the error to remain?
Thanks, I had used this very step to make the move, this seemed to go just fine - until creating new WordPress sites.
New sites created prior worked with no permission errors, after the move the errors began.
Any thoughts on what could be the solution?
Hello,
*Updating to a new subject here - as put in the incorrect name...my apologies.
After moving sites from initial default directory to a new /home directory - there are certain permission errors happening following creating new WordPress sites.
Here is some errors showing up in the logs...