starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Joplin Server LXC install fails #2152

New Issue
Closed
opened 2026-02-05 03:58:13 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 03:58:13 +03:00
Owner
Copy Link

Originally created by @Hotzigetty on GitHub (Dec 11, 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?

Joplin Server

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.2-2-pve

📝 Provide a clear and concise description of the issue.

Tried installing Joplin Server from the scripts - both github and gitea and it fails with a 403 error. I reran the script with verbose logs enabled and attached here.

install-lxc-105-f722bc44 (1).log

🔄 Steps to reproduce the issue.

Run the script, either github or gitea, with default settings or customized settings.

❌ Paste the full error output (if available).

install-lxc-105-f722bc44 (1).log

🖼️ Additional context (optional).

No response

Originally created by @Hotzigetty on GitHub (Dec 11, 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? Joplin Server ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/joplin-server.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? pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.2-2-pve ### 📝 Provide a clear and concise description of the issue. Tried installing Joplin Server from the scripts - both github and gitea and it fails with a 403 error. I reran the script with verbose logs enabled and attached here. [install-lxc-105-f722bc44 (1).log](https://github.com/user-attachments/files/24099148/install-lxc-105-f722bc44.1.log) ### 🔄 Steps to reproduce the issue. Run the script, either github or gitea, with default settings or customized settings. ### ❌ Paste the full error output (if available). [install-lxc-105-f722bc44 (1).log](https://github.com/user-attachments/files/24099155/install-lxc-105-f722bc44.1.log) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:58:13 +03:00
OVERLORD commented 2026-02-05 03:58:19 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 15, 2025):

where you get issues? Your log is cropped at database. I cant reproduce it. Installed Joplin 4 Times now (different nodes) / 403 mean in the most cases an github api rate limit

@MickLesk commented on GitHub (Dec 15, 2025): where you get issues? Your log is cropped at database. I cant reproduce it. Installed Joplin 4 Times now (different nodes) / 403 mean in the most cases an github api rate limit
OVERLORD commented 2026-02-05 03:58:25 +03:00
Author
Owner
Copy Link

@Hotzigetty commented on GitHub (Dec 15, 2025):

where you get issues? Your log is cropped at database. I cant reproduce it. Installed Joplin 4 Times now (different nodes) / 403 mean in the most cases an github api rate limit

That's weird that the log was cropped. I saw the 403 error and hence tried the gitea link as well.

I will try and install on another node to see if I can reproduce it and provide logs.

@Hotzigetty commented on GitHub (Dec 15, 2025): > where you get issues? Your log is cropped at database. I cant reproduce it. Installed Joplin 4 Times now (different nodes) / 403 mean in the most cases an github api rate limit That's weird that the log was cropped. I saw the 403 error and hence tried the gitea link as well. I will try and install on another node to see if I can reproduce it and provide logs.
OVERLORD commented 2026-02-05 03:58:28 +03:00
Author
Owner
Copy Link

@Hotzigetty commented on GitHub (Dec 15, 2025):

Ran on two nodes and no erros, guess it was just a bad moment for the laurent22 github repo on that day. closing now.

@Hotzigetty commented on GitHub (Dec 15, 2025): Ran on two nodes and no erros, guess it was just a bad moment for the laurent22 github repo on that day. closing now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2152
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?