Privatebin: Update command fails #2010

Closed
opened 2026-02-05 03:19:06 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @SeDi343 on GitHub (Nov 15, 2025).

Have you read and understood the above guidelines?

yes

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

Privatebin

📂 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 13

📈 Which Proxmox version are you on?

PVE 9.0.10

📝 Provide a clear and concise description of the issue.

Running command update for privatebin from version 2.0.1 to 2.0.3 (but seems to try to install an older version or not) fails with following error and does not update binaries.

🔄 Steps to reproduce the issue.

  • Execute update on 2.0.1 binaries in verbose mode

Paste the full error output (if available).

    ____       _             __       ____  _     
   / __ \_____(_)   ______ _/ /____  / __ )(_)___ 
  / /_/ / ___/ / | / / __ `/ __/ _ \/ __  / / __ \
 / ____/ /  / /| |/ / /_/ / /_/  __/ /_/ / / / / /
/_/   /_/  /_/ |___/\__,_/\__/\___/_____/_/_/ /_/ 
                                                  

  ✔️   Update available: privatebin 2.0.1 → 1.7.9
  ✔️   Backup created
  ✔️   Deployed: privatebin (2.0.3)
  ⏳   Configuring PrivateBinchmod: cannot access '/opt/privatebin/data}': No such file or directory

[ERROR] in line 42: exit code 0: while executing command chmod -R 0755 /opt/privatebin/data}

root@privatebin-server:~#

This is everything you get from verbose update command.

🖼️ Additional context (optional).

No response

Originally created by @SeDi343 on GitHub (Nov 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Privatebin ### 📂 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 13 ### 📈 Which Proxmox version are you on? PVE 9.0.10 ### 📝 Provide a clear and concise description of the issue. Running command `update` for privatebin from version 2.0.1 to 2.0.3 (but seems to try to install an older version or not) fails with following error and does not update binaries. ### 🔄 Steps to reproduce the issue. - Execute `update` on 2.0.1 binaries in verbose mode ### ❌ Paste the full error output (if available). ``` ____ _ __ ____ _ / __ \_____(_) ______ _/ /____ / __ )(_)___ / /_/ / ___/ / | / / __ `/ __/ _ \/ __ / / __ \ / ____/ / / /| |/ / /_/ / /_/ __/ /_/ / / / / / /_/ /_/ /_/ |___/\__,_/\__/\___/_____/_/_/ /_/ ✔️ Update available: privatebin 2.0.1 → 1.7.9 ✔️ Backup created ✔️ Deployed: privatebin (2.0.3) ⏳ Configuring PrivateBinchmod: cannot access '/opt/privatebin/data}': No such file or directory [ERROR] in line 42: exit code 0: while executing command chmod -R 0755 /opt/privatebin/data} root@privatebin-server:~# ``` This is everything you get from verbose update command. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:19:06 +03:00
Author
Owner

@SeDi343 commented on GitHub (Nov 15, 2025):

Is it possible to update the container afterwards or do i need to install it with the new script? Asking since i have it in production already.

@SeDi343 commented on GitHub (Nov 15, 2025): Is it possible to update the container afterwards or do i need to install it with the new script? Asking since i have it in production already.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2010