Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In latest release 5.0.10 sync with encryption does not work #139

Closed
csaggo opened this issue May 1, 2018 · 3 comments
Closed

In latest release 5.0.10 sync with encryption does not work #139

csaggo opened this issue May 1, 2018 · 3 comments
Assignees
Labels

Comments

@csaggo
Copy link

@csaggo csaggo commented May 1, 2018

I updated the .phar to the current 5.0.10 release and did not change anything in my config.json.
But now i get the following error:
Exception 'phpbu\App\Backup\Sync\Exception' with message 'target file 'mysql-20180501-0200.sql.bz2' doesn't exist' in phar:///etc/nginx/conf.d/PHPBU/phpbu.phar/Backup/Sync/AmazonS3v3.php:49

I use the crypt option with openssl, so the filename it looks to upload to s3 should actually be mysql-20180501-0200.sql.bz2.enc

The Files are generated correctly and exist.

@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented May 1, 2018

I'll look into this asap

Loading

sebastianfeldmann added a commit that referenced this issue May 1, 2018
While changing the runner concept to 'Backup', 'Simulate'
and 'Restore' runners adding the 'Crypter' to the target for
correct suffix resolution was falsely removed.
@sebastianfeldmann
Copy link
Owner

@sebastianfeldmann sebastianfeldmann commented May 1, 2018

You are absolutely right. I messed it up during some --restore preparations.

Update to version 5.0.11 and it should be fixed.

Loading

@csaggo
Copy link
Author

@csaggo csaggo commented May 1, 2018

Thanks so much for the quick reaction!

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants