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

Firefly III install script fails during Composer diagnosis – misleading exit code and Packagist HTTP error #1511

New Issue
Closed
opened 2026-02-05 01:24:26 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 01:24:26 +03:00
Owner
Copy Link

Originally created by @miguelalfayate on GitHub (Aug 21, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Firefly III

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/firefly.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.

When running the Firefly III install script from this repository, the Composer installation step fails during diagnostics with a misleading exit code 0 and an HTTP error related to Packagist.

🔄 Steps to reproduce the issue.

Run the Firefly III install script from this repo.

❌ Paste the full error output (if available).

⏳   Installing Composer  
You are already using the latest available Composer version 2.8.11 (stable channel).  
Checking platform settings: OK  
Checking git settings: No git process found  
Checking http connectivity to packagist: FAIL  
[Composer\Downloader\TransportException] The "http://repo.packagist.org/packages.json" file could not be downloaded (HTTP/1.1 451 unused)  
Checking https connectivity to packagist: OK  
Checking github.com rate limit: OK  
Checking disk free space: OK  
Checking pubkeys:  
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0  87719BA6 8F3BB723 4E5D42D0 84A14642  
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B  0C708369 153E328C AD90147D AFE50952  
OK  
Checking Composer version: OK  
Checking Composer and its dependencies for vulnerabilities: OK  
Composer version: 2.8.11  
PHP version: 8.4.11  
PHP binary path: /usr/bin/php8.4  
OpenSSL version: OpenSSL 3.0.16 11 Feb 2025  
curl version: 7.88.1 libz 1.2.13 brotli 1.0.9 zstd supported ssl OpenSSL/3.0.17  
zip: extension present, unzip present, 7-Zip not available  

[ERROR] in line 547: exit code 0: while executing command $STD "$COMPOSER_BIN" diagnose  

[ERROR] in line 1353: 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)"

🖼️ Additional context (optional).

No response

Originally created by @miguelalfayate on GitHub (Aug 21, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Firefly III ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/firefly.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. When running the Firefly III install script from this repository, the Composer installation step fails during diagnostics with a misleading exit code 0 and an HTTP error related to Packagist. ### 🔄 Steps to reproduce the issue. Run the Firefly III install script from this repo. ### ❌ Paste the full error output (if available). ``` ⏳ Installing Composer You are already using the latest available Composer version 2.8.11 (stable channel). Checking platform settings: OK Checking git settings: No git process found Checking http connectivity to packagist: FAIL [Composer\Downloader\TransportException] The "http://repo.packagist.org/packages.json" file could not be downloaded (HTTP/1.1 451 unused) Checking https connectivity to packagist: OK Checking github.com rate limit: OK Checking disk free space: OK Checking pubkeys: Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0 87719BA6 8F3BB723 4E5D42D0 84A14642 Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B 0C708369 153E328C AD90147D AFE50952 OK Checking Composer version: OK Checking Composer and its dependencies for vulnerabilities: OK Composer version: 2.8.11 PHP version: 8.4.11 PHP binary path: /usr/bin/php8.4 OpenSSL version: OpenSSL 3.0.16 11 Feb 2025 curl version: 7.88.1 libz 1.2.13 brotli 1.0.9 zstd supported ssl OpenSSL/3.0.17 zip: extension present, unzip present, 7-Zip not available [ERROR] in line 547: exit code 0: while executing command $STD "$COMPOSER_BIN" diagnose [ERROR] in line 1353: 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)" ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 01:24:26 +03:00
OVERLORD commented 2026-02-05 01:24:34 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 21, 2025):

Working fine here

  ⏳   Installing ComposerYou are already using the latest available Composer version 2.8.11 (stable channel).
Checking platform settings: OK
Checking git settings: No git process found
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
Checking pubkeys: 
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0  87719BA6 8F3BB723 4E5D42D0 84A14642
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B  0C708369 153E328C AD90147D AFE50952
OK
Checking Composer version: OK
Checking Composer and its dependencies for vulnerabilities: OK
Composer version: 2.8.11
PHP version: 8.4.11
PHP binary path: /usr/bin/php8.4
OpenSSL version: OpenSSL 3.0.16 11 Feb 2025
curl version: 7.88.1 libz 1.2.13 brotli 1.0.9 zstd supported ssl OpenSSL/3.0.17
zip: extension present, unzip present, 7-Zip not available
  ✔️   Composer is ready at /usr/local/bin/composer

do you have issues with https://repo.packagist.org/ ? (Adblock / PiHole)
pct enter (broken lxc id) and execute: curl -fsI https://repo.packagist.org/

@MickLesk commented on GitHub (Aug 21, 2025): Working fine here ```shell ⏳ Installing ComposerYou are already using the latest available Composer version 2.8.11 (stable channel). Checking platform settings: OK Checking git settings: No git process found Checking http connectivity to packagist: OK Checking https connectivity to packagist: OK Checking github.com rate limit: OK Checking disk free space: OK Checking pubkeys: Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0 87719BA6 8F3BB723 4E5D42D0 84A14642 Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B 0C708369 153E328C AD90147D AFE50952 OK Checking Composer version: OK Checking Composer and its dependencies for vulnerabilities: OK Composer version: 2.8.11 PHP version: 8.4.11 PHP binary path: /usr/bin/php8.4 OpenSSL version: OpenSSL 3.0.16 11 Feb 2025 curl version: 7.88.1 libz 1.2.13 brotli 1.0.9 zstd supported ssl OpenSSL/3.0.17 zip: extension present, unzip present, 7-Zip not available ✔️ Composer is ready at /usr/local/bin/composer ``` do you have issues with https://repo.packagist.org/ ? (Adblock / PiHole) pct enter <CTID> (broken lxc id) and execute: curl -fsI https://repo.packagist.org/
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#1511
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?