SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-29 01:02:50 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

ERROR Update LXC TPLINK OMADA Software Controller to Controller 5.15.6.7 Build 20241128140044 #219

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

Originally created by @bahaman1971 on GitHub (Dec 20, 2024).

✅ Have you read and understood the above guidelines?

yes

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

"update" in the lxc console

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

latest_url=$(curl -fsSL "https://www.tp-link.com/en/support/download/omada-software-controller/" | grep -o 'https://.*x64.deb' | head -n1)

📝 Provide a clear and concise description of the issue.

There is a new version of the Omada software controller available on the website and is also displayed in the software controller itself.
2024-12-20 17_59_47-OmadaControllerProxLXC
You normally start the update of the LXC in the corresponding console with the command "update"
2024-12-20 17_58_34-ProxFutroS740 - Proxmox Virtual Environment
. Now the script aborts with the corresponding error message.
2024-12-20 17_59_09-ProxFutroS740 - Proxmox Virtual Environment

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

log into the console

run "update" , the script stops with the error and the virtual omada softwarecontroler in the lxc isn´t updated

❌ Paste the full error output (if available).

[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)
2024-12-20 17_59_09-ProxFutroS740 - Proxmox Virtual Environment

🖼️ Additional context (optional).

No response

Originally created by @bahaman1971 on GitHub (Dec 20, 2024). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? "`update`" in the lxc console ### 📂 What was the exact command used to execute the script? `latest_url=$(curl -fsSL "https://www.tp-link.com/en/support/download/omada-software-controller/" | grep -o 'https://.*x64.deb' | head -n1)` ### 📝 Provide a clear and concise description of the issue. There is a new version of the Omada software controller available on the website and is also displayed in the software controller itself. ![2024-12-20 17_59_47-OmadaControllerProxLXC](https://github.com/user-attachments/assets/22e80e9f-636f-45e7-af0f-16f94e5eed2f) You normally start the update of the LXC in the corresponding console with the command "`update`" ![2024-12-20 17_58_34-ProxFutroS740 - Proxmox Virtual Environment](https://github.com/user-attachments/assets/b585d602-747b-40c6-b56b-97830754e192) . Now the script aborts with the corresponding error message. ![2024-12-20 17_59_09-ProxFutroS740 - Proxmox Virtual Environment](https://github.com/user-attachments/assets/a3ec766e-fe1c-4b3a-b41f-863b33f1c035) ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. log into the console run "`update`" , the script stops with the error and the virtual omada softwarecontroler in the lxc isn´t updated ### ❌ Paste the full error output (if available). `[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)` ![2024-12-20 17_59_09-ProxFutroS740 - Proxmox Virtual Environment](https://github.com/user-attachments/assets/81bceecd-4dbe-4032-9bc9-64f3150e4f90) ### 🖼️ Additional context (optional). _No response_
saavagebueno added the question label 2025-11-20 04:45:08 -05:00
saavagebueno commented 2025-11-20 04:45:09 -05:00
Author
Owner
Copy Link

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

Fixed since lunch? (6-7h ago) Thats an old call

@MickLesk commented on GitHub (Dec 20, 2024): Fixed since lunch? (6-7h ago) Thats an old call
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

I knew the "old" topic... I rebooted my node and the server, the error still exists and I entered the entry here immediately after the error I found. And it also affected a "different" line of code. And in the end there is no improvement, so I opened a "new" topic. If this is against the rules, I can attach my case to the old one, but it doesn't make any sense because I'm writing in a supposed "cold case" ... and the filelink should be
https://static.tp-link.com/upload/software/2024/202412/20241205/omada_v5.15.6.7_linux_x64_20241128140044.deb
this is the forwarding of https://support.omadanetworks.com/en/product/omada-software-controller/?resourceType=download

@bahaman1971 commented on GitHub (Dec 20, 2024): I knew the "old" topic... I rebooted my node and the server, the error still exists and I entered the entry here immediately after the error I found. And it also affected a "different" line of code. And in the end there is no improvement, so I opened a "new" topic. If this is against the rules, I can attach my case to the old one, but it doesn't make any sense because I'm writing in a supposed "cold case" ... and the filelink should be `https://static.tp-link.com/upload/software/2024/202412/20241205/omada_v5.15.6.7_linux_x64_20241128140044.deb` this is the forwarding of `https://support.omadanetworks.com/en/product/omada-software-controller/?resourceType=download`
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

Install a new LXC and Test again. I cant reproduce

@MickLesk commented on GitHub (Dec 20, 2024): Install a new LXC and Test again. I cant reproduce
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

the lxc was running over 6 month, it was the "old" script from tteckster (R.I.P) maybe thats why you can´t reproduce ... what a trouble shooting

@bahaman1971 commented on GitHub (Dec 20, 2024): the lxc was running over 6 month, it was the "old" script from tteckster (R.I.P) maybe thats why you can´t reproduce ... what a trouble shooting
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

Because you Hit Update. You dont have updated the Update command? ^^ its an issue by u. We have an Update Script on website

@MickLesk commented on GitHub (Dec 20, 2024): Because you Hit Update. You dont have updated the Update command? ^^ its an issue by u. We have an Update Script on website
saavagebueno commented 2025-11-20 04:45:10 -05:00
Author
Owner
Copy Link

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

i don´t wanne fight here any more :-) I don't want to fight here any further but on your "new" script page it still says...
https://community-scripts.github.io/ProxmoxVE/scripts?id=omada
To Update Omada Controller, run the command below (or type update) in the LXC Console. and only update was the instruction for the tteckster script .. I have set up a new lxc and of course it works now. I hope that there is a simpler solution for all users of the "old" tteckster script...

@bahaman1971 commented on GitHub (Dec 20, 2024): i don´t wanne fight here any more :-) I don't want to fight here any further but on your "new" script page it still says... [https://community-scripts.github.io/ProxmoxVE/scripts?id=omada](url) `To Update Omada Controller, run the command below (or type update) in the LXC Console.` and only `update `was the instruction for the tteckster script .. I have set up a new lxc and of course it works now. I hope that there is a simpler solution for all users of the "old" tteckster script...
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

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

https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo

Is the Solution. Your Update Crawl the old tteck Repo, not this Repo. Understand now?

@MickLesk commented on GitHub (Dec 20, 2024): https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo Is the Solution. Your Update Crawl the old tteck Repo, not this Repo. Understand now?
saavagebueno commented 2025-11-20 04:45:11 -05:00
Author
Owner
Copy Link

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

We have do the simplest Solution ever ^^ you only need to understand this and execute it.

https://github.com/community-scripts/ProxmoxVE/discussions/13#discussioncomment-11131675

@MickLesk commented on GitHub (Dec 20, 2024): We have do the simplest Solution ever ^^ you only need to understand this and execute it. https://github.com/community-scripts/ProxmoxVE/discussions/13#discussioncomment-11131675
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 question
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#219
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?