• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. KirkM

    Issue 18.0.30 update broke FTPS backups

    Annnnnd... it is now failing again after less than 24 hours.
  2. KirkM

    Issue 18.0.30 update broke FTPS backups

    So I noticed that there is Update 1 now for 18.0.30. I first tested FTPS and it failed again. I immediately installed the panel update and ran the exact same backup again and it works. Looks like either the update repaired whatever might have gone wrong with the previous 18.0.30 update on my...
  3. KirkM

    Issue 18.0.30 update broke FTPS backups

    It supports TLS 1.2 and 1.3. It does NOT support TLS 1.1. As I said, it worked just fine using FTPS for months and broke the day of the 18.0.30 update so unless that update changed to only use TLS 1.1 (which I find unlikely), the TLS version isn't the problem on the remote backup server. I...
  4. KirkM

    Issue 18.0.30 update broke FTPS backups

    New test: - Create local backup to psa dumps - download to local computer - upload to IONOS HiDrive - change naming to fit format for remote FTP backups - restore from remote ftp This works. [UPDATE] Backing up to remote ftp without FTPS and passive mode on works perfectly. 18.0.30 has broken...
  5. KirkM

    Issue 18.0.30 update broke FTPS backups

    It is definitely an FTPS issue regarding the archive metadata. - Backup to server PSA dumps is fine and restores correctly - Backup to FTPS on IONOS HiDrive shows error after backup and file that is written is slightly larger than a valid dumps backup: And attempts to restore the remote file...
  6. KirkM

    Issue 18.0.30 update broke FTPS backups

    Well that didn't work either...
  7. KirkM

    Issue 18.0.30 update broke FTPS backups

    No, I never have that checked. All backups are full backups. The error occurs with both manual and scheduled backups - always full backups with no multivolume. I am going to try completely wiping the scheduled backups and the remote FTP server settings to see if something there went bad...
  8. KirkM

    Issue 18.0.30 update broke FTPS backups

    Thank you for your reply Peter. I had read on other threads about this and did check the psa.BackupsScheduled table and there is only one of each scheduled backup listed. I did observe the full server backup the other day writing the backup and then starting a second one before the first one...
  9. KirkM

    Issue 18.0.30 update broke FTPS backups

    Remote FTP backups have been working perfectly until the panel updated to 18.0.30. All backups, domain and full server are throwing error messages: FULL SERVER: DOMAINS: I have only a couple hundred MB used on a 2 TB remote backup drive so it isn't out of space. It doesn't appear to be a...
  10. KirkM

    Resolved Port 25 closed cannot send email

    I have been with 1&1 (now Ionos) for literally decades but always had a dedicated hardware box (since cloud servers didn't exist when I started doing this). I have always created my own custom nameservers and specific DNS templates for some of my specialized applications. I didn't really know...
  11. KirkM

    Resolved Port 25 closed cannot send email

    I probably should have said "custom nameservers" to be more clear. No, it is not "non-Plesk nameservers, I use Plesk to handle all of my DNS and nameserver setup. It is non-IONOS nameservers and DNS management
  12. KirkM

    Resolved Plesk Mobile Center app crashes after update 1.10.0

    Follow Anthony's instructions above and it should fix the issue.
  13. KirkM

    Resolved Port 25 closed cannot send email

    I can confirm this with Ionos dedicated cloud servers. If you are using your own nameservers and sending mail through your Plesk server hostname, you MUST call and have them unblock port 25 OUTGOING. The Ionos cloud server panel firewall gives you control ONLY over incoming ports, not...
  14. KirkM

    Resolved Plesk Mobile Center app crashes after update 1.10.0

    Fantastic! I didn't even get the message in the app to update after doing the manual update in the Plesk panel. The app worked perfectly right when I opened it. Thanks so much for you prompt attention and efficient response to this issue. Much appreciated.
  15. KirkM

    Resolved Plesk Mobile Center app crashes after update 1.10.0

    Yes: -rw------- 1 psaadm psaadm 53248 May 31 12:47 /usr/local/psa/var/modules/plesk-mobile/MobileConnector.sqlite Log says only: May 31 12:47:41 (229d2) [WARNING] [User] cli No cache database found, creating an empty one. Thanks for looking into this.
  16. KirkM

    Resolved Plesk Mobile Center app crashes after update 1.10.0

    I have the same issue and same errors. This solution did not fix it. [2019-05-31 12:46:02.139] ERR [panel] Class 'Modules_PleskMobile_App_Database_Exception' not found: 0: /usr/local/psa/admin/plib/modules/plesk-mobile/library/App/Database.php:61 Modules_PleskMobile_App_Database->init() 1...
  17. KirkM

    Resolved Broke server name / IP relationship

    Nevermind. I used the long form way of restoring the dump. Once I did that and then re-uploaded the certificate, it came back up.
  18. KirkM

    Resolved Broke server name / IP relationship

    Yes, that is the article I read. Here is what it says to restore: The example below shows how to restore 'PSA' database from the dump: # plesk db psa < psa.sql That command obviously doesn't work on a gz file or unzipped for that matter. There is some significant instruction missing here.
  19. KirkM

    Resolved Broke server name / IP relationship

    Thanks Igor. I finally got into the panel with the IP address and it wiped out the CSR and certificate. I hoped that was it so I did a new CSR request and re-issued the cert. No luck. I tried everything else, so I guess I do need to restore the psa database. I haven't done that before and I...
Back
Top