Staubgeborener / Klipper-Backup

Klipper-Backup is a script for manual or automated Klipper GitHub backups. It's Lightweight, pragmatic and comfortable.
https://klipperbackup.xyz
295 stars 57 forks source link

"corrupt" error #15

Closed fushiV closed 1 year ago

fushiV commented 1 year ago

I cant seem to figure out whats causing this "corrupt" error, when I click hard recovery it shows a user name error but my user name is correct in the .env and my files back up just fine. I have tried reinstalling everything from scratch but no change. I also get this other warning while using the backup script from ssh, not sure its related. I also can't figure out why my two of my .cfg don't show up in GitHub with the actual contents but instead just show the file path also pictured below.

Screenshot 2023-10-05 at 08 02 47 Screenshot 2023-10-05 at 07 46 29 Screenshot 2023-10-05 at 07 44 57 Screenshot 2023-10-05 at 07 45 09 Screenshot 2023-10-05 at 07 45 46
Staubgeborener commented 1 year ago

I cant seem to figure out whats causing this "corrupt" error, when I click hard recovery it shows a user name error but my user name is correct in the .env and my files back up just fine. I have tried reinstalling everything from scratch but no change. I also get this other warning while using the backup script from ssh, not sure its related.

This is related to this issue.

TLTR: You cloned this repository from "my" page, after adjusting the git init file (so you can use this project in your own repository), moonraker is quite confused how to handle this. How to fix this: Create a brand new directory for the user, where the backup files and also this script will be packed in to get rid of this problem.

But i need a few testers for this, because i hardly find time for this project alone: I have specially created a dev branch. You can find in the link above all further information.

I also can't figure out why my two of my .cfg don't show up in GitHub with the actual contents but instead just show the file path also pictured below.

Indeed, this is odd. Which version of klipper-backup do you use and could please provide you .env file (with hidden tokens)?

fushiV commented 1 year ago

Thank you for the quick reply. Please see the below picture and text of my .env I have tried to keep it simple and just back up the entire printer_data on this install, but previously I had it set to back up each individual cfg file and it had the same problem for the mainsail.cfg (i did not think to look at the timelapse.cfg during the first install).

.env:

github_token=github_pat_xxxxxxxxxxxxxxxxxx github_username=fushiv github_repository=V2-1-backup

back up whole folder syntax:

path_klipperdata=/home/pi/printer_data/

backup_folder=V2-1_klipper_backup


Screenshot 2023-10-05 at 11 33 07
Staubgeborener commented 1 year ago

Which version of klipper-backup do you use? cat version

After that, please re-run script.sh and post a link to your repository at GitHub.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale.