Search results

This is also not correct in my case, there are only small errors and still the backup is marked as invalid, as you can see here are only a few small errors and pictures that could not be found at the time because they may have been deleted in the forum by a Cronjob (Full-Backup from 22th): Even...

- The full backup from before has only 2 errors from 2! Image-files (forum) where the backup was made and never so much that 20GB had to be backed up again. - That's the problem where I created in the other thread, since the function was disabled that the domain can be disabled before the backup...

Hello, But it is (see screenshot), this phenomenon has also only occurred since the last major update, otherwise it was always so between 100-150 MB with incremental. Clearly no major changes or files have been changed or added to the web hosting. I even opened the backup archive of today...

Hello, Since the update yesterday to plesk 18.0.23 I noticed something: Some of my incremental backups are significantly larger, otherwise always around 100MB now 21GB? How can that be, is that normal, does anyone have that, or has there been a bug in plesk again? It is definitely not normal...

@IgorG are there any news about this? I see a lot of people having problems with backup-feature :) Thanks.

Hello, I have problems understanding the composer system (because never used it). Let's say I want to install the following package: vlucas/valitron All I have to do here is this: Put the composer.json from github in httpdocs? Scan via the Plesk-GUI and install or update? Then in most cases...

Try with another browser an or delete cache/cookies before :)

Hi, I can login without problem BUT it is not very smart to post your login data here in the public... Some "bad"-guys can install some maleware on your machine. So I suggest you to reinstall the hole machine even if your problem is solved!!!

Yes, I know that. But I mean rather a bug tracker which is confirmed but not fixed yet :) Thanks.

Thank you, other question where can I look into confirmed bugs like the PPPM-xxxx? Is there anywhere a public bug-tracker? Thank you.

Maybe @IgorG need to report that "bug" :)

Hello @IgorG , That's a good thing, even if the mentioned feature doesn't come back, maybe Plesk will find another way to escape these problems and similars differently. Thank you very much for your commitment :)

Hello, Now I also got this error message during an incremental backup, something has to be refined by Plesk, of course log files are not so important but something has to be refined and optimized here: @Igor

Thank you, i will set this later :) EDIT: Has been done, all good.

Hello, In the changelog of the last update (Plesk Obsidian 18.0.21) I read the following: So this means that if I've upgraded from Plesk Onyx I need to do the above command in SSH? In addition, I think the command is missing in the changelog all behind a " or? Need to restart something after...

@seqoi You don't understand why it's possible and you are confusing things here, so please don't have this conversation and you're missing the point. Of course your opinion has a few right points, but unfortunately also a few wrong views. Of course I don't want to forbid you to talk, but...

You bring it on the point :D PLEASE PLESK-TEAM BRING BACK THE OPTION OR KEEP A EYE ON IT TO IMPROVE THAT :)

Every Plesk user must have the possibility to enable/disable this according to his wishes. In my case this would be more than important that I could count on my backups for my very large forum, even if there might be a small downtime for this domain. There would be a much longer downtime if...

I can't say often enough, that's why the function is so important that the website is deactivated BEFORE the backup is run and only deactivated again when the backup is FINISHED, so this problems don't exists :) Plesk should think about this a little bit because with plesk obsidian this should...

But what if e.g. the entry in the database (e.g. in a forum) is still present but not in the filesystem? If you play in a backup again it could come here in the forum to error messages, because database and file system are not on the same level. That's why I think it makes sense to...