Plesk 12.x / Linux :: Php-fpm And Wordpress Permalinks
Apr 15, 2015
I've searched and tried every solution to this I could find. When Plesk 12.1 is configured to process php by nginx, I just can't get Wordpress permalinks to work. If I switch permalinks to default the pages will appear, but if I use something like day and date for the permalinks I get a Nginx 404 error. Of course if I'm just using Apache and it can read the .htaccess file everything works fine. I think part of the reason the solutions I find won't work is my main site is static with the wordpress blog in the /blog/ subdirectory. What would I add in Plesk to get permalinks to work correctly with wordpress in a /blog subdirectory. I'd also like to get WP Super cache working as well if possible.
I don't know what's wrong with the server where the wordpress site is hosted. But in the permalinks, index.php must be included in the permalinks (more information here:[url]
What can be fixed in the server so that wordpress permalinks will work correctly?
I have some issues access my files through FTP. I created a new FTP user, that match the domain name, so it is easy for me to terminate access if i choose to delete the domain.
I can only access / see files that i uploaded with that specific FTP user. If i install a plugin inside Wordpress, i can not access those files via FTP.
If i login via SSH, with the root user, i can see all files.
I have tried to add the FTP user to the psacln group, but no luck.
I recently changed the main domain url from website.com to www.website.com, this resulted in 404-errors when i navigated to wordpress...
I found a solution on the internet and updated the records with phpmyadmin [URL] ....
When I click on Login at the the WordPress Installations I'm still being navigated to the old website url. It supprices me that there is no option to change it on Plesk level after wordpress is deployed.
How can i change or update the wordpress path once it is installed in Plesk?
I'm using CentOS 6.2, maybe there is a config file or an database for Plesk?
See the attached jpeg for the complete error message.
All the sites are working okay so we know the databases are accessible and working. We have the latest version of Plesk 12 with micro updates done daily. This is a plain installation with no mods to the system files or software. This is hosted at 1and1.com; our other server at Rackspace found the WP installations without any problems.
Component nameComponent version awstats7.3-14050621.parallels bind9.8.2-0.23.rc1.el6_5.1
i went to server setting and checked manage php with nginx then start getting 404 Not Found nginx. It was clear that it s a problem with the wordpress permanent links so i went in wordpress back-end and switched to default links then it start working but when i switched to permanent link againi got the previous error again
I searched for a while on internet and i found . URL.... So the problem that i have is that i added this piece of code manually in : /var/www/vhosts/system/domaine.com/conf/nginx.conf....Since it s mentioned above
#ATTENTION! # #DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY, #SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
if I try to use the new wordpress service in the admin panel, I get following errors:
By starting a search of wordpress installations: PHP Fatal error: "Die Suche nach WordPress-Installationen wurde mit Fehlern abgeschlossen: Resource with UID 'c94fef81-1552-43e1-ae5b-ce125776caa7' not found."
One installation is found but by open the detail view I get the error "Call to undefined function is_admin() in /usr/share/plesk-wp-cli/php/wp-cli.php(18) : eval()'d code on line 87".
So. Plesk has a button to enable or not enable automatic updates of WordPress installations it knows about. I toggled it and it didn't seem to effect the setting in my wp-config.php file:
//--- disable auto upgrade define( 'AUTOMATIC_UPDATER_DISABLED', true );
which remained like that whatever I did to the Plesk button.
Nor does it seem to set this setting either way: define( 'WP_AUTO_UPDATE_CORE', false );
So. Is it something independent of WordPress? I.e. Plesk goes and gets the updates and applies them? If so - what updates is it getting - major changes or just minor ones?
If I try to fetch manual Wordpress installations, they run in trouble with the Wordpress support (doesn't recognize them). Also if I do a fresh installation of Wordpress, it's recognized first but all changes to plugins or themes within Wordpress are not recognized and handled, also if removing the installation in Plesk and rescanning for installations.
When I visit the Wordpress Toolkit page on one of my servers I get the following error...Internal error: Specified column "name" is not in the row
MessageSpecified column "name" is not in the row File Abstract.php Line179 TypeZend_Db_Table_Row_Exception Go To Previous Page
This server appeard to upgrade successfully, and has the relevant tools installed with no errors on apt-get.Perhaps removing and re-installing the wordpress toolkit will work?
I know it's not specifically a plesk issue, but as I use plesk to resell webs and many users install (manually) wordpress, I thought I'll ask around.I would like to know if this can be done with a single sql select or if I would have to use a script to do this:
- track all mysql databases on my server - find the proper table in each database (as the prefix can be customized, the start of the table name will probably never be the same in two WP installations) - find the proper field in that table and check the WP version and administrator email
and then what I will do is send an email to those adresses advising them to update WP
To be clear i don't mean the wp-config.php admin password for mysql but the wordpress Plesk admin account that is associated with Log in button
For some reason my user has lost his password and is not able to use the Wordpress forgot password - wizard form at the page where you normally logged on.
I have tried to reset the password via Change Account on the WordPress Installation and it came back with the message
Error: Unable to find the specified administrator account in WordPress. Specify the username of your administrator's account in WordPress. This account will be associated with Plesk.
I have tried to add another admin via MySQL with this [URL] ... and that didn't work either.
I read in the Plesk 12 release notes that resellers should have access to the new Wordpress toolkit. However, when I login with a reseller account, the Wordpress tool does not show up in the left-hand side menu. What do I need to do to give resellers access?
My Wordpress Toolkit stops showing the Wordpress Installations.
Instead of that, is showing a yellow sign with the following error:
"Decoding failed: Syntax error"
I found this [URL] ... but it did not work for me.
I decided to reinstall several times my Wordpress site using my Wordpress backup.
The Wordpress installation using the Toolkit works fine, however, when I update Wordpress (core, plugins or theme) within my Wordpress dashboard, the Plesk's Wordpress Toolkit keeps saying there are still updates pending. Also I noticed that if I change the site's name in my Wordpress dashboard, the Plesk Wordpress Toolkit keeps showing the old one. (same happens with languages)
Although my website is working fine, after a while, not matter if I update or not my Wordpress site using the Toolkit, eventually I receive the "Decoding failed: Syntax error" in my Plesk panel.
Plesk version 12.0.18 Update #24, Centos 6.6 Final
In the Wordpress Toolkit several WP installs appear with exclamation mark and title: "A Wordpress installation was previously detected at this path, but it is not operating properly".
Simple... new Plesk 12 includes this fancy feature to tell me which Wordpress plugins and themes need updating (because I obviously can't do this myself). But maybe I don't want to update some plugins (because they've been customized and changed)... how do I....
STOP Plesk 12 from sending me Wordpress update notification emails EVERY DAY!???? The auto-update is off... and EVERY day is sends me (and all of those clients) an ugly email about their Wordpress installations. How do I turn this OFF?
I have installed the Wordpress application. The wordpress url is "server.com/wordpress", but I want to change it to something like "server.com/myblog".
In Plesk, the installation path cannot be changed (at least, it is not under "Change Settings").
Changing the Wordpress installation itself is not that difficult (renaming the folder in httpdocs and changing the siteurl and home parameter in the database), however, in Plesk still the old installation path is shown, and the Plesk interface to Wordpress obviously does not work any more.
How can I change the Wordpress installation path in Plesk?
Version Parallels Plesk v12.0.18_build1200140606.15 os_Ubuntu 12.04 OS Ubuntu 12.04.5 LTS
After a recent update (4.2.1) for Wordpress all of our sites showed issues when editing a page the "Visual editor" would not be available any more.
You would only see nothing where normally html text or WYSIWYG is supposed to appear. Text in editor window has the same color (white) as background (white).
I'm curious if others had same issue?
-- it's affected all websites -- it's not plugin related -- fresh websites with twentytwelve and hello world page have same issue -- disabled mod (did not work)
eventlog:
[Wed Apr 29 15:10:12 2015] [error] [client xx.xx.xx.xx] client denied by server configuration: /var/www/vhosts/my-example-website.org/httpdocs/wp-includes/js/tinymce/wp-tinymce.php, referer: http://my-example-website.org/wp-admin/post.php?post=142&action=editClick to expand...
Wordpress is becoming more and more integrated with Plesk which makes it quite easy to setup a new domain for someone and install Wordpress so he can start.
Often this Wordpress site has to be developed and a better looking site is already available.
By default Wordpress installs in a subfolder /wordpress (I know you can change it by choosing "custom install"). After a while that website is ready for publishing.
To move that website I will have to move the running site to a subfolder and then move the content of /wordpress to the root. This is not sufficient. I then have to do a search and replace on the /wordpress and wordpress/ and replace it with /
No problem there....
But then I have lost Wordpress from the Plesk interface.....
What's the most elegant way to move a Plesk managed Wordpress site?
I don't mind if it stays in its folder (maybe preferrable?), as long as the user doesn't see that "/wordpress" in its URL.
I`ve got a problem with plesk when hosting Wordpress, when using Wordpress navigating between the pages (front-end and back-end) server time seems to be 15 sec.I`ve checked CPU usage and that stays under 5%.
When I install Drupal or Concrete5 or any other application that uses PHP with MYSQL it runs very fast.I`ve already fine-tuned PHP / Apache2 / Nginx & Mysql to get the max possible performance out of it.
What i`m using for hardware: i7 920 2.6Ghz 24GB Ram LSI Raid controller 9260-8i RAID 10, 6 WD Black disks (internal speed goes about 450mb/sec) RAID 1, 2 x Samsung SSD Evo 840
Software: ESXI 5.5, optimised for maximum performance. (no standard config) PLESK VM has 8 cores, 16GB Ram and I/O access priority set to max.
If I move the PLESK VM to the SSD datastore it makes no difference.Again, the problem only happens when i`m installing Wordpress..I Also did a manual install of Wordpress, same issue..I`m going to try the older version of Wordpress (3.9) so see i`m having the same problems..Using the latest plesk 12 on Ubuntu 14 with trail license at the moment.
I'm pretty new to Plesk and would like to setup a testing wordpress website without changing DNS yet. I assume I need to create a webspace for it. But do I use actual domain or an IP address? Wordpress ties up to the domain as far as I know.
We are trying to use the new Wordpress toolkit, but when we try to install an instance it says this:
Contact your service provider for assistance. Upgrade the system PHP CLI to version 5.3.0 or later, or set the correct path to the PHP CLI in the clipath option of the php_handler utility for a custom PHP handler.
Screenshot:
Now that would not be a problem if the requirements were not met, but there are installed PHP versions that are higher than 5.3 and the website is configured to us these versions...
