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

Flaresolverr update script breaks Flaresolverr install #1970

New Issue
Closed
opened 2025-11-20 05:20:56 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:20:56 -05:00
Owner
Copy Link

Originally created by @chunkyfen on GitHub (Sep 29, 2025).

✅ Have you read and understood the above guidelines?

yes

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

FlareSolverr

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

📈 Which Proxmox version are you on?

9

📝 Provide a clear and concise description of the issue.

When the command 'update' is executed from inside the Flaresolverr LXC, the script breaks the installation of Flaresolverr. It is no longer working. I get this error from Prowlarr 'Unable to connect to proxy: Connection refused (Ip of LXC:Default Port). Check the log surrounding this error for details'.

I recreated a new lxc using the install script and directly ran the update command from inside the container and it broke the install.

🔄 Steps to reproduce the issue.

Run Flaresolverr Install script on proxmox host.
Once install,ed from inside the flaresolverr lxc container, run the command 'update'
Then, the service is no longer working.

❌ Paste the full error output (if available).

Update
✔️ Stopped service
✔️ flaresolverr is already up-to-date (v3.3.25)
✔️ Started service
root@flaresolverr:# systemctl status flaresolverr
● flaresolverr.service - FlareSolverr
Loaded: loaded (/etc/systemd/system/flaresolverr.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2025-09-29 10:47:45 EDT; 3s ago
Process: 14776 ExecStart=/opt/flaresolverr/flaresolverr (code=exited, status=203/EXEC)
Main PID: 14776 (code=exited, status=203/EXEC)
CPU: 951us
root@flaresolverr:#

🖼️ Additional context (optional).

No response

Originally created by @chunkyfen on GitHub (Sep 29, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? FlareSolverr ### 📂 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 12 ### 📈 Which Proxmox version are you on? 9 ### 📝 Provide a clear and concise description of the issue. When the command 'update' is executed from inside the Flaresolverr LXC, the script breaks the installation of Flaresolverr. It is no longer working. I get this error from Prowlarr 'Unable to connect to proxy: Connection refused (Ip of LXC:Default Port). Check the log surrounding this error for details'. I recreated a new lxc using the install script and directly ran the update command from inside the container and it broke the install. ### 🔄 Steps to reproduce the issue. Run Flaresolverr Install script on proxmox host. Once install,ed from inside the flaresolverr lxc container, run the command 'update' Then, the service is no longer working. ### ❌ Paste the full error output (if available). Update ✔️ Stopped service ✔️ flaresolverr is already up-to-date (v3.3.25) ✔️ Started service root@flaresolverr:~# systemctl status flaresolverr ● flaresolverr.service - FlareSolverr Loaded: loaded (/etc/systemd/system/flaresolverr.service; enabled; preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2025-09-29 10:47:45 EDT; 3s ago Process: 14776 ExecStart=/opt/flaresolverr/flaresolverr (code=exited, status=203/EXEC) Main PID: 14776 (code=exited, status=203/EXEC) CPU: 951us root@flaresolverr:~# ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:20:56 -05:00
saavagebueno commented 2025-11-20 05:20:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 29, 2025):

Execute:
/opt/flaresolverr/flaresolverr

@MickLesk commented on GitHub (Sep 29, 2025): Execute: /opt/flaresolverr/flaresolverr
saavagebueno commented 2025-11-20 05:20:57 -05:00
Author
Owner
Copy Link

@chunkyfen commented on GitHub (Sep 29, 2025):

Execute: /opt/flaresolverr/flaresolverr

I mean, I know how to fix it, I repaired it, i'm just saying this is not the expected behavior I think.

@chunkyfen commented on GitHub (Sep 29, 2025): > Execute: /opt/flaresolverr/flaresolverr I mean, I know how to fix it, I repaired it, i'm just saying this is not the expected behavior I think.
saavagebueno commented 2025-11-20 05:20:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 29, 2025):

What Breaks the Install? Ive added the LXC at the moment, Run Overlay, Update and all working fine?

@MickLesk commented on GitHub (Sep 29, 2025): What Breaks the Install? Ive added the LXC at the moment, Run Overlay, Update and all working fine?
saavagebueno commented 2025-11-20 05:20:57 -05:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Oct 1, 2025):

Hey, I too think that there may be some minor issue.
What I did (two times, and with reboots in the middle):

  • install Flaresolverr using script - all working fine!
  • update to Trixie using the usual method, because why not - all working fine!
  • run "update", although there was nothing to update as predictable => got the "stopped service" -> "started service" messages in console as usual - app doesn't work anymore.
  • ran "/opt/flaresolverr/flaresolverr" but got "-bash: /opt/flaresolverr/flaresolverr: No such file or directory"

Not sure if I'm doing something wrong so please don't bash too hard....

@Aloe-recite commented on GitHub (Oct 1, 2025): Hey, I too think that there may be some minor issue. What I did (two times, and with reboots in the middle): * install Flaresolverr using script - all working fine! * update to Trixie using the usual method, because why not - all working fine! * run "update", although there was nothing to update as predictable => got the "stopped service" -> "started service" messages in console as usual - app doesn't work anymore. * ran "/opt/flaresolverr/flaresolverr" but got "-bash: /opt/flaresolverr/flaresolverr: No such file or directory" Not sure if I'm doing something wrong so please don't bash too hard....
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
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#1970
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?