SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-13 03:32:10 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Documenso script Error #1060

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

Originally created by @volcomgethub on GitHub (May 7, 2025).

Originally assigned to: @MickLesk on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

documenso

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

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

[ERROR] in line 88: exit code 0: while executing command $STD npm run build:web
/dev/fd/63: line 72: SPINNER_PID: unbound variable
root@prox2:~#

🔄 Steps to reproduce the issue.

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

run the script , but build:web is broken

❌ Paste the full error output (if available).

Run npm audit for details.
⠼npm error Missing script: "build:web"
npm error
npm error To see a list of scripts, run:
npm error npm run
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-05-03T15_53_01_568Z-debug-0.log

[ERROR] in line 88: exit code 0: while executing command $STD npm run build:web
/dev/fd/63: line 72: SPINNER_PID: unbound variable
root@prox2:~#

🖼️ Additional context (optional).

No response

Originally created by @volcomgethub on GitHub (May 7, 2025). Originally assigned to: @MickLesk on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? documenso ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/documenso.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. [ERROR] in line 88: exit code 0: while executing command $STD npm run build:web /dev/fd/63: line 72: SPINNER_PID: unbound variable root@prox2:~# ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/documenso.sh)" run the script , but build:web is broken ### ❌ Paste the full error output (if available). Run npm audit for details. ⠼npm error Missing script: "build:web" npm error npm error To see a list of scripts, run: npm error npm run npm error A complete log of this run can be found in: /root/.npm/_logs/2025-05-03T15_53_01_568Z-debug-0.log [ERROR] in line 88: exit code 0: while executing command $STD npm run build:web /dev/fd/63: line 72: SPINNER_PID: unbound variable root@prox2:~# ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bugexternal labels 2025-11-20 05:03:34 -05:00
saavagebueno commented 2025-11-20 05:03:36 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 7, 2025):

@MickLesk build:web script doesnt exist

@tremor021 commented on GitHub (May 7, 2025): @MickLesk build:web script doesnt exist
saavagebueno commented 2025-11-20 05:03:37 -05:00
Author
Owner
Copy Link

@vk2r commented on GitHub (May 7, 2025):

It's a 429 error (many retries).

I've found that in many of the scripts they download, there is some GitHub limiting rule that prevents many downloads. The files are as follows:

Even the SPINNER_PID error occurs when the file cannot be downloaded. This error is handled in this function:

error_handler() { source /dev/stdin <<<$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func) if [ -n "$SPINNER_PID" ] && ps -p "$SPINNER_PID" >/dev/null; then kill "$SPINNER_PID" >/dev/null; fi printf "\e[?25h" local exit_code="$?" local line_number="$1" local command="$2" local error_message="${RD}[ERROR]${CL} in line ${RD}$line_number${CL}: exit code ${RD}$exit_code${CL}: while executing command ${YW}$command${CL}" post_update_to_api "failed" "${command}" echo -e "\n$error_message\n" }

@vk2r commented on GitHub (May 7, 2025): It's a 429 error (many retries). I've found that in many of the scripts they download, there is some GitHub limiting rule that prevents many downloads. The files are as follows: - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func Even the SPINNER_PID error occurs when the file cannot be downloaded. This error is handled in this function: `error_handler() { source /dev/stdin <<<$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func) if [ -n "$SPINNER_PID" ] && ps -p "$SPINNER_PID" >/dev/null; then kill "$SPINNER_PID" >/dev/null; fi printf "\e[?25h" local exit_code="$?" local line_number="$1" local command="$2" local error_message="${RD}[ERROR]${CL} in line ${RD}$line_number${CL}: exit code ${RD}$exit_code${CL}: while executing command ${YW}$command${CL}" post_update_to_api "failed" "${command}" echo -e "\n$error_message\n" }`
saavagebueno commented 2025-11-20 05:03:37 -05:00
Author
Owner
Copy Link

@volcomgethub commented on GitHub (May 8, 2025):

@MickLesk build:web script doesn't exist

exactly , you can edit it and run just "build" but it does not finish the url side
Hopefully someone can update it soon, Documenso is a really nice open source solution

@volcomgethub commented on GitHub (May 8, 2025): > [@MickLesk](https://github.com/MickLesk) build:web script doesn't exist exactly , you can edit it and run just "build" but it does not finish the url side Hopefully someone can update it soon, Documenso is a really nice open source solution
saavagebueno commented 2025-11-20 05:03:38 -05:00
Author
Owner
Copy Link

@volcomgethub commented on GitHub (May 8, 2025):

It's a 429 error (many retries).

I've found that in many of the scripts they download, there is some GitHub limiting rule that prevents many downloads. The files are as follows:

Even the SPINNER_PID error occurs when the file cannot be downloaded. This error is handled in this function:

error_handler() { source /dev/stdin <<<$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func) if [ -n "$SPINNER_PID" ] && ps -p "$SPINNER_PID" >/dev/null; then kill "$SPINNER_PID" >/dev/null; fi printf "\e[?25h" local exit_code="$?" local line_number="$1" local command="$2" local error_message="${RD}[ERROR]${CL} in line ${RD}$line_number${CL}: exit code ${RD}$exit_code${CL}: while executing command ${YW}$command${CL}" post_update_to_api "failed" "${command}" echo -e "\n$error_message\n" }

Im pretty sure the links you posted are the "unpopulated" or frame work for the scripts to build the container and options

i could be wrong as i dont really know how to write much code, from what i can see there is no build:web script so it breaks ,
if build:web or "web" was defined i assume it would finish the browser side login stuff

@volcomgethub commented on GitHub (May 8, 2025): > It's a 429 error (many retries). > > I've found that in many of the scripts they download, there is some GitHub limiting rule that prevents many downloads. The files are as follows: > > * https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/build.func > * https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func > > Even the SPINNER_PID error occurs when the file cannot be downloaded. This error is handled in this function: > > `error_handler() { source /dev/stdin <<<$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/api.func) if [ -n "$SPINNER_PID" ] && ps -p "$SPINNER_PID" >/dev/null; then kill "$SPINNER_PID" >/dev/null; fi printf "\e[?25h" local exit_code="$?" local line_number="$1" local command="$2" local error_message="${RD}[ERROR]${CL} in line ${RD}$line_number${CL}: exit code ${RD}$exit_code${CL}: while executing command ${YW}$command${CL}" post_update_to_api "failed" "${command}" echo -e "\n$error_message\n" }` Im pretty sure the links you posted are the "unpopulated" or frame work for the scripts to build the container and options i could be wrong as i dont really know how to write much code, from what i can see there is no build:web script so it breaks , if build:web or "web" was defined i assume it would finish the browser side login stuff
saavagebueno commented 2025-11-20 05:03:38 -05:00
Author
Owner
Copy Link

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

i take a look in next hours

@MickLesk commented on GitHub (May 8, 2025): i take a look in next hours
saavagebueno commented 2025-11-20 05:03:39 -05:00
Author
Owner
Copy Link

@volcomgethub commented on GitHub (May 8, 2025):

i take a look in next hours

did you have a chance to look at it ? ill work on it if you can point me in the right direction

@volcomgethub commented on GitHub (May 8, 2025): > i take a look in next hours did you have a chance to look at it ? ill work on it if you can point me in the right direction
saavagebueno commented 2025-11-20 05:03:39 -05:00
Author
Owner
Copy Link

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

Nothing works, not only for me, i see in there repo many fails. But Support should be relative less

@MickLesk commented on GitHub (May 8, 2025): Nothing works, not only for me, i see in there repo many fails. But Support should be relative less
saavagebueno commented 2025-11-20 05:03:39 -05:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (May 10, 2025):

Looks like the devs have made a lot of changes to the build, and some other things; it's too complicated to fix for existing installs. People should reinstall, if my PR is merged - #4382.

Here is what existing installs could do, and it might save them from reinstalling (take a backup/snapshot beforehand!):

  1. Stop the service - systemctl stop documenso
  2. Backup your /opt/documenso/.env and wherever the actual data is stored (no idea, I don't use this app)
  3. rm -r /opt/documenso
  4. Download & extract the most recent release - curl -fsSLO https://github.com/documenso/documenso/archive/refs/tags/v1.10.0.zip && unzip v1.10.0.zip
  5. mv documenso-1.10.0 /opt/documenso
  6. restore your env file to /opt/documenso/.env (and your data)
  7. npm ci
  8. turbo run build --filter=@documenso/remix
  9. npm run prisma:migrate-deploy
  10. turbo daemon stop
  11. echo "1.10.0" > /opt/documenso_release.txt
  12. Edit /etc/systemd/system/documenso.service
  • WorkingDirectory=/opt/documenso
  • ExecStart=/usr/bin/turbo run start --filter=@documenso/remix
  • Save, close and run systemctl daemon-reload
  1. Start the service - systemctl start documenso
  2. Cross your fingers & toes
@vhsdream commented on GitHub (May 10, 2025): Looks like the devs have made a lot of changes to the build, and some other things; it's too complicated to fix for existing installs. People should reinstall, if my PR is merged - #4382. Here is what existing installs could do, and it might save them from reinstalling (take a backup/snapshot beforehand!): 1. Stop the service - `systemctl stop documenso` 2. Backup your `/opt/documenso/.env` and wherever the actual data is stored (no idea, I don't use this app) 3. `rm -r /opt/documenso` 4. Download & extract the most recent release - `curl -fsSLO https://github.com/documenso/documenso/archive/refs/tags/v1.10.0.zip && unzip v1.10.0.zip` 5. `mv documenso-1.10.0 /opt/documenso` 6. restore your env file to `/opt/documenso/.env` (and your data) 7. `npm ci` 8. `turbo run build --filter=@documenso/remix` 9. `npm run prisma:migrate-deploy` 10. `turbo daemon stop` 11. `echo "1.10.0" > /opt/documenso_release.txt` 12. Edit `/etc/systemd/system/documenso.service` - `WorkingDirectory=/opt/documenso` - `ExecStart=/usr/bin/turbo run start --filter=@documenso/remix` - Save, close and run `systemctl daemon-reload` 13. Start the service - `systemctl start documenso` 14. Cross your fingers & toes
saavagebueno commented 2025-11-20 05:03:39 -05:00
Author
Owner
Copy Link

@volcomgethub commented on GitHub (May 12, 2025):

is the script gone ? not on the site any more and it fails before it starts now ....
@vhsdream @MickLesk @tremor021

https://community-scripts.github.io/ProxmoxVE/ cant find it on the site any more either

@volcomgethub commented on GitHub (May 12, 2025): is the script gone ? not on the site any more and it fails before it starts now .... @vhsdream @MickLesk @tremor021 https://community-scripts.github.io/ProxmoxVE/ cant find it on the site any more either
saavagebueno commented 2025-11-20 05:03:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 12, 2025):

currently on backup state until it work again

@MickLesk commented on GitHub (May 12, 2025): currently on backup state until it work again
saavagebueno commented 2025-11-20 05:03:40 -05:00
Author
Owner
Copy Link

@volcomgethub commented on GitHub (May 12, 2025):

its being worked on ? any eta ?
Thank You !

@volcomgethub commented on GitHub (May 12, 2025): its being worked on ? any eta ? Thank You !
saavagebueno commented 2025-11-20 05:03:41 -05:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (May 13, 2025):

its being worked on ? any eta ? Thank You !

The fix was merged 3 days ago - just run the command that you would normally find on the Helper Scripts page:

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

But it's a breaking change so running the update function in an existing installation of Documenso won't work.

@vhsdream commented on GitHub (May 13, 2025): > its being worked on ? any eta ? Thank You ! The fix was merged 3 days ago - just run the command that you would normally find on the Helper Scripts page: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/documenso.sh)"` But it's a breaking change so running the update function in an existing installation of Documenso won't work.
saavagebueno commented 2025-11-20 05:03:41 -05:00
Author
Owner
Copy Link

@kbkozlev commented on GitHub (May 14, 2025):

I just tested the script, and it works, but what are the default login details?

@kbkozlev commented on GitHub (May 14, 2025): I just tested the script, and it works, but what are the default login details?
saavagebueno commented 2025-11-20 05:03:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 14, 2025):

I just tested the script, and it works, but what are the default login details?

  "default_credentials": {
        "username": "helper-scripts@local.com",
        "password": "helper-scripts"
    },
@MickLesk commented on GitHub (May 14, 2025): > I just tested the script, and it works, but what are the default login details? ```json "default_credentials": { "username": "helper-scripts@local.com", "password": "helper-scripts" },
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 external
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#1060
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?