starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Ghost install error #1875

New Issue
Closed
opened 2026-02-05 02:37:27 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 02:37:27 +03:00
Owner
Copy Link

Originally created by @miguelns21 on GitHub (Oct 24, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Ghost

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

Install error:

Processing triggers for man-db (2.11.2-2) ...
✔️ Installed Dependencies
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Get:4 https://repo.mysql.com/apt/debian bookworm InRelease [22.7 kB]
Err:4 https://repo.mysql.com/apt/debian bookworm InRelease
The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering mysql-build@oss.oracle.com
Reading package lists... Done
W: GPG error: https://repo.mysql.com/apt/debian bookworm InRelease: The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering mysql-build@oss.oracle.com
E: The repository 'https://repo.mysql.com/apt/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.

[ERROR] in line 645: exit code 0: while executing command $STD apt update

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

r

🔄 Steps to reproduce the issue.

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

❌ Paste the full error output (if available).

Processing triggers for man-db (2.11.2-2) ...
✔️ Installed Dependencies
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Get:4 https://repo.mysql.com/apt/debian bookworm InRelease [22.7 kB]
Err:4 https://repo.mysql.com/apt/debian bookworm InRelease
The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering mysql-build@oss.oracle.com
Reading package lists... Done
W: GPG error: https://repo.mysql.com/apt/debian bookworm InRelease: The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering mysql-build@oss.oracle.com
E: The repository 'https://repo.mysql.com/apt/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.

[ERROR] in line 645: exit code 0: while executing command $STD apt update

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

r

🖼️ Additional context (optional).

No response

Originally created by @miguelns21 on GitHub (Oct 24, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Ghost ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/ghost.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve) ### 📝 Provide a clear and concise description of the issue. Install error: Processing triggers for man-db (2.11.2-2) ... ✔️ Installed Dependencies Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Get:4 https://repo.mysql.com/apt/debian bookworm InRelease [22.7 kB] Err:4 https://repo.mysql.com/apt/debian bookworm InRelease The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering <mysql-build@oss.oracle.com> Reading package lists... Done W: GPG error: https://repo.mysql.com/apt/debian bookworm InRelease: The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering <mysql-build@oss.oracle.com> E: The repository 'https://repo.mysql.com/apt/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. [ERROR] in line 645: exit code 0: while executing command $STD apt update [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" r ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/ghost.sh)" ### ❌ Paste the full error output (if available). Processing triggers for man-db (2.11.2-2) ... ✔️ Installed Dependencies Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Get:4 https://repo.mysql.com/apt/debian bookworm InRelease [22.7 kB] Err:4 https://repo.mysql.com/apt/debian bookworm InRelease The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering <mysql-build@oss.oracle.com> Reading package lists... Done W: GPG error: https://repo.mysql.com/apt/debian bookworm InRelease: The following signatures were invalid: EXPKEYSIG B7B3B788A8D3785C MySQL Release Engineering <mysql-build@oss.oracle.com> E: The repository 'https://repo.mysql.com/apt/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. [ERROR] in line 645: exit code 0: while executing command $STD apt update [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" r ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:37:27 +03:00
OVERLORD commented 2026-02-05 02:37:38 +03:00
Author
Owner
Copy Link

@amar5150 commented on GitHub (Oct 26, 2025):

Same exact problem here.

@amar5150 commented on GitHub (Oct 26, 2025): Same exact problem here.
OVERLORD commented 2026-02-05 02:37:41 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 26, 2025):

Gpg issue. Does Ghost running fine with mariadb?

@MickLesk commented on GitHub (Oct 26, 2025): Gpg issue. Does Ghost running fine with mariadb?
OVERLORD commented 2026-02-05 02:37:45 +03:00
Author
Owner
Copy Link

@pirona commented on GitHub (Oct 26, 2025):

Hello guys : I figured out something, but I don't have the solution.
I 've met the problem too : but if I just install mariadb-server using apt, avoiding the special repo, I can install it.
EDIT : this implies to delete or rename the mysql repo in /etc/apt/sources.list.d/

mv /etc/apt/sources.list.d/mysql.sources /etc/apt/sources.list.d/mysql.sources.nope

The thing is I can't pass the script setup which eventually goes to a install-mysql.sh which install the repo and so the expired key.

An adjustement may be necessary in this script ?

Or maybe a way to get the installation process back after this step ?

@pirona commented on GitHub (Oct 26, 2025): Hello guys : I figured out something, but I don't have the solution. I 've met the problem too : but if I just install mariadb-server using apt, avoiding the special repo, I can install it. EDIT : this implies to delete or rename the mysql repo in /etc/apt/sources.list.d/ `mv /etc/apt/sources.list.d/mysql.sources /etc/apt/sources.list.d/mysql.sources.nope` The thing is I can't pass the script setup which eventually goes to a install-mysql.sh which install the repo and so the expired key. An adjustement may be necessary in this script ? Or maybe a way to get the installation process back after this step ?
OVERLORD commented 2026-02-05 02:37:47 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 29, 2025):

switched to mariadb

@MickLesk commented on GitHub (Oct 29, 2025): switched to mariadb
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1875
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?