-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 [Free Games Claimer] Unable to start addon #1617
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Just adding that I have the same issue so this doesn't get closed automatically |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Does anyone have any ideas on how to get this working? |
No idea. If I could fine the script in question in the repo I might have a starting point in figuring out how to fix this but it doesn't show up when I search for it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The log states what you need to do. Make sure you've customized your The mentioned script |
Is it better in the latest pushed version ? |
ah no it's another error in config.yaml script - I'll solve it a bit later |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Getting the error
Error : /etc/cont-init.d/99-run.sh exiting 1
on starting. Config appears to be read correctly (I have redacted information from the config section of log).This file does not appear to be present: /config/addons_autoscripts/free-games-claimer.sh
Reproduction steps
Addon Logs
Architecture
aarch64
OS
HAos
The text was updated successfully, but these errors were encountered: