Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion -
Inviting everyone to the UX test of a new security feature in the WP Toolkit
For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.
Resolved Run cron with user 'psacln' && can't modify when created
- Thread starter dariusju
- Start date
psacln is the default group name, not the user name. The file owner (user) is the one you've scratched out in your screenshot. All cronjobs are run as the domains system user. For security reasons each webspace runs with it own user, to prevent other (system) users from accessing their webspace.
Why would want to change the file owner/user?
Why would want to change the file owner/user?
dariusju
Basic Pleskian
What you suggest to chose? I choosed root so it created file with root ownership.
It so because cron running makes log file it was not before, so ownership is broken when website try to access that log file.
dariusju
Basic Pleskian
I found that I need create schedule tasks from websites n domains, not from tools n settings.
