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.
Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
Thank you in advance for your patience and understanding on the matter.
Hi @Djjh!
Seems you upgrade is incomplete: /usr/local/psa/version shows 12.0 but microupdates.xml shows 12.5.
Try this KB article: http://kb.odin.com/127211
1. Does this user present in /etc/passwd ?
2. Does this user present in the list of sys users in plesk db?
# plesk db "select login, home from sys_users"
Hi @sdmx80!
Try to run:
# plesk repair ftp
It can clean up orphaned FTP users. The root cause can be that FTP user could be locked by some process while removal.
I checked on our test environment and I can confirm that Outgoing Limiting and MagicSpam conflict with each other. But both of them can filter outgoing spam. I suggest you to choose one of them.
Hi @roadrash!
Could you please clarify several points:
Do you want to have some wp-plugins installed by default when user installs a new WordPress instance?
Do you want to put some .htaccess by default when user installs a new WordPress instance? Or you just have .htaccess file and you want...
Hello, @tschorakl!
This behavior means you are switched to Power User View but doesn't have any admin subscriptions.
Could you please answer several questions:
1. What version of Plesk did have before upgrade to Plesk 12.5?
2. What license edition do you use?
Hi @jens1!
If you use Plesk 12.5 you can use Plesk self-repair feature to fix password of apsc user. It's made in scope of database repair aspect:
# plesk repair db
I suppose your upgrade failed with some error from yum and now you have packages both from Plesk 12.0 and Plesk 12.5.
You can check it by:
# yum check
And see it'll report the conflicted packages (errors like "psa-12.5.30-cos7.build1205150826.19.x86_64 is a duplicate with...
Hi @kiav!
Unfortunately there is no such opportunity on Linux. Could you please describe what is your case and maybe we can advice you some workaround.
Tried with manually installed wordpress but still cannot reproduce the issue in our test environment.
By "stopped web hosting" you mean:
1. change hosting type on Hosting Settings screen
2. disable domain
3. or something else?
Hello, @BastienB
Thank you for reporting the issue. I confirm that it's bug with ID PPP-18133 in our internal tracker. I hope it'll be fixed in upcoming microupdates.
Unfortunately, I cannot suggest you any workaround.
Hi @psx01de!
Could you please give some more information:
1. What is your OS (you can place here output of "plesk version" CLI command)?
2. What Plesk version did you use before upgrade to Plesk 12.5.30#7?
Hi @Linulex
Thank you for reporting the issue.
I agree that this notification is a bit annoying but as I see the same behavior was in Plesk 12.0.18 too.
What do you mean by "In plesk 12.0.18 there is an option to dismiss this warning"?