• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

404 And TimeOut Error When Loading "Extensions" And "Add or Remove Components" Pages

T

TravisPM

Guest
My Setup Is As Follows:

I'm using CentOS 6.3, 64 bit.

Plesk 11.09, Update #9.

External domain to access Plesk
https://server.mydomain.com:8443/

I'm using 1:1 NAT to a local IP address:
https://10.5.1.1:8443/

I am using a resolvable FQDN.

Problem 1:
When clicking on the Server Tab and then the Extensions Tab I get a 404 Error:

"The requested URL /smb/redirect/pleskin/root//plesk/modules/ was not found on this server."

URL that is trying to be loaded:

https://server.mydomain.com:8443/smb/redirect/pleskin/root/%2Fplesk%2Fmodules/?dst=%2Fadmin%2Fmodule%2Flist&src=%2Fsmb%2Fsettings%2F&srcController=SettingsController

All other links that I've used in Plesk work fine.

Problem 2:

Clicking on "Add or Remove Components" loads the following URL:

https://10.5.1.2:8447/add_components.html?secret=&locale=en-US

Being a local IP address it comes up with "This web page is not available".

I assume is should be loading the following instead as it works fine:

https://server.mydomain.com:8447/add_components.html?secret=&locale=en-US
 
Thank you for your reply abdi

I was aware of that post, but it was my understanding that the post you referred to was for Plesk 10.
A solution was never posted in any case.

It certainly does look like the same/similar problem that's continuing in Plesk 11.

Anyone got a resolution?
 
Out of curiosity, had you upgraded the plesk database with bootstrapper repair ? /usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair
 
My bad, it ended up being a web application firewall on the Plesk port.

As soon as I disabled it on that port, the two issues where no longer there.
 
Back
Top