SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

TeddyCloud community script fails updating - overwriting www dir with old files #329

New Issue
Closed
opened 2025-11-20 04:47:02 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 04:47:02 -05:00
Owner
Copy Link

Originally created by @SciLor on GitHub (Jan 9, 2025).

Originally assigned to: @dsiebel on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

teddycloud

📂 What was the exact command used to execute the script?

And how you updated teddyCloud? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/teddycloud.sh)"

📝 Provide a clear and concise description of the issue.

The script first downloads and unzips the new version (a) and then copies over the data dir (b) over the unzipped files. The data dir contains version specific files in the www directory. So the frontend will be overwritten with the previous version.
As alternative I would copy over the previous data dir first and then overwrite it with the data from the zipfile.

a)
19e7751fb9/ct/teddycloud.sh (L41)
b)
19e7751fb9/ct/teddycloud.sh (L46)

I would suggest replicating the volumes of the docker version.
https://github.com/toniebox-reverse-engineering/teddycloud/blob/master/docker/docker-compose.yaml

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

🔄 Steps to reproduce the issue.

Install version 0.6.2 of teddyCloud and then update to 0.6.3 using the script

❌ Paste the full error output (if available).

"Error - the GUI is not in the expected state.
The backend has a different version than the frontend. In a Docker installation, please ensure that no volume has been created under data/www."

🖼️ Additional context (optional).

No response

Originally created by @SciLor on GitHub (Jan 9, 2025). Originally assigned to: @dsiebel on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? teddycloud ### 📂 What was the exact command used to execute the script? And how you updated teddyCloud? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/teddycloud.sh)" ### 📝 Provide a clear and concise description of the issue. The script first downloads and unzips the new version (a) and then copies over the data dir (b) over the unzipped files. The data dir contains version specific files in the www directory. So the frontend will be overwritten with the previous version. As alternative I would copy over the previous data dir first and then overwrite it with the data from the zipfile. a) https://github.com/community-scripts/ProxmoxVE/blob/19e7751fb90f0063826245656958efbce57ac0e3/ct/teddycloud.sh#L41 b) https://github.com/community-scripts/ProxmoxVE/blob/19e7751fb90f0063826245656958efbce57ac0e3/ct/teddycloud.sh#L46 I would suggest replicating the volumes of the docker version. https://github.com/toniebox-reverse-engineering/teddycloud/blob/master/docker/docker-compose.yaml ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 🔄 Steps to reproduce the issue. Install version 0.6.2 of teddyCloud and then update to 0.6.3 using the script ### ❌ Paste the full error output (if available). "Error - the GUI is not in the expected state. The backend has a different version than the frontend. In a Docker installation, please ensure that no volume has been created under data/www." ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:47:02 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 9, 2025):

@dsiebel

@MickLesk commented on GitHub (Jan 9, 2025): @dsiebel
saavagebueno commented 2025-11-20 04:47:02 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 21, 2025):

can anyone test it? Its an blind-fix because i cant use the tool.

@MickLesk commented on GitHub (Jan 21, 2025): can anyone test it? Its an blind-fix because i cant use the tool.
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@fampla commented on GitHub (Jan 23, 2025):

Sorry to bother, but how do I fix the installation? When I try to update, the script says "no new version".
I'm sure this is a stupid question, but I'm stumped

@fampla commented on GitHub (Jan 23, 2025): Sorry to bother, but how do I fix the installation? When I try to update, the script says "no new version". I'm sure this is a stupid question, but I'm stumped
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 23, 2025):

New LXC

@MickLesk commented on GitHub (Jan 23, 2025): New LXC
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@fampla commented on GitHub (Jan 23, 2025):

That was a little bit too easy, thanks.

@fampla commented on GitHub (Jan 23, 2025): That was a little bit too easy, thanks.
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@dsiebel commented on GitHub (Jan 25, 2025):

can anyone test it? Its an blind-fix because i cant use the tool.

Apologies for being late to the party. I haven't had much time to work on it lately.
I don't think #1652 fixed it. It does the same as the previous version minus the symlinks.
It still copies the entire data directory, replacing needed files in the data/www subdir.

@dsiebel commented on GitHub (Jan 25, 2025): > can anyone test it? Its an blind-fix because i cant use the tool. Apologies for being late to the party. I haven't had much time to work on it lately. I don't think #1652 fixed it. It does the same as the previous version minus the symlinks. It still copies the entire data directory, replacing needed files in the `data/www` subdir.
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@skara2024 commented on GitHub (Mar 4, 2025):

New LXC

Just for me as a noob: Can I simply replace the /opt/teddycloud-6.0.3/data/www folder n the old container with files from a clean install? So I could keep the config etc., or is there some further data that needs to be replaced?

@skara2024 commented on GitHub (Mar 4, 2025): > New LXC Just for me as a noob: Can I simply replace the /opt/teddycloud-6.0.3/data/www folder n the old container with files from a clean install? So I could keep the config etc., or is there some further data that needs to be replaced?
saavagebueno commented 2025-11-20 04:47:03 -05:00
Author
Owner
Copy Link

@tech2mar commented on GitHub (Mar 9, 2025):

I wanted to share my experience with the issue regarding the GUI and backend version mismatch on my TeddyCloud server running in a Proxmox LXC container.
After performing an update, I encountered the error:
"The GUI is not in the expected state. The backend has a different version than the frontend."
Notably, there is no persistent mount for data/www in my configuration. Despite following the recommended setup for LXC environments, the version mismatch persists.
I am also waiting for a fix that addresses this issue specifically in LXC setups. If more logs or configuration details are required, I am happy to provide them.
Thank you for your attention to this matter.

@tech2mar commented on GitHub (Mar 9, 2025): I wanted to share my experience with the issue regarding the GUI and backend version mismatch on my TeddyCloud server running in a Proxmox LXC container. After performing an update, I encountered the error: "The GUI is not in the expected state. The backend has a different version than the frontend." Notably, there is no persistent mount for data/www in my configuration. Despite following the recommended setup for LXC environments, the version mismatch persists. I am also waiting for a fix that addresses this issue specifically in LXC setups. If more logs or configuration details are required, I am happy to provide them. Thank you for your attention to this matter.
saavagebueno commented 2025-11-20 04:47:04 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 11, 2025):

check again with #2996

Otherwise create an new issue with more information. Old Issues see nobody of Contributors

@MickLesk commented on GitHub (Mar 11, 2025): check again with #2996 Otherwise create an new issue with more information. Old Issues see nobody of Contributors
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#329
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?