starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

go2rtc wrong binary name #1356

New Issue
Closed
opened 2026-02-05 00:27:33 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 00:27:33 +03:00
Owner
Copy Link

Originally created by @erlonbie on GitHub (Jul 27, 2025).

✅ Have you read and understood the above guidelines?

yes

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

go2rtc

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

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

When the script finishes and you try to open the container ip + port, it gives a network error.

🔄 Steps to reproduce the issue.

Just install the script with default settings

❌ Paste the full error output (if available).

root@go2rtc:/# systemctl status go2rtc.service
× go2rtc.service
Loaded: loaded (/etc/systemd/system/go2rtc.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2025-07-27 12:10:42 -04; 54s ago
Duration: 1ms
Process: 11110 ExecStart=/opt/go2rtc/go2rtc_linux_amd64 (code=exited, status=203/EXEC)
Main PID: 11110 (code=exited, status=203/EXEC)
CPU: 496us

Jul 27 12:10:42 go2rtc (ux_amd64)[11110]: go2rtc.service: Failed to locate executable /opt/go2rtc/go2rtc_linux_amd64: No such >
Jul 27 12:10:42 go2rtc (ux_amd64)[11110]: go2rtc.service: Failed at step EXEC spawning /opt/go2rtc/go2rtc_linux_amd64: No such>
Jul 27 12:10:42 go2rtc systemd[1]: Started go2rtc.service.
Jul 27 12:10:42 go2rtc systemd[1]: go2rtc.service: Main process exited, code=exited, status=203/EXEC
Jul 27 12:10:42 go2rtc systemd[1]: go2rtc.service: Failed with result 'exit-code'.

🖼️ Additional context (optional).

To fix this I changed the ExecStart from /etc/systemd/system/go2rtc.service from go2rtc_linux_amd64 to go2rtc which is the binary inside /opt/go2rtc

Originally created by @erlonbie on GitHub (Jul 27, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? go2rtc ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/go2rtc.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. When the script finishes and you try to open the container ip + port, it gives a network error. ### 🔄 Steps to reproduce the issue. Just install the script with default settings ### ❌ Paste the full error output (if available). root@go2rtc:/# systemctl status go2rtc.service × go2rtc.service Loaded: loaded (/etc/systemd/system/go2rtc.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2025-07-27 12:10:42 -04; 54s ago Duration: 1ms Process: 11110 ExecStart=/opt/go2rtc/go2rtc_linux_amd64 (code=exited, status=203/EXEC) Main PID: 11110 (code=exited, status=203/EXEC) CPU: 496us Jul 27 12:10:42 go2rtc (ux_amd64)[11110]: go2rtc.service: Failed to locate executable /opt/go2rtc/go2rtc_linux_amd64: No such > Jul 27 12:10:42 go2rtc (ux_amd64)[11110]: go2rtc.service: Failed at step EXEC spawning /opt/go2rtc/go2rtc_linux_amd64: No such> Jul 27 12:10:42 go2rtc systemd[1]: Started go2rtc.service. Jul 27 12:10:42 go2rtc systemd[1]: go2rtc.service: Main process exited, code=exited, status=203/EXEC Jul 27 12:10:42 go2rtc systemd[1]: go2rtc.service: Failed with result 'exit-code'. ### 🖼️ Additional context (optional). To fix this I changed the `ExecStart` from /etc/systemd/system/go2rtc.service from `go2rtc_linux_amd64` to `go2rtc` which is the binary inside /opt/go2rtc
OVERLORD added the bug label 2026-02-05 00:27:33 +03:00
OVERLORD commented 2026-02-05 00:27:39 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jul 27, 2025):

Oops, yes, this is correct. Fix is incoming

@tremor021 commented on GitHub (Jul 27, 2025): Oops, yes, this is correct. Fix is incoming
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#1356
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?