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

go2rtc is missing config file /opt/go2rtc/go2rtc.yaml #2108

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

Originally created by @MikePfaff on GitHub (Dec 3, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

📜 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

📈 Which Proxmox version are you on?

pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)

📝 Provide a clear and concise description of the issue.

The go2rtc LXC is missing the config file /opt/go2rtc/go2rtc.yaml. Therefore go2rtc starts with a default config (application internal config, so no config file). Even if i put my own file at /opt/go2rtc/go2rtc.yaml and restart, it is still using the default (internal) config.

When i go to the go2rtc web interface i can edit the config (which is empty, because there is no file yet) and save that config, which then creates a config file under /go2rtc.yaml (yes, in the / directory of the filesystem). I can then edit /go2rtc.yaml and if i then restart, that config from the /go2rtc.yaml file is used.

So at least the documentation https://community-scripts.github.io/ProxmoxVE/scripts?id=go2rtc should list the correct config file. Even better would be if

  • the config location was actually /opt/go2rtc/go2rtc.yaml (= go2rtc would be using the config from /opt/go2rtc/go2rtc.yaml)
  • there was a config file already at /opt/go2rtc/go2rtc.yaml

🔄 Steps to reproduce the issue.

  1. Create go2rc LXC using the script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/go2rtc.sh)"
  2. Put my own config at /opt/go2rtc/go2rtc.yaml
  3. Run service go2rtc restart

Expected result: go2rtc should be using my config from /opt/go2rtc/go2rtc.yaml
Actual result: go2rtc is NOT using my config from /opt/go2rtc/go2rtc.yaml

❌ Paste the full error output (if available).

None

🖼️ Additional context (optional).

No response

Originally created by @MikePfaff on GitHub (Dec 3, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? No (this issue will likely be closed automatically) ### 📜 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 ### 📈 Which Proxmox version are you on? pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve) ### 📝 Provide a clear and concise description of the issue. The go2rtc LXC is missing the config file /opt/go2rtc/go2rtc.yaml. Therefore go2rtc starts with a default config (application internal config, so no config file). Even if i put my own file at /opt/go2rtc/go2rtc.yaml and restart, it is still using the default (internal) config. When i go to the go2rtc web interface i can edit the config (which is empty, because there is no file yet) and save that config, which then creates a config file under /go2rtc.yaml (yes, in the / directory of the filesystem). I can then edit /go2rtc.yaml and if i then restart, that config from the /go2rtc.yaml file is used. So at least the documentation https://community-scripts.github.io/ProxmoxVE/scripts?id=go2rtc should list the correct config file. Even better would be if - the config location was actually /opt/go2rtc/go2rtc.yaml (= go2rtc would be using the config from /opt/go2rtc/go2rtc.yaml) - there was a config file already at /opt/go2rtc/go2rtc.yaml ### 🔄 Steps to reproduce the issue. 1. Create go2rc LXC using the script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/go2rtc.sh)" 2. Put my own config at /opt/go2rtc/go2rtc.yaml 3. Run service go2rtc restart Expected result: go2rtc should be using my config from /opt/go2rtc/go2rtc.yaml Actual result: go2rtc is NOT using my config from /opt/go2rtc/go2rtc.yaml ### ❌ Paste the full error output (if available). None ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:47:11 +03:00
OVERLORD commented 2026-02-05 03:47:24 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Dec 3, 2025):

Fixed in #9618

@tremor021 commented on GitHub (Dec 3, 2025): Fixed in #9618
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#2108
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?