Search Engine: Elastic

Article ID: 130995, created on Jun 13, 2017, last review on Jun 13, 2017

  • Applies to:
  • Operations Automation

Symptoms

Any calls to a particular APS application endpoint end with 403 Forbidden error.

As an example, a mozyPro upgrade task fails with:

Internal error: APSC: Upgrade to ver. 2.1-16 : resource 4ca24197-56b6-464a-b296-099ea9033746 of type 'mozyPro' (http://www.mozy.com/mozyProAPS2/mozyPro/1.2) for APS application 'mozy APS2-2.1-16' : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access /mozy/mozyPro.php
on this server.</p>
</body></html>

SSL is enforced for the application directory:

# cat /var/www/html/mozy/.htaccess
...
  RewriteCond %{HTTPS} !=on

Cause

.htaccess file inside the application directory is configured to force SSL, while the endpoint is set to use HTTP connection (check URL at **TOP > Applications > application_name > Instances > instance_name > General).

Resolution

Edit /var/www/html/<application_name>/.htaccess file and replace:

  RewriteCond %{HTTPS} !=on

with:

  RewriteCond %{HTTPS} !=off

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF