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

Gitea not updating, no error fails silently #1659

New Issue
Closed
opened 2025-11-20 05:14:20 -05:00 by saavagebueno · 16 comments
saavagebueno commented 2025-11-20 05:14:20 -05:00
Owner
Copy Link

Originally created by @aptonline on GitHub (Aug 8, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Gitea

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

update

⚙️ 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.

I'm trying to update Gitea Version: 1.23.6 to the latest version but the update command is failing silently.

🔄 Steps to reproduce the issue.

Login to Gitlea LXC
Run update
no output or error

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

I've run Proxmox Community Repository update.

Originally created by @aptonline on GitHub (Aug 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Gitea ### 📂 What was the exact command used to execute the script? update ### ⚙️ 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. I'm trying to update Gitea Version: 1.23.6 to the latest version but the update command is failing silently. ### 🔄 Steps to reproduce the issue. Login to Gitlea LXC Run update no output or error ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). I've run Proxmox Community Repository update.
saavagebueno added the bug label 2025-11-20 05:14:20 -05:00
saavagebueno commented 2025-11-20 05:14:21 -05:00
Author
Owner
Copy Link

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

No Output with verbose? There are Minimum 7 Outputs 🤔

@MickLesk commented on GitHub (Aug 8, 2025): No Output with verbose? There are Minimum 7 Outputs 🤔
saavagebueno commented 2025-11-20 05:14:21 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 8, 2025):

I tried to run update -v but not output. Is there another way to run with verbose?

@aptonline commented on GitHub (Aug 8, 2025): I tried to run `update -v `but not output. Is there another way to run with verbose?
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

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

If you run Update you get an whiptail with dialogues. The 2nd is with verbose.

But it Sounds your update is broken, whats the output of cat /usr/bin/update ?

@MickLesk commented on GitHub (Aug 8, 2025): If you run Update you get an whiptail with dialogues. The 2nd is with verbose. But it Sounds your update is broken, whats the output of cat /usr/bin/update ?
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 8, 2025):

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/gitea.sh)"

@aptonline commented on GitHub (Aug 8, 2025): `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/gitea.sh)"`
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

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

Try to Run this inside the lxc Shell:
bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/gitea.sh)"

Do you get an dialogue?

@MickLesk commented on GitHub (Aug 8, 2025): Try to Run this inside the lxc Shell: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/gitea.sh)" Do you get an dialogue?
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 8, 2025):

Getting:

curl: (7) Failed to connect to git.community-scripts.org port 443 after 19 ms: Couldn't connect to server

@aptonline commented on GitHub (Aug 8, 2025): Getting: `curl: (7) Failed to connect to git.community-scripts.org port 443 after 19 ms: Couldn't connect to server`
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

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

Did your AdBlocker Block our Repo?

@MickLesk commented on GitHub (Aug 8, 2025): Did your AdBlocker Block our Repo?
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 8, 2025):

Just checked, not blocked. Only GitHub related traffic that is blocked is
collector.github.com

@aptonline commented on GitHub (Aug 8, 2025): Just checked, not blocked. Only GitHub related traffic that is blocked is `collector.github.com`
saavagebueno commented 2025-11-20 05:14:22 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 8, 2025):

All other community scripts update fine btw

@aptonline commented on GitHub (Aug 8, 2025): All other community scripts update fine btw
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

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

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

Should Not Work too? Then its an Network issue inside your lxc, Check this Out.

@MickLesk commented on GitHub (Aug 8, 2025): bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/gitea.sh)" Should Not Work too? Then its an Network issue inside your lxc, Check this Out.
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

@aptonline commented on GitHub (Aug 9, 2025):

That failed as well but I found the issue. For some reason my default gateway had been lost, entered that and its now allowing me to update. Thanks for the support.

@aptonline commented on GitHub (Aug 9, 2025): That failed as well but I found the issue. For some reason my default gateway had been lost, entered that and its now allowing me to update. Thanks for the support.
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

@ErwinEdx commented on GitHub (Oct 24, 2025):

Updating failed for me too. This is the output when selecting verbose, it still is version 1.23.8. After failing this I ran a manual update and this worked:

/ | / /___ ()__ ___ / () /_ ____ _
/ /| | / / __ / / __ / _ _/ / / / / _ / __ `/
/ ___ |/ / /_/ / / / / / // // / / // / // /
// |// ./// /_/_/ _//_/___/_,/
/_/
⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz
OK: 209 MiB in 138 packages
✔️ Updated Alpine Packages
⏳ Updating GiteaOK: 209 MiB in 138 packages
✔️ Updated Gitea
⏳ Restarting Gitea * Stopping gitea ... [ ok ]

  • Starting gitea ... [ ok ]
    ✔️ Restarted Gitea
    /dev/fd/62: line 21: pveversion: command not found

[ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')

/var/lib # # Check the actual version
/var/lib # gitea --version
Gitea version 1.23.8 built with GNU Make 4.4.1, go1.24.8 : tidb, sqlite, sqlite_unlock_notify
/var/lib #
/var/lib # # Check the binary modification date
/var/lib # ls -lh /usr/bin/gitea
-rwxr-xr-x 1 root root 97.9M Oct 12 20:13 /usr/bin/gitea
/var/lib #
/var/lib # # Check if the downloaded binary exists
/var/lib # ls -lh /tmp/gitea* 2>/dev/null
/var/lib # # Stop Gitea service
/var/lib # rc-service gitea stop

  • Stopping gitea ... [ ok ]
    /var/lib #
    /var/lib # # Download Gitea 1.24.6 to /tmp
    /var/lib # cd /tmp
    /tmp # wget -O gitea-1.24.6 https://dl.gitea.com/gitea/1.24.6/gitea-1.24.6-linux-amd64
    Connecting to dl.gitea.com (18.239.50.47:443)
    saving to 'gitea-1.24.6'
    gitea-1.24.6 100% |*************************************************************************************************| 107M 0:00:00 ETA
    'gitea-1.24.6' saved
    /tmp #
@ErwinEdx commented on GitHub (Oct 24, 2025): Updating failed for me too. This is the output when selecting verbose, it still is version 1.23.8. After failing this I ran a manual update and this worked: ___ __ _ _______ __ / | / /___ (_)___ ___ / ____(_) /____ ____ _ / /| | / / __ \/ / __ \/ _ \______/ / __/ / __/ _ \/ __ `/ / ___ |/ / /_/ / / / / / __/_____/ /_/ / / /_/ __/ /_/ / /_/ |_/_/ .___/_/_/ /_/\___/ \____/_/\__/\___/\__,_/ /_/ ⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz OK: 209 MiB in 138 packages ✔️ Updated Alpine Packages ⏳ Updating GiteaOK: 209 MiB in 138 packages ✔️ Updated Gitea ⏳ Restarting Gitea * Stopping gitea ... [ ok ] * Starting gitea ... [ ok ] ✔️ Restarted Gitea /dev/fd/62: line 21: pveversion: command not found [ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}') /var/lib # # Check the actual version /var/lib # gitea --version Gitea version 1.23.8 built with GNU Make 4.4.1, go1.24.8 : tidb, sqlite, sqlite_unlock_notify /var/lib # /var/lib # # Check the binary modification date /var/lib # ls -lh /usr/bin/gitea -rwxr-xr-x 1 root root 97.9M Oct 12 20:13 /usr/bin/gitea /var/lib # /var/lib # # Check if the downloaded binary exists /var/lib # ls -lh /tmp/gitea* 2>/dev/null /var/lib # # Stop Gitea service /var/lib # rc-service gitea stop * Stopping gitea ... [ ok ] /var/lib # /var/lib # # Download Gitea 1.24.6 to /tmp /var/lib # cd /tmp /tmp # wget -O gitea-1.24.6 https://dl.gitea.com/gitea/1.24.6/gitea-1.24.6-linux-amd64 Connecting to dl.gitea.com (18.239.50.47:443) saving to 'gitea-1.24.6' gitea-1.24.6 100% |*************************************************************************************************| 107M 0:00:00 ETA 'gitea-1.24.6' saved /tmp #
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

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

Create new issue

@MickLesk commented on GitHub (Oct 24, 2025): Create new issue
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

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

Updating failed for me too. This is the output when selecting verbose, it still is version 1.23.8. After failing this I ran a manual update and this worked:

/ | / /___ ()__ ___ / **() /__ ____ _ / /| | / / __ / / __ / _ __/ / __/ / **/ _ / __ `/ / ___ |/ / // / / / / / // // / / // **/ // / // |/_/ ./// /// **////_,/ // ⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz OK: 209 MiB in 138 packages ✔️ Updated Alpine Packages ⏳ Updating GiteaOK: 209 MiB in 138 packages ✔️ Updated Gitea ⏳ Restarting Gitea * Stopping gitea ... [ ok ]

  • Starting gitea ... [ ok ]
    ✔️ Restarted Gitea
    /dev/fd/62: line 21: pveversion: command not found

[ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')

/var/lib # # Check the actual version /var/lib # gitea --version Gitea version 1.23.8 built with GNU Make 4.4.1, go1.24.8 : tidb, sqlite, sqlite_unlock_notify /var/lib # /var/lib # # Check the binary modification date /var/lib # ls -lh /usr/bin/gitea -rwxr-xr-x 1 root root 97.9M Oct 12 20:13 /usr/bin/gitea /var/lib # /var/lib # # Check if the downloaded binary exists /var/lib # ls -lh /tmp/gitea* 2>/dev/null /var/lib # # Stop Gitea service /var/lib # rc-service gitea stop

  • Stopping gitea ... [ ok ]
    /var/lib #
    /var/lib # # Download Gitea 1.24.6 to /tmp
    /var/lib # cd /tmp
    /tmp # wget -O gitea-1.24.6 https://dl.gitea.com/gitea/1.24.6/gitea-1.24.6-linux-amd64
    Connecting to dl.gitea.com (18.239.50.47:443)
    saving to 'gitea-1.24.6'
    gitea-1.24.6 100% |*************************************************************************************************| 107M 0:00:00 ETA
    'gitea-1.24.6' saved
    /tmp #

Hello, How did you manually update gitea? updating via script fails with this message:

⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz
OK: 204 MiB in 106 packages
✔️ Updated Alpine Packages
⏳ Updating GiteaOK: 204 MiB in 106 packages
✔️ Updated Gitea
⏳ Restarting Gitea * Stopping gitea ... [ ok ]

  • Starting gitea ... [ ok ]
    ✔️ Restarted Gitea
    /dev/fd/62: line 21: pveversion: command not found

[ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')

@renjithstalin commented on GitHub (Oct 29, 2025): > Updating failed for me too. This is the output when selecting verbose, it still is version 1.23.8. After failing this I ran a manual update and this worked: > > / | / /___ (_)___ ___ / _**_(_) /**__ ____ _ / /| | / / __ / / __ / _ __**/ / __/ / **/ _ / __ `/ / ___ |/ / /_/ / / / / / /**_/ /_/ / / /_/ **/ /_/ / /_/ |_/_/ .**_/_/_/ /_/_/ _**_/_/__/___/__,_/ /_/ ⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz OK: 209 MiB in 138 packages ✔️ Updated Alpine Packages ⏳ Updating GiteaOK: 209 MiB in 138 packages ✔️ Updated Gitea ⏳ Restarting Gitea * Stopping gitea ... [ ok ] > > * Starting gitea ... [ ok ] > ✔️ Restarted Gitea > /dev/fd/62: line 21: pveversion: command not found > > [ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}') > > /var/lib # # Check the actual version /var/lib # gitea --version Gitea version 1.23.8 built with GNU Make 4.4.1, go1.24.8 : tidb, sqlite, sqlite_unlock_notify /var/lib # /var/lib # # Check the binary modification date /var/lib # ls -lh /usr/bin/gitea -rwxr-xr-x 1 root root 97.9M Oct 12 20:13 /usr/bin/gitea /var/lib # /var/lib # # Check if the downloaded binary exists /var/lib # ls -lh /tmp/gitea* 2>/dev/null /var/lib # # Stop Gitea service /var/lib # rc-service gitea stop > > * Stopping gitea ... [ ok ] > /var/lib # > /var/lib # # Download Gitea 1.24.6 to /tmp > /var/lib # cd /tmp > /tmp # wget -O gitea-1.24.6 https://dl.gitea.com/gitea/1.24.6/gitea-1.24.6-linux-amd64 > Connecting to dl.gitea.com (18.239.50.47:443) > saving to 'gitea-1.24.6' > gitea-1.24.6 100% |*************************************************************************************************| 107M 0:00:00 ETA > 'gitea-1.24.6' saved > /tmp # Hello, How did you manually update gitea? updating via script fails with this message: ⏳ Updating Alpine Packagesfetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/latest-stable/community/x86_64/APKINDEX.tar.gz OK: 204 MiB in 106 packages ✔️ Updated Alpine Packages ⏳ Updating GiteaOK: 204 MiB in 106 packages ✔️ Updated Gitea ⏳ Restarting Gitea * Stopping gitea ... [ ok ] * Starting gitea ... [ ok ] ✔️ Restarted Gitea /dev/fd/62: line 21: pveversion: command not found [ERROR] in line 21: exit code 0: while executing command pve_version=$(pveversion | awk -F'[/ ]' '{print $2}')
saavagebueno commented 2025-11-20 05:14:23 -05:00
Author
Owner
Copy Link

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

Fixed. Next time create an new issue. I only saw it by chance; all that was missing was an exit.

@MickLesk commented on GitHub (Oct 29, 2025): Fixed. Next time create an new issue. I only saw it by chance; all that was missing was an exit.
saavagebueno commented 2025-11-20 05:14:24 -05:00
Author
Owner
Copy Link

@renjithstalin commented on GitHub (Oct 30, 2025):

Fixed. Next time create an new issue. I only saw it by chance; all that was missing was an exit.

Will do, Thanks! script runs fine now.

@renjithstalin commented on GitHub (Oct 30, 2025): > Fixed. Next time create an new issue. I only saw it by chance; all that was missing was an exit. Will do, Thanks! script runs fine now.
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#1659
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?