Invalid Links in Panel

[brainforge]

Go into domains, select a domain control panel.

Click on SSL Certificates link I get the following error:

The requested URL /smb/redirect/pleskin/root//plesk/client@11/domain@33/certificate@/root//plesk/client@11/domain@33/mpc-certificates// was not found on this server.

Click on FTP Access I get the following error:

The requested URL /smb/redirect/pleskin/root//plesk/client@11/domain@33/hosting/ftp-users//root//plesk/client@11/domain@33/hosting/web-users//root//plesk/client@11/domain@33/hosting/anonymous-ftp// was not found on this server.

Click on Backup Manager I get the following error:

The requested URL /smb/redirect/pleskin/root//plesk/client@/domain@33/backup// was not found on this server.

Click on Account Additional Services I get the following error:

The requested URL /smb/redirect/pleskin/root//plesk/client@11// was not found on this server.

Go into tool & utilities.
Click on Updates I get problem loading page error:
The URL looks like this:

https://localhost:8447/?secret=spcndmrtqaemyjzapctc&locale=en-US

Works if manually changed to:

https://mydomain.com:8447/?secret=spcndmrtqaemyjzapctc&locale=en-US

------------------------------------------------------------------------------------------------

All these problems turn out to be due to my use of a subdomain and Apache proxy module to access Plesk.
I use this setup as occassionally I need access from behind a firewall which blocks port 8443 and I am always in the habit of typing https://plesk.domain.com instead of https://mydomain.com:8443.

I am sure this did not happen in Plesk 9.

Minor inconvenience but does anyone have any ideas how to modify mod_proxy configuration in vhost_ssl.conf to handle these links correctly, or is it a Plesk issue and up to them to fix?

SSLProxyEngine on
ProxyRequests off
ProxyPass / https://localhost:8443/
ProxyPassReverse / https://localhost:8443/

 

[IgorG]

Make sure that you install Plesk on server with correct and resolvable hostname in FQDN format and you will never see mentioned errors.

 

[markus.wenzel]

I am using correct and resolvable hostname in FQDN format but are getting the same problem using the Apache Proxy for getting access to the Plesk Panel via standard SSL port 443.

Plesk Panel: https://plesk.mydomain.com:8443

Apache vhost: https://plesk.mydomain.com with vhost_ssl.conf

SSLProxyEngine On
ProxyPass / https://plesk.mydomain.com:8443/
ProxyPassReverse / https://plesk.mydomain.com:8443/

With Plesk Panel 9.x everything was okay. Most of the panel pages with 10.x are working also. But the links described by brainforge do not work on my site too.

Any suggestions for solving this issue?

 

[WillemK]

I would love a solution for this too!

 

[GravuTrad]

I have exactly the same problem (with the same domain name). No solution?

 

[MerlijnH]

I am facing this same issue, and it seems to be something weird in Apache (although the URLs Plesk uses are a little dirty as well).

If you access Plesk directly on port 8443 you get the following request:

/smb/redirect/pleskin/root/%2Fplesk%2Fclient%407%2Fdomain%406%2Fcertificate%40/root/%2Fplesk%2Fclient%407%2Fdomain%406%2Fmpc-certificates%2F/?dst=%2Fplesk%2Fclient%407%2Fdomain%406%2Fcertificate%40&src=%2Fsmb%2Fweb%2Fview%2Ftype%2Fssl-certificates&srcController=WebController

This has partial URI encoding, which is not mapped correctly through Apache mod_proxy. The most useful config for Apache is to also set AllowEncodedSlashes NoDecode / AcceptPathInfo Default - which results in the following URL being called:

/smb/redirect/pleskin/root/%252Fplesk%252Fclient@7%252Fdomain@6%252Fcertificate@/root/%252Fplesk%252Fclient@7%252Fdomain@6%252Fmpc-certificates%252F/?dst=%2Fplesk%2Fclient%407%2Fdomain%406%2Fcertificate%40&src=%2Fsmb%2Fweb%2Fview%2Ftype%2Fssl-certificates&srcController=WebController

The most problematic part appears to be that the % signs are expanded to %25 and I am currently completely stuck on how to resolve this. I've tried adding rewrite rules both on the end of Apache and on the end of the Plesk server running lighttpd - but neither way I appear to be able to get this to work.