• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Apache user changes with directive. - Why?

Sebastian

New Pleskian
When I run a simple php web page that echos out the apache user with
PHP:
echo exec('whoami');
it gives me the expected system user, e.g.
Code:
bob

When I run the same but with an alias directive in apache settings:
Code:
AliasMatch /appname(/.*)? /var/www/vhosts/domain.dev/httpdocs/apps/appname/$1
Alias /appname /var/www/vhosts/domain.dev/httpdocs/apps/appname
<Directory "/var/www/vhosts/domain.dev/httpdocs/apps/appname">
    <IfModule sapi_apache2.c>
        php_admin_flag engine on
    </IfModule>
    <IfModule mod_php7.c>
        php_admin_flag engine on
    </IfModule>
</Directory>
the user changes to
Code:
www-data
Question: Why? And how can I avoid this?
 
Last edited:
I think that explanation in this thread could be interesting for you Resolved - apache run whit customer user not whit www-data
I read this before, but it does not help here.
What UFHH01 points out there is a warning not to mess around with config files to force apache to use another user. And I can second that.
E.g. I have played around with /etc/apache2/envvars and changed the APACHE_RUN_USER and APACHE_RUN_GROUP, but that (at least) broke the Plesk log file viewer, so I had to reverse it.
 
Back
Top