-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
FPP Backup is not working #2118
Comments
Hi @atticusm , Can you try to load http://primarycontroller-ip/api/backups/configuration/list in your browser? I'm expecting a error or something but just want try confirm where it's falling over |
Thank you for responding. Here is what I get:
[image: image.png]
…On Mon, Jan 20, 2025 at 7:22 AM Jared ***@***.***> wrote:
Hi @atticusm <https://github.com/atticusm> ,
Can you try to load http:///api/backups/configuration/list in your
browser?
Do you get a error returned once the page loads or is it just blank? Also
it seem blank but on the page it may just have square brackets like []
—
Reply to this email directly, view it on GitHub
<#2118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLX2MQYI23K4WHO24ZSB7L2LT2B3AVCNFSM6AAAAABVBHYBI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBSGQYTMOJSHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Unfortunately the image didn't come through, can you try again?, if there is error text would able to copy/paste it here might be easier? |
FPP Version and Hardware: FPP v8.4.2 (v8.4 branch) on two different controllers. 2 K32's and 1 PI
Describe the bug and Steps to reproduce:
Expected behavior:
Json downloads
Additional context:
Only 1 of my controllers allows me to download the backups. Under FPP Download there are no existing backups displayed. Clicking on 'Download Configuration' will either load a blank page or throw error. Manually POSTing the backup API results in error.
PrimaryKulpController.zip
![image](https://github.com/user-attachments/assets/029b7c87-7
PiControllerLogs.zip
f90-4082-9aa9-d407507a91ea)
The text was updated successfully, but these errors were encountered: