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

Sabnzbd warning: Unable to link to OpenSSL, optimized SSL connection functions will not be used #2344

New Issue
Open
opened 2025-11-20 05:27:46 -05:00 by saavagebueno · 11 comments
saavagebueno commented 2025-11-20 05:27:46 -05:00
Owner
Copy Link

Originally created by @bouwew on GitHub (Nov 17, 2025).

✅ Have you read and understood the above guidelines?

Yes

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

Sabnzbd

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0

📝 Provide a clear and concise description of the issue.

The warning message as written in the header shows up in the sabnzbd webinterface at every (re-)start of sabnzbd.

See also here: https://github.com/sabnzbd/sabnzbd/issues/3194#issuecomment-3540438274

🔄 Steps to reproduce the issue.

Install the Sabnzdb LXC via the helper script, then browse to http://(your local ip):7777

❌ Paste the full error output (if available).

None.

🖼️ Additional context (optional).

No response

Originally created by @bouwew on GitHub (Nov 17, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Sabnzbd ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/sabnzbd.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? 9.0 ### 📝 Provide a clear and concise description of the issue. The warning message as written in the header shows up in the sabnzbd webinterface at every (re-)start of sabnzbd. See also here: https://github.com/sabnzbd/sabnzbd/issues/3194#issuecomment-3540438274 ### 🔄 Steps to reproduce the issue. Install the Sabnzdb LXC via the helper script, then browse to http://(your local ip):7777 ### ❌ Paste the full error output (if available). None. ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issueinvestigation labels 2025-11-20 05:27:46 -05:00
saavagebueno commented 2025-11-20 05:27:46 -05:00
Author
Owner
Copy Link

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

ive read the issue, so they say "uv is faulty". So our opinion -> we use uv only because some issues. So the only solution is => Remove

@MickLesk commented on GitHub (Nov 17, 2025): ive read the issue, so they say "uv is faulty". So our opinion -> we use uv only because some issues. So the only solution is => Remove
saavagebueno commented 2025-11-20 05:27:46 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 17, 2025):

@MickLesk thanks for your quick reply!

What are you saying? Using uv solves some important issues, which is good of course :)
And my issue is less important? So I should accept this and close the issue?

Or did you mean something else?

@bouwew commented on GitHub (Nov 17, 2025): @MickLesk thanks for your quick reply! What are you saying? Using `uv` solves some important issues, which is good of course :) And my issue is less important? So I should accept this and close the issue? Or did you mean something else?
saavagebueno commented 2025-11-20 05:27:46 -05:00
Author
Owner
Copy Link

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

What I meant was that we specifically switched to UV system-wide, and if that causes problems, we'll have to consider removing the script. However, I'm currently working on circumventing the stupid bug (#555), as it has caused at least 200 issues, which was the main reason for switching to UV. Currently, I'm busy with the core redesign in VED and don't want to squeeze in any major tasks at the moment. It should have been finished six weeks ago.

@MickLesk commented on GitHub (Nov 17, 2025): What I meant was that we specifically switched to UV system-wide, and if that causes problems, we'll have to consider removing the script. However, I'm currently working on circumventing the stupid bug (#555), as it has caused at least 200 issues, which was the main reason for switching to UV. Currently, I'm busy with the core redesign in VED and don't want to squeeze in any major tasks at the moment. It should have been finished six weeks ago.
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 17, 2025):

OK thanks for clarifying!

This issue is not something major for me, the application functions as intended.
Also, I can use an alternative solution, I was just testing the helper script, being it available is very much appreciated 👍

Should I close this issue or do you prefer to keep it open?

@bouwew commented on GitHub (Nov 17, 2025): OK thanks for clarifying! This issue is not something major for me, the application functions as intended. Also, I can use an alternative solution, I was just testing the helper script, being it available is very much appreciated 👍 Should I close this issue or do you prefer to keep it open?
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

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

you can left it open - can you add an screenshot?

@MickLesk commented on GitHub (Nov 17, 2025): you can left it open - can you add an screenshot?
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 17, 2025):

Yes will do, when I'm back at home, later today.

@bouwew commented on GitHub (Nov 17, 2025): Yes will do, when I'm back at home, later today.
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 17, 2025):

Image
@bouwew commented on GitHub (Nov 17, 2025): <img width="924" height="279" alt="Image" src="https://github.com/user-attachments/assets/7696696d-4528-417e-a8d6-c0dee9fac5f9" />
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

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

can you try inside the lxc:

apt install -y \
    libssl-dev \
    libffi-dev
/opt/sabnzbd/venv/bin/pip install --no-binary sabctools --force-reinstall sabctools
@MickLesk commented on GitHub (Nov 18, 2025): can you try inside the lxc: ```bash apt install -y \ libssl-dev \ libffi-dev /opt/sabnzbd/venv/bin/pip install --no-binary sabctools --force-reinstall sabctools
saavagebueno commented 2025-11-20 05:27:47 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 18, 2025):

The apt install ... goes well, the 2nd part fails:

root@sabnzbd:~/.local/share/uv/python# /opt/sabnzbd/venv/bin/pip install --no-binary sabctools --force-reinstall sabctools
-bash: /opt/sabnzbd/venv/bin/pip: No such file or directory
@bouwew commented on GitHub (Nov 18, 2025): The `apt install ...` goes well, the 2nd part fails: ``` root@sabnzbd:~/.local/share/uv/python# /opt/sabnzbd/venv/bin/pip install --no-binary sabctools --force-reinstall sabctools -bash: /opt/sabnzbd/venv/bin/pip: No such file or directory ```
saavagebueno commented 2025-11-20 05:27:48 -05:00
Author
Owner
Copy Link

@bouwew commented on GitHub (Nov 18, 2025):

When I create a copy of the existing pip file (/usr/bin/pip) in the venv/bin directory, the 2nd part executes OK.

But, after a restart of sabnzbd the warning is still shown.

@bouwew commented on GitHub (Nov 18, 2025): When I create a copy of the existing `pip` file (`/usr/bin/pip`) in the `venv/bin` directory, the 2nd part executes OK. But, after a restart of sabnzbd the warning is still shown.
saavagebueno commented 2025-11-20 05:27:48 -05:00
Author
Owner
Copy Link

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

Allright, then default-pip doesnt solve it too

@MickLesk commented on GitHub (Nov 18, 2025): Allright, then default-pip doesnt solve it too
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 investigation not a script issue
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#2344
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?