• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Resolved Run cron with user 'psacln' && can't modify when created

dariusju

Basic Pleskian
Server operating system version
Ubuntu 23
Plesk version and microupdate number
Latest
I don't see to chose this kind of user when creating cron job.

psacln

Also, after creation I can't edit user.
 

Attachments

  • Screenshot_2023-10-03-22-32-04-938_com.vivaldi.browser-edit.jpg
    Screenshot_2023-10-03-22-32-04-938_com.vivaldi.browser-edit.jpg
    331.6 KB · Views: 4
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?
 
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?
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.
 
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.
I found that I need create schedule tasks from websites n domains, not from tools n settings.
 
Back
Top