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

Plex LXC Update Script Bug #249

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

Originally created by @Outsmart2383 on GitHub (Dec 28, 2024).

✅ Have you read and understood the above guidelines?

Yes

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

Plex (Update command)

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

update

📝 Provide a clear and concise description of the issue.

Running update in the console of your Plex LXC to update it gives the following error:

⠋ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null

There was a previous issue raised for this, it was closed because the reporter was using the wrong Ubuntu version, however, this continues to be an issue. Previous issue: https://github.com/community-scripts/ProxmoxVE/issues/794

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 22.04

🔄 Steps to reproduce the issue.

Running command update

❌ Paste the full error output (if available).

⠋ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null

🖼️ Additional context (optional).

No response

Originally created by @Outsmart2383 on GitHub (Dec 28, 2024). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Plex (Update command) ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. Running `update` in the console of your Plex LXC to update it gives the following error: ` ⠋ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null` There was a previous issue raised for this, it was closed because the reporter was using the wrong Ubuntu version, however, this continues to be an issue. Previous issue: https://github.com/community-scripts/ProxmoxVE/issues/794 ### ⚙️ What settings are you using? - [ ] Default Settings - [X] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 22.04 ### 🔄 Steps to reproduce the issue. Running command `update` ### ❌ Paste the full error output (if available). ` ⠋ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null` ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

@thebatfink commented on GitHub (Dec 28, 2024):

I also have the tteck Plex LXC, updated with the update script https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh which reported as updating sucessfully (couple hours ago).

Afterwards when performing update in the Plex LXC, same error:

⠏ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null

Ubuntu:

lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy

@thebatfink commented on GitHub (Dec 28, 2024): I also have the tteck Plex LXC, updated with the update script https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-repo.sh which reported as updating sucessfully (couple hours ago). Afterwards when performing update in the Plex LXC, same error: ` ⠏ Updating Plex LXC [ERROR] in line 41: exit code 0: while executing command apt-get update &> /dev/null ` Ubuntu: `lsb_release -a` `Distributor ID: Ubuntu` `Description: Ubuntu 22.04.5 LTS` `Release: 22.04` `Codename: jammy `
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

@lurkus commented on GitHub (Dec 28, 2024):

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.5 LTS
Release:        22.04
Codename:       jammy

Same here. When manually running apt-get update, I get the following output:

apt-get update
Hit:1 https://downloads.plex.tv/repo/deb public InRelease
Get:2 http://ftp.debian.org/debian bookworm InRelease [151 kB]              
Err:2 http://ftp.debian.org/debian bookworm InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481
Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
W: GPG error: http://ftp.debian.org/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481
E: The repository 'http://ftp.debian.org/debian bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
@lurkus commented on GitHub (Dec 28, 2024): ``` lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy ``` Same here. When manually running `apt-get update`, I get the following output: ``` apt-get update Hit:1 https://downloads.plex.tv/repo/deb public InRelease Get:2 http://ftp.debian.org/debian bookworm InRelease [151 kB] Err:2 http://ftp.debian.org/debian bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481 Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Done W: GPG error: http://ftp.debian.org/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481 E: The repository 'http://ftp.debian.org/debian bookworm InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ```
saavagebueno commented 2025-11-20 04:45:40 -05:00
Author
Owner
Copy Link

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

fixed generally with newest Breaking Change

@MickLesk commented on GitHub (Dec 28, 2024): fixed generally with newest Breaking Change
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

@thebatfink commented on GitHub (Dec 28, 2024):

fixed generally with newest Breaking Change

What does this mean?

@thebatfink commented on GitHub (Dec 28, 2024): > fixed generally with newest Breaking Change What does this mean?
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

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

remove the wrong source in your list (http://ftp.debian.org/debian bookworm InRelease) and then enter update again

@MickLesk commented on GitHub (Dec 28, 2024): remove the wrong source in your list (http://ftp.debian.org/debian bookworm InRelease) and then enter update again
saavagebueno commented 2025-11-20 04:45:41 -05:00
Author
Owner
Copy Link

@thebatfink commented on GitHub (Dec 28, 2024):

Seems OK. For anyone unsure:

sudo nano /etc/apt/sources.list delete the debian line, save file. Now update again.

@thebatfink commented on GitHub (Dec 28, 2024): Seems OK. For anyone unsure: `sudo nano /etc/apt/sources.list` delete the debian line, save file. Now update again.
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#249
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?