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

it's not backing up #131

Closed
1 task done
drumstick77 opened this issue Sep 25, 2024 · 12 comments
Closed
1 task done

it's not backing up #131

drumstick77 opened this issue Sep 25, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@drumstick77
Copy link

Code of Conduct

  • I promise that i have used markdown syntax to make the code more readable which helps to fix the problem and that I have tested the --fix command mentioned above without success.

What happened

I've reinstalled and followed install.sh, entered my details but it's not backing up. it's now doing it on both printers.

What did you expect to happen

I expected it to backup to my github

How to reproduce

I've re-installed but it is still not uploading files to my repositories

Debug

Unable to create/upload debug

Additional information

image

@drumstick77 drumstick77 added the bug Something isn't working label Sep 25, 2024
@Staubgeborener
Copy link
Owner

Unable to create/upload debug

Why?

I think you are using your github password in your .env file instead a token. The error message tells you basically this.

Password-based authentication for Git has been removed in favor of more secure authentication methods. For more information, see "[Managing your personal access tokens]:

@drumstick77
Copy link
Author

okay, so how would one resolve this issue?

@Staubgeborener
Copy link
Owner

You create a token like it is explained here and use it instead your github password in your .env. You could simple run the install.sh and add the token if the installer ask for it.

@drumstick77
Copy link
Author

ok, yes that's exactly how I did it
I created the token in github and pasted it during the wizard of running install.sh

@drumstick77
Copy link
Author

I never had to edit or tweak .env

@drumstick77
Copy link
Author

drumstick77 commented Sep 25, 2024

should I be generating tokens (classic)? or fine-grained tokens? because your instruction says doesn't matter which one. and I'm using fine-grained tokens

@drumstick77
Copy link
Author

should I remove the current .env and start again?

@Staubgeborener
Copy link
Owner

You can just edit your post instead of re-posting.

should I be generating tokens (classic)? or fine-grained tokens? because your instruction says doesn't matter which one. and I'm using fine-grained tokens

Indeed, it doesn't matter but just create a Fine-grained token with these settings (i will update the docs with this information):

Only select repositories -> select your backup repository

Account permissions:
-------------------------------
Administration: Read and write
Commit statuses: Read and write 

should I remove the current .env and start again?
This is not necessary. Create the token like i explained, run the install.sh again (like ~/klipper-backup/install.sh) and add the token when the script ask for it.

If this still doesn't work, please give me the whole script.sh --debug output.

@drumstick77
Copy link
Author

ok, I've managed to fix this. I went with the classic token which gives the ability to set permission like per modbot video. the fine grain is slightly different. Although, if I remember rightly Minimal 3DP went with fine grain and he clicked on generate token without setting any permissions. Anyway, I will go with this classic token and will also apply to my other printers. thanks for you help.

@drumstick77
Copy link
Author

drumstick77 commented Sep 25, 2024

just did it do another printer and was getting this error
image

@Staubgeborener
Copy link
Owner

Try script.sh --fix and run again.

@drumstick77
Copy link
Author

Good man! awesome. thank you. all sorted now. Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants