SOLVED mod_userdir broken since cPanel 66

[Kent Brockman]

Hello guys, I want to report a possible bug starting on cPanel 66: since the upgrade from version 64, all the IP/hostname accesses that used to work normally are now showing the "not supported" message.

This must be something broken in this release. I noticed this happens specifically with WordPress sites. Folders with PHP sites without .htaccess files are working ok.

Can you try to reproduce this?

Thanks!

 

[cPanelMichael]

Hello,

Internal case CPANEL-15459 is open to address an issue where enabling the recommend "search /home directory and below" setting for the .htaccess optimization feature in cPanel version 66 breaks Mod_Userdir functionality. I'll monitor this case and update this thread with more information as it becomes available. In the meantime, you can browse to "WHM >> Home >> Service Configuration >> Apache Configuration >> Global Configuration" and set "Optimize .htaccess (AllowOverride)" to "Search "/" and below (No optimization, Search Full Path)" as a workaround.

Thank you.

 

[cPanelMichael]

Hi @Kent Brockman,

It looks something else might have lead to the issue you are facing, as we have been unable to reproduce this issue in a test environment. Could you let us know the output from the below commands on an affected system?

rpm -qa|grep passenger
rpm -qa|grep ruid2
rpm -qa|grep itk
/usr/local/cpanel/bin/rebuild_phpconf --current
ls -al /var/cpanel/templates/apache2_4/|grep local

Thank you.

 

[Kent Brockman]

Hi @Kent Brockman,

It looks something else might have lead to the issue you are facing, as we have been unable to reproduce this issue in a test environment. Could you let us know the output from the below commands on an affected system?

rpm -qa|grep passenger
rpm -qa|grep ruid2
rpm -qa|grep itk
/usr/local/cpanel/bin/rebuild_phpconf --current
ls -al /var/cpanel/templates/apache2_4/|grep local

Thank you.

OK, here it is.

On cPanel 66, where mod_userdir is broken:

[root ~]# rpm -qa|grep passenger
[root ~]# rpm -qa|grep ruid2
[root ~]# rpm -qa|grep itk
[root ~]# /usr/local/cpanel/bin/rebuild_phpconf --current
DEFAULT PHP: ea-php70
ea-php54 SAPI: cgi
ea-php55 SAPI: suphp
ea-php56 SAPI: cgi
ea-php70 SAPI: cgi
ea-php71 SAPI: cgi
[root ~]# ls -al /var/cpanel/templates/apache2_4/|grep local
-rw-r--r-- 1 root root   200 May  1 22:46 000-local_template_check.json

On cPanel 64, where mod_userdir does work well:

[root ~]# rpm -qa|grep passenger
[root ~]# rpm -qa|grep ruid2
[root ~]# rpm -qa|grep itk
[root ~]# /usr/local/cpanel/bin/rebuild_phpconf --current
DEFAULT PHP: ea-php70
ea-php55 SAPI: suphp
ea-php56 SAPI: cgi
ea-php70 SAPI: cgi
ea-php71 SAPI: cgi
[root ~]# ls -al /var/cpanel/templates/apache2_4/|grep local
-rw-r--r-- 1 root root   200 May  1 22:19 000-local_template_check.json

Any other places to look for differences?

 

[Edward Solomon]

I've been encountering the same problem. Here is the output of the same set of commands on my VPS:

[email protected] [~]# rpm -qa|grep passenger
[email protected] [~]# rpm -qa|grep ruid2
[email protected] [~]# rpm -qa|grep itk
[email protected] [~]# /usr/local/cpanel/bin/rebuild_phpconf --current
DEFAULT PHP: ea-php70
ea-php55 SAPI: suphp
ea-php56 SAPI: suphp
ea-php70 SAPI: suphp
[email protected] [~]# ls -al /var/cpanel/templates/apache2_4/|grep local
-rw-r--r--  1 root root   200 May  1 21:50 000-local_template_check.json

 

[cPanelMichael]

Hello,

Thanks for the additional information. We were able to reproduce the issue after further testing. I'll update this thread again once we publish a resolution.

Thank you.

 

[Mikhail]

Do we have an update on this it's killing my business!

 

[Fraser-Hannah]

This is causing us a real issue as well - is there any idea of a timescale to get this fixed?

 

[cPanelMichael]

This is causing us a real issue as well - is there any idea of a timescale to get this fixed?

The resolution should be included in the next cPanel 66 build that's published. We don't have a specific time frame to offer, but I'll update this thread as soon as it's released.

Thank you.

 

[edgemyster]

This is also a problem for me. The temporary workaround that has worked for me in meantime has been to change the PHP Handler for the various versions from CGI to SUPHP... and then enabling PHP-FPM for any sites that are still having problems.

 

[edgemyster]

UPDATE: Given my symptoms were the same and the problem sprouted up at the same time, I assumed I had a similar issue. The problem compounded itself when I noticed that scripts in the cgi-bin directories were now failing whereas they worked fine before the update. However, I was able to fix this issue in the following way. I went into EasyApache 4 ("Customize") to look at the status of mod_cgid and discovered that MANY of the packages listed there indicated they could be "Updated." Once I provisioned the update across these packages, everything began functioning properly again. Sorry if this is unrelated, but I wanted to post this in the event it helped someone else.

 

[cPanelMichael]

Hello,

This is fixed in the most recent EasyApache 4 update:

1.0-111 - EA-6733: Ensure .htaccess is read with mod_userdir and htaccess optimizations

You can use the "yum update" command to update your system to the latest EA4 RPMs if automatic updates are disabled.

Thank you.

 

[kenlaws]

Hey, sorry to be dense about this, but I want to be sure that a) I have this problem and b) I know how to fix this problem.

I have "standard" WordPress installs, up-to-date, with the standard WordPress .htaccess files at the root public_html level, successfully running on PHP 7.1 up until a few days ago.

Now, while the target post loads, none of the theme or js files load. (i.e., /wp-content/themes/klog/styles.css.) 404 not found.

This is the problem we're talking about here, correct?

Michael: Thank you for keeping us up-to-date on a fix. Sadly, since I am a dunce, can you give me some slightly more step-by-step instructions? I tried running System Update as well as yum update, but both claim I'm up-to-date.

I'm running v66.0.18.

 

[cPanelMichael]

Now, while the target post loads, none of the theme or js files load. (i.e., /wp-content/themes/klog/styles.css.) 404 not found.

This is the problem we're talking about here, correct?

Are you accessing the URL with Apache Mod_Userdir (e.g. IP/~username/)? If not, the issue you described seems more likely to relate to the following thread:

SOLVED - Latest cPanel Update causes 404 errors

Thank you.