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 Controller MongoDB Update fails #1385

New Issue
Open
opened 2025-11-20 05:09:18 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:09:18 -05:00
Owner
Copy Link

Originally created by @Raltahook on GitHub (Jun 29, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Omada Controller

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Hello, I tried to update the Omada Controller from 5.15.20.20 to the newest version (5.15.24.17) via the "update" command in the LXC. The script throws an error right away while updating MongoDB.

🔄 Steps to reproduce the issue.

Step 1: Start update with "update" command"
Step 2: Choose Update (with verbose)

❌ Paste the full error output (if available).

⏳ Updating MongoDBcurl: (7) Failed to connect to pgp.mongodb.com port 443 after 17 ms: Couldn't connect to server
gpg: no valid OpenPGP data found.

[ERROR] in line 39: exit code 0: while executing command gpg --dearmor > /usr/share/keyrings/mongodb-server-${MONGODB_VERSION}.gpg

🖼️ Additional context (optional).

It is an old installation still from the TTeck era if that matters. I was able to update it some time ago with the new repository from the community scripts.

Originally created by @Raltahook on GitHub (Jun 29, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Omada Controller ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hello, I tried to update the Omada Controller from 5.15.20.20 to the newest version (5.15.24.17) via the "update" command in the LXC. The script throws an error right away while updating MongoDB. ### 🔄 Steps to reproduce the issue. Step 1: Start update with "update" command" Step 2: Choose Update (with verbose) ### ❌ Paste the full error output (if available). ⏳ Updating MongoDBcurl: (7) Failed to connect to pgp.mongodb.com port 443 after 17 ms: Couldn't connect to server gpg: no valid OpenPGP data found. [ERROR] in line 39: exit code 0: while executing command gpg --dearmor > /usr/share/keyrings/mongodb-server-${MONGODB_VERSION}.gpg ### 🖼️ Additional context (optional). It is an old installation still from the TTeck era if that matters. I was able to update it some time ago with the new repository from the community scripts.
saavagebueno added the bug label 2025-11-20 05:09:18 -05:00
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 bug
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#1385
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?