• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

AWOL FTP Backup Repository

matthew@

New Pleskian
Just migrated my Plesk 7.5/FreeBSD 5.3 to a Plesk 8.3/FreeBSD 6.2 environment. Couple of minor things that aren't quite right...

* When I do an FTP backup (for a client, in this case), it seems to work fine, but in the FTP Repository tab, under 'Existing backup files', it says 'No existing backup files' - is it supposed to show me all the files in my FTP site? It does seem to be working so it's not a disaster, but it would be nice to see them.

* The migration broke all my permissions, all httpdocs folders and files inside them were set to 750 :( Fixed now, but I have some more domains to migrate, any idea why?

* I'm having trouble with Watchdog reporting that Apache is down, but it's running just fine (I've restarted Apache and rebooted the server). But from other threads here, I guess I'm not alone so maybe I should just live without it for now...

MTIA, Matthew
 
I said:

* I'm having trouble with Watchdog reporting that Apache is down, but it's running just fine (I've restarted Apache and rebooted the server). But from other threads here, I guess I'm not alone so maybe I should just live without it for now...

Well, one down - looking at the watchdog config files, I figured out that there was a PHP error in one of my sites, that broke it when accessing it via IP rather than by domain name.

It seems that watchdog is not just checking that the Apache process exists, but checking that the the primary IP address returns a valid response - ie that the default domain for that IP address is working OK.

My FTP backup problem still persists though... any ideas appreciated.
 
Back
Top