NetProducts
New Pleskian
Hello,
Automatic plesk updates fail for the panel it self.
Debian-based packages install fine, so the update service is functioning correctly.
Problem: plesk downloads a binary or archive file from a HTTP-based domain, not via SSL like the apt/dpkg tools do.
Likely cause: Our enterprise firewall does not like this. Probably because of the mitm vulnerability possibilities regarding sending executable files over unsecured connections and then automatically starting them as a privileged user.
The line in the relevant log file reads:
E: Failed to fetch http://autoinstall.plesk.com/debian/PSA_17.5.3/../../PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base/psa-updates_17.5.3-debian8.0.build1705170810.18_all.deb Connection failed
Interestingly, Index of /PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base exists and contains the file it wants. Manually downloading it and running it would resolve the current problem, but the real question is:
Can we, and if so, how do we reconfigure Plesk Onyx for Linux so it uses the https:// version of the domain?
Note: I've used the linux 'find' utility to try to find where this path is stored, but complicated XML files and executables turn up.
Automatic plesk updates fail for the panel it self.
Debian-based packages install fine, so the update service is functioning correctly.
Problem: plesk downloads a binary or archive file from a HTTP-based domain, not via SSL like the apt/dpkg tools do.
Likely cause: Our enterprise firewall does not like this. Probably because of the mitm vulnerability possibilities regarding sending executable files over unsecured connections and then automatically starting them as a privileged user.
The line in the relevant log file reads:
E: Failed to fetch http://autoinstall.plesk.com/debian/PSA_17.5.3/../../PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base/psa-updates_17.5.3-debian8.0.build1705170810.18_all.deb Connection failed
Interestingly, Index of /PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base exists and contains the file it wants. Manually downloading it and running it would resolve the current problem, but the real question is:
Can we, and if so, how do we reconfigure Plesk Onyx for Linux so it uses the https:// version of the domain?
Note: I've used the linux 'find' utility to try to find where this path is stored, but complicated XML files and executables turn up.