Search Engine: Elastic

Article ID: 132434, created on Mar 23, 2018, last review on Mar 23, 2018

  • Applies to:
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3

Symptoms

Customer has Apache website site 1 located on NG Web-cluster/server. On attempt to access the site error 404 - not found is shown

Cause

Customer has another website site 2 based on APS-application WordPress in the same webspace. Site 2 is located in root directory of the webspace.

In result there is a redirect rule in file PATH_TO_WEBSPACE/webspace/.htaccess:

RewriteRule "^httpdocs(|/.*)$" /siteapps/WordPress-_ID_/htdocs$1
RewriteRule "^httpsdocs(|/.*)$" /siteapps/WordPress-_ID_/htdocs$1

These redirect rules forward requests to site 1 to unexisting location. In result error 404 - Not Found is shown

Resolution

Change location of site 2 from / to /site_2_name:

CCP > Websites > site 2 > tab Web > Edit

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e dd79f16c76b9dca75205ab5e9f5465ea

Email subscription for changes to this article
Save as PDF