Stirling-PDF - The current install and update script produce an error (v1.5.0, v1.6.0, v2.0.0) #2078

Closed
opened 2026-02-05 03:40:43 +03:00 by OVERLORD · 14 comments
Owner

Originally created by @kevinstsauveur on GitHub (Nov 26, 2025).

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

stirling-pdf

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

The current script, executed as :

  • an update in a properly functioning Stirling-pdf LXC (1.5.0)
  • as a new LXC

Both conclude without error in the terminal. But once I try to access the service, an error page come up :
Try 1 :
"HTTP ERROR 404 No static resource ."
Image
Try 2 (to get the logs with verbose)

Image

🔄 Steps to reproduce the issue.

  1. Access Proxmox shell
  2. Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)"
  3. Select Default settings
  4. Select "without login"

Paste the full error output (if available).

There's no error during update or new installation.

Here are the logs :
https://pastebin.com/GLJx7r9E

🖼️ Additional context (optional).

As relevant information, Stirling-PDF published yesterday two new versions :

Here's Stirling doc on how to migrate from V1 to V2 : https://docs.stirlingpdf.com/Migrating-to-V2.

The bot updated the version v1.5.0 to v2.0.0 in the commit https://github.com/community-scripts/ProxmoxVE/pull/9450. Since the reason I added the three (v1.5.0, v1.6.0, v2.0.0) to the title.

Originally created by @kevinstsauveur on GitHub (Nov 26, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? stirling-pdf ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. The [current script](https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh), executed as : - an update in a properly functioning Stirling-pdf LXC (1.5.0) - as a new LXC Both conclude without error in the terminal. But once I try to access the service, an error page come up : Try 1 : "HTTP ERROR 404 No static resource ." <img width="745" height="201" alt="Image" src="https://github.com/user-attachments/assets/c4d73d87-28c9-4d52-a0ce-f746d871bf56" /> Try 2 (to get the logs with verbose) <img width="745" height="204" alt="Image" src="https://github.com/user-attachments/assets/699565cb-2ceb-4f09-b8e8-f8c98bde5041" /> ### 🔄 Steps to reproduce the issue. 1. Access Proxmox shell 2. Run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)"` 3. Select Default settings 4. Select "without login" ### ❌ Paste the full error output (if available). There's no error during update or new installation. Here are the logs : [https://pastebin.com/GLJx7r9E](https://pastebin.com/GLJx7r9E) ### 🖼️ Additional context (optional). As relevant information, Stirling-PDF published yesterday two new versions : - [2.0 A true Acrobat Competitor release!](https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v2.0.0) - [1.6.0 ebook, video, pdf/a-3 and various other, Last V1 release!](https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v1.6.0) Here's Stirling doc on how to migrate from V1 to V2 : [https://docs.stirlingpdf.com/Migrating-to-V2](https://docs.stirlingpdf.com/Migrating-to-V2). The bot updated the version v1.5.0 to v2.0.0 in the commit [https://github.com/community-scripts/ProxmoxVE/pull/9450](https://github.com/community-scripts/ProxmoxVE/pull/9450). Since the reason I added the three (v1.5.0, v1.6.0, v2.0.0) to the title.
OVERLORD added the bug label 2026-02-05 03:40:43 +03:00
Author
Owner

@Aloe-recite commented on GitHub (Nov 26, 2025):

Same here, strangely the update process looked quite faster than usual

@Aloe-recite commented on GitHub (Nov 26, 2025): Same here, strangely the update process looked quite faster than usual
Author
Owner

@MickLesk commented on GitHub (Nov 26, 2025):

I will have take a look later

@MickLesk commented on GitHub (Nov 26, 2025): I will have take a look later
Author
Owner

@MickLesk commented on GitHub (Nov 26, 2025):

https://github.com/Stirling-Tools/Stirling-PDF/issues/5016#issuecomment-3581690347

Its maybe an jar issue. Ive tested the new released jar into this discussion and that worked fine. So maybe we wait for an hotfix.

@MickLesk commented on GitHub (Nov 26, 2025): https://github.com/Stirling-Tools/Stirling-PDF/issues/5016#issuecomment-3581690347 Its maybe an jar issue. Ive tested the new released jar into this discussion and that worked fine. So maybe we wait for an hotfix.
Author
Owner

@Aloe-recite commented on GitHub (Nov 26, 2025):

Stirling-Tools/Stirling-PDF#5016 (comment)

Its maybe an jar issue. Ive tested the new released jar into this discussion and that worked fine. So maybe we wait for an hotfix.

thanks a lot, as usual you guys are amazing

@Aloe-recite commented on GitHub (Nov 26, 2025): > [Stirling-Tools/Stirling-PDF#5016 (comment)](https://github.com/Stirling-Tools/Stirling-PDF/issues/5016#issuecomment-3581690347) > > Its maybe an jar issue. Ive tested the new released jar into this discussion and that worked fine. So maybe we wait for an hotfix. thanks a lot, as usual you guys are amazing
Author
Owner

@kevinstsauveur commented on GitHub (Nov 26, 2025):

Alright, so the version v2.0.1 is now out ! 🎊

There's an error using the script with the default settings with both "without login" set to yes and no. Here's some logs : https://pastebin.com/3ycrcLGT.

Image Image
@kevinstsauveur commented on GitHub (Nov 26, 2025): Alright, so the version [v2.0.1](https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v2.0.1) is now out ! 🎊 There's an error using the script with the default settings with both "without login" set to yes and no. Here's some logs : [https://pastebin.com/3ycrcLGT](https://pastebin.com/3ycrcLGT). <img width="1435" height="587" alt="Image" src="https://github.com/user-attachments/assets/31145021-e223-42cf-b914-aae70370684d" /> <img width="1435" height="587" alt="Image" src="https://github.com/user-attachments/assets/8b8b819d-b4de-49f8-a781-dfcb5f8e79e1" />
Author
Owner

@MickLesk commented on GitHub (Nov 26, 2025):

You are to fast, Release = Not directly exist files, they added after release

Tested now, release fetching working fine

✔️ Setup Temurin JDK 21
Do you want to use Stirling-PDF with Login? (no/n = without Login) [Y/n] y
✔️ Deployed: stirling-pdf (2.0.1)

✔️ Setup Temurin JDK 21
Do you want to use Stirling-PDF with Login? (no/n = without Login) [Y/n] n
✔️ Deployed: stirling-pdf (2.0.1)

@MickLesk commented on GitHub (Nov 26, 2025): You are to fast, Release = Not directly exist files, they added after release Tested now, release fetching working fine ✔️ Setup Temurin JDK 21 Do you want to use Stirling-PDF with Login? (no/n = without Login) [Y/n] y ✔️ Deployed: stirling-pdf (2.0.1) ✔️ Setup Temurin JDK 21 Do you want to use Stirling-PDF with Login? (no/n = without Login) [Y/n] n ✔️ Deployed: stirling-pdf (2.0.1)
Author
Owner

@MickLesk commented on GitHub (Nov 26, 2025):

both working fine, i close the issue for now

@MickLesk commented on GitHub (Nov 26, 2025): both working fine, i close the issue for now
Author
Owner

@Aloe-recite commented on GitHub (Nov 27, 2025):

I ran a 2.0-2.0.1 update but it completely broke. I’m going to restore the 1.5.0 backup and retry.

@Aloe-recite commented on GitHub (Nov 27, 2025): I ran a 2.0-2.0.1 update but it completely broke. I’m going to restore the 1.5.0 backup and retry.
Author
Owner

@krestaino commented on GitHub (Nov 27, 2025):

@Aloe-recite I just upgraded from 1.6.0 to 2.0.1 with the update script and it worked fine.

@krestaino commented on GitHub (Nov 27, 2025): @Aloe-recite I just upgraded from 1.6.0 to 2.0.1 with the `update` script and it worked fine.
Author
Owner

@ppskj178 commented on GitHub (Nov 28, 2025):

@MickLesk
I installed version 2.0.1 via an LXC script, but I'm stuck in a loop when trying to change settings.

When I try to save changes, the Web UI restart fails and tells me to restart manually. But even when I restart the service manually through the shell, the changes are not saved and revert to the previous state.

It seems like the application is unable to detect the correct installation path or JAR location within the LXC environment, which breaks the internal restart and save mechanism.

@ppskj178 commented on GitHub (Nov 28, 2025): @MickLesk I installed version 2.0.1 via an LXC script, but I'm stuck in a loop when trying to change settings. When I try to save changes, the Web UI restart fails and tells me to restart manually. But even when I restart the service manually through the shell, the changes are not saved and revert to the previous state. It seems like the application is unable to detect the correct installation path or JAR location within the LXC environment, which breaks the internal restart and save mechanism.
Author
Owner

@Aloe-recite commented on GitHub (Nov 28, 2025):

@ppskj178 confirmed also on my side. Setting up OIDC in particular broke the app two times in a row (setup OIDC - reboot manually as asked - app is broken, cpu and memory go up and down like a roller coaster; at 2 AM I didn’t read any logs sorry but this afternoon I’ll try to give it a better look)

@Aloe-recite commented on GitHub (Nov 28, 2025): @ppskj178 confirmed also on my side. Setting up OIDC in particular broke the app two times in a row (setup OIDC - reboot manually as asked - app is broken, cpu and memory go up and down like a roller coaster; at 2 AM I didn’t read any logs sorry but this afternoon I’ll try to give it a better look)
Author
Owner

@MickLesk commented on GitHub (Nov 28, 2025):

Report this there. Its not related to lxc, its Just an Linux.

@MickLesk commented on GitHub (Nov 28, 2025): Report this there. Its not related to lxc, its Just an Linux.
Author
Owner

@Aloe-recite commented on GitHub (Nov 28, 2025):

Thanks, done. @ppskj178 you may want to chime in too

@Aloe-recite commented on GitHub (Nov 28, 2025): Thanks, done. @ppskj178 you may want to chime in too
Author
Owner

@MickLesk commented on GitHub (Nov 28, 2025):

And remember, the app has been almost completely redesigned, so I think we can expect a few problems in the early v2 version. Let's see how it looks in a few weeks.

@MickLesk commented on GitHub (Nov 28, 2025): And remember, the app has been almost completely redesigned, so I think we can expect a few problems in the early v2 version. Let's see how it looks in a few weeks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2078