Error 403 when using parameter on main page of Drupal/CiviCRM

[edvanleeuwen]

I know it is a vague title, but I am faced with the fact that I am getting a 403 when I enter a specific command on a specific server which has Drupal and CiviCRM: https://www.domain.com/civicrm/?reset=1

Other commands (e.g. https://www.domain.com/civicrm/dashboard or https://www.domain.com/civicrm/view?reset=1) are working well.

I have looked into .htaccess, settings.php and the ownership of files and directories. But they seem to be okay as far as I can tell.

The reason that I pose the question here, is that I think this does not have anything to do with the specific applications, as this is working fine on my other TAP environments.

Does anyone have a pointer where to look further? Or direct me to another place where I can pose this question?

Thanks in advance.

 

[factor]

working fine on my other TAP environments.

Are your other Environments DA? Are they all updated?
On the offending system
New Server?
What OS? What PHP version? Did you compare Application requirements for the said softwares?
In general are there differences on the good system and the bad?

 

[edvanleeuwen]

Thanks, Brent. All environments are DA. Everything updated, both OS and CB.
I have diff-ed the applications and noticed not differences. No new server. Centos 7, PHP 7.3. Did several rewrite_confs, no luck.

 

[edvanleeuwen]

Ok, I set up Apache logging and got:

AH01276: Cannot serve directory /home/user/domains/domain.com/private_html/civicrm/: No matching DirectoryIndex (index.php,index.html,index.htm) found, and server-generated directory index forbidden by Options directive, referer: https://www.domain.com/civicrm/dashboard

If I enter https://www.domain.com/civicrm/dashboard it works perfectly.

 

[edvanleeuwen]

Finally figured it out. There was an extra civicrm folder in the webroot instead of only in the sites/all/modules folder. Deleted the one in the webroot which did the trick.