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

Omada update error #261

New Issue
Closed
opened 2025-11-20 04:45:50 -05:00 by saavagebueno · 14 comments
saavagebueno commented 2025-11-20 04:45:50 -05:00
Owner
Copy Link

Originally created by @psychedelicu on GitHub (Dec 30, 2024).

✅ Have you read and understood the above guidelines?

yes

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

Omada Controller LXC

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

update

📝 Provide a clear and concise description of the issue.

When i try to update the controller with the "update" function, it gives me this error:

[ERROR] in line 58: exit code 0: while executing command latest_url=$(curl -fsSL "https://www.tp-link.com/en/support/download/omada-software-controller/" | grep -o 'https://.*x64.deb' | head -n1)

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

image

❌ Paste the full error output (if available).

image

🖼️ Additional context (optional).

No response

Originally created by @psychedelicu on GitHub (Dec 30, 2024). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Omada Controller LXC ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. When i try to update the controller with the "update" function, it gives me this error: [ERROR] in line 58: exit code 0: while executing command latest_url=$(curl -fsSL "https://www.tp-link.com/en/support/download/omada-software-controller/" | grep -o 'https://.*x64.deb' | head -n1) ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. ![image](https://github.com/user-attachments/assets/faaf5ab7-9675-41fa-a4bd-3d7fc12589c8) ### ❌ Paste the full error output (if available). ![image](https://github.com/user-attachments/assets/f83a959a-d481-473b-8358-6a58786c050c) ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:45:51 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 30, 2024):

I used this script in LXC, but it comes with another error.
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)"

Updating Omada Controller
(Reading database ... 29202 files and directories currently installed.)
Preparing to unpack Omada_SDN_Controller_v5.14.26.1_linux_x64.deb ...
A previous controller version has been detected.
Unpacking omadac (5.14.26.1) over (5.14.26.1) ...
Setting up omadac (5.14.26.1) ...
Install Omada Controller succeeded!

data dir is not empty.
current data is not empty
Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap].
check omada
Starting Omada Controller. Please wait..............................................^Cdpkg: error processing package omadac (--install):
installed omadac package post-installation script subprocess was interrupted
Errors were encountered while processing:
omadac

[ERROR] in line 45: exit code 0: while executing command dpkg -i ${latest_version}

root@omada:~#

@psychedelicu commented on GitHub (Dec 30, 2024): I used this script in LXC, but it comes with another error. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)" Updating Omada Controller (Reading database ... 29202 files and directories currently installed.) Preparing to unpack Omada_SDN_Controller_v5.14.26.1_linux_x64.deb ... A previous controller version has been detected. Unpacking omadac (5.14.26.1) over (5.14.26.1) ... Setting up omadac (5.14.26.1) ... Install Omada Controller succeeded! ========================== data dir is not empty. current data is not empty Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap]. check omada Starting Omada Controller. Please wait..............................................^Cdpkg: error processing package omadac (--install): installed omadac package post-installation script subprocess was interrupted Errors were encountered while processing: omadac [ERROR] in line 45: exit code 0: while executing command dpkg -i ${latest_version} root@omada:~#
saavagebueno commented 2025-11-20 04:45:51 -05:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Dec 30, 2024):

That error message in the original screenshot looks like the repo is pointing at the old Tteck script.

You need to run this in your Proxmox shell to re-point it to the community scripts:
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)"

@oOStroudyOo commented on GitHub (Dec 30, 2024): That error message in the original screenshot looks like the repo is pointing at the old Tteck script. You need to run this in your Proxmox shell to re-point it to the community scripts: `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)"`
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@bahaman1971 commented on GitHub (Dec 30, 2024):

I think it's the same thing I "fought" with, so it´s an "solved" issue
https://github.com/community-scripts/ProxmoxVE/issues/944
@MickLesk

@bahaman1971 commented on GitHub (Dec 30, 2024): I think it's the same thing I "fought" with, so it´s an "solved" issue https://github.com/community-scripts/ProxmoxVE/issues/944 @MickLesk
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 30, 2024):

Sorry, but i have tried that already. Not working.
After update, Omada starts then it crash.

  1. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)"
  2. sed -i 's/tteck/Proxmox/community-scripts/ProxmoxVE/g' /usr/bin/update

image
image

image

@psychedelicu commented on GitHub (Dec 30, 2024): Sorry, but i have tried that already. Not working. After update, Omada starts then it crash. 1. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh)" 2. sed -i 's/tteck\/Proxmox/community-scripts\/ProxmoxVE/g' /usr/bin/update ![image](https://github.com/user-attachments/assets/92556e52-a7f6-40f4-a1ea-20e642499abb) ![image](https://github.com/user-attachments/assets/ab3738a2-9de3-4930-b0f3-4bde31808825) ![image](https://github.com/user-attachments/assets/fe1e209c-329b-42f4-833d-d4f257b9ac34)
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 30, 2024):

Why you kill the Update with Ctrl c?

@MickLesk commented on GitHub (Dec 30, 2024): Why you kill the Update with Ctrl c?
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 30, 2024):

Because it doesnt do anything for hours. And also, instead of upgrading, omada is downgrading.

In omada i can see the 5.15.6.7 is the latest.
And currently, downgrading from 5.14.32.3 to 5.14.26.1.

The script is not working.

@psychedelicu commented on GitHub (Dec 30, 2024): Because it doesnt do anything for hours. And also, instead of upgrading, omada is downgrading. In omada i can see the 5.15.6.7 is the latest. And currently, downgrading from 5.14.32.3 to 5.14.26.1. The script is not working.
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@tismofied commented on GitHub (Dec 30, 2024):

Because it doesnt do anything for hours. And also, instead of upgrading, omada is downgrading.

In omada i can see the 5.15.6.7 is the latest. And currently, downgrading from 5.14.32.3 to 5.14.26.1.

The script is not working.

I am seeing the exact same thing in my instance as well. I used ttecks script and I was on the latest version before he passed. I have no idea how I got version 5.14.32.2. because the latest version on tplink download site is v5.14.26.1
I even tried using a new lXC and use the community script but when I reached the step of restoring the settings, omada complained the the version of the backup is higher than that of the software from the community script. (which is 5.14.26.1)

image
I made sure to update the repos to point the community repos instead of ttecks

@tismofied commented on GitHub (Dec 30, 2024): > Because it doesnt do anything for hours. And also, instead of upgrading, omada is downgrading. > > In omada i can see the 5.15.6.7 is the latest. And currently, downgrading from 5.14.32.3 to 5.14.26.1. > > The script is not working. I am seeing the exact same thing in my instance as well. I used ttecks script and I was on the latest version before he passed. I have no idea how I got version 5.14.32.2. because the latest version on [tplink download site](https://support.omadanetworks.com/us/product/omada-software-controller/?resourceType=download) is v5.14.26.1 I even tried using a new lXC and use the community script but when I reached the step of restoring the settings, omada complained the the version of the backup is higher than that of the software from the community script. (which is 5.14.26.1) ![image](https://github.com/user-attachments/assets/2ee1b84b-499c-43af-b4cc-fd0f127a6967) I made sure to update the repos to point the community repos instead of ttecks
saavagebueno commented 2025-11-20 04:45:52 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 30, 2024):

I managed to update it via:

cd /tmp
wget https://download.tplinkcloud.com/firmware/omada_v5.15.6.7_linux_x64_20241128140044_1733188152890.deb
dpkg -i omada_v5.15.6.7_linux_x64_20241128140044_1733188152890.deb

The UI is different now.,

image

@psychedelicu commented on GitHub (Dec 30, 2024): I managed to update it via: cd /tmp wget https://download.tplinkcloud.com/firmware/omada_v5.15.6.7_linux_x64_20241128140044_1733188152890.deb dpkg -i omada_v5.15.6.7_linux_x64_20241128140044_1733188152890.deb The UI is different now., ![image](https://github.com/user-attachments/assets/889708e0-1491-4a49-8951-452c6a682278)
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@tismofied commented on GitHub (Dec 30, 2024):

Thank you so much for including your steps for upgrade. You saved me a day's worth of headache lol.
Yeah They updated their UI few days ago I noticed the same in the app as well.

so for the script, do I just wait until it gets updated to 5.15.6.x before using it again?

@tismofied commented on GitHub (Dec 30, 2024): Thank you so much for including your steps for upgrade. You saved me a day's worth of headache lol. Yeah They updated their UI few days ago I noticed the same in the app as well. so for the script, do I just wait until it gets updated to 5.15.6.x before using it again?
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 30, 2024):

Thank you so much for including your steps for upgrade. You saved me a day's worth of headache lol. Yeah They updated their UI few days ago I noticed the same in the app as well.

so for the script, do I just wait until it gets updated to 5.15.6.x before using it again?

I have no idea about the script. For me, is not working.

@psychedelicu commented on GitHub (Dec 30, 2024): > Thank you so much for including your steps for upgrade. You saved me a day's worth of headache lol. Yeah They updated their UI few days ago I noticed the same in the app as well. > > so for the script, do I just wait until it gets updated to 5.15.6.x before using it again? I have no idea about the script. For me, is not working.
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@deku-m commented on GitHub (Dec 30, 2024):

Same for me after using update this will downgrade and wont start anymore.

@deku-m commented on GitHub (Dec 30, 2024): Same for me after using update this will downgrade and wont start anymore.
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@bahaman1971 commented on GitHub (Dec 30, 2024):

The actual Script has a Version "Error" , See https://github.com/community-scripts/ProxmoxVE/discussions/1113

@bahaman1971 commented on GitHub (Dec 30, 2024): The actual Script has a Version "Error" , See https://github.com/community-scripts/ProxmoxVE/discussions/1113
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 30, 2024):

To be honest, I'm thinking about removing omada completely. They change their deb package names every time. Just like the repolinks. This is not only exhausting but also shitty for everyone

@MickLesk commented on GitHub (Dec 30, 2024): To be honest, I'm thinking about removing omada completely. They change their deb package names every time. Just like the repolinks. This is not only exhausting but also shitty for everyone
saavagebueno commented 2025-11-20 04:45:53 -05:00
Author
Owner
Copy Link

@psychedelicu commented on GitHub (Dec 31, 2024):

Me too. Also, too many bugs and crashes. I'll try OPNsense soon.

@psychedelicu commented on GitHub (Dec 31, 2024): Me too. Also, too many bugs and crashes. I'll try OPNsense soon.
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#261
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?