[GH-ISSUE #54] Install not complete #44

New issue

Closed

opened 2026-03-02 15:47:28 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 15:47:28 +03:00

Owner

Originally created by @kayvanaarssen on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/54

Just installed with the oneliner install.
But it stops at step 6/6

Used: curl -sSL https://raw.githubusercontent.com/PegaProx/project-pegaprox/refs/heads/main/deploy.sh | sudo bash

Nothing is running yet.

═══════════════════════════════════════════════════════════════════════════
Step 6/6: Configuring Service
═══════════════════════════════════════════════════════════════════════════

Select access port:
  1) Default (5000) - Standard ports
  2) HTTPS (443)    - Professional setup
  3) Custom         - Enter your own

root@pegaprox-01:~#

Where can we collect some logs for you to check?

Originally created by @kayvanaarssen on GitHub (Feb 21, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/54 Just installed with the oneliner install. But it stops at step 6/6 Used: `curl -sSL https://raw.githubusercontent.com/PegaProx/project-pegaprox/refs/heads/main/deploy.sh | sudo bash` Nothing is running yet. ``` ═══════════════════════════════════════════════════════════════════════════ Step 6/6: Configuring Service ═══════════════════════════════════════════════════════════════════════════ Select access port: 1) Default (5000) - Standard ports 2) HTTPS (443) - Professional setup 3) Custom - Enter your own root@pegaprox-01:~# ``` Where can we collect some logs for you to check?

kerem closed this issue

2026-03-02 15:47:29 +03:00

kerem commented

2026-03-02 15:47:29 +03:00

Author

Owner

@johnzastrow commented on GitHub (Feb 21, 2026):

This happens to me too. But this fix to line 231 let it advance:

The script has set -e at line 13, which means it will exit immediately if any command fails. When read can't access stdin (which happens when the script is piped via curl | sudo bash or when stdin is redirected), the read command fails silently, causing the entire script to exit.

Here's the fix - add a check to ensure stdin is available before attempting interactive input:

228 print_step "Step 6/6: Configuring Service"
229
230 # Interactive port selection
231 - if [ "$INTERACTIVE" = true ]; then
231 + if [ "$INTERACTIVE" = true ] && [ -t 0 ]; then
232 echo -e "${YELLOW}Select access port:${NC}"
233 echo " 1) Default (5000) - Standard ports"
234 echo " 2) HTTPS (443) - Professional setup"

@johnzastrow commented on GitHub (Feb 21, 2026): This happens to me too. But this fix to line 231 let it advance: The script has set -e at line 13, which means it will exit immediately if any command fails. When read can't access stdin (which happens when the script is piped via curl | sudo bash or when stdin is redirected), the read command fails silently, causing the entire script to exit. Here's the fix - add a check to ensure stdin is available before attempting interactive input: 228 print_step "Step 6/6: Configuring Service" 229 230 # Interactive port selection 231 - if [ "$INTERACTIVE" = true ]; then 231 + if [ "$INTERACTIVE" = true ] && [ -t 0 ]; then 232 echo -e "${YELLOW}Select access port:${NC}" 233 echo " 1) Default (5000) - Standard ports" 234 echo " 2) HTTPS (443) - Professional setup"

kerem commented

2026-03-02 15:47:29 +03:00

Author

Owner

@kayvanaarssen commented on GitHub (Feb 21, 2026):

Yep, that works!

@kayvanaarssen commented on GitHub (Feb 21, 2026): Yep, that works!