Indemnity83

[note that this application isn't in Community Apps yet, working on the process and needed to start a support thread] Always Bring a Gift (ABAG) is a simple, self-hosted gift-tracking application designed to help you remember events, track people, and keep gift ideas organized across holidays, birthdays, celebrations, and family traditions. This thread serves as the official support and discussion area for running ABAG on Unraid through Community Applications. 🎁 What Is ABAG? If you’ve ever forgotten what you gave someone last year—or had a great idea weeks before an event and promptly forgot it—ABAG helps solve that. The app lets you: Track people and their preferences Record gift ideas for any time of year Organize events and prepare ahead Maintain a gift history so you always know what you’ve given Keep everything tidy in one simple, self-hosted interface It’s designed to be lightweight, easy to use, and easy to run on Unraid. 🚀 Features Clean, modern web interface Fast search and filtering Track ideas, gifts, and events Bulk import people from CSV or vCard files Add notes, links, prices, and more Automatic tracking of gift history Compatible with desktop and mobile browsers 🔑 Initial Login & First-Time Account Setup When ABAG starts for the first time, it automatically creates your initial admin account with a random admin password. You can find it in the container logs: Go to Docker in Unraid Click the icon next to the ABAG container Select the Logs option in the menu Look for the line showing your generated admin password You can then log in using: Email: [email protected] Password: (shown in the logs) After logging in, you can change these credentials from within the application. 🧪 Beta Status Always Bring a Gift is currently in beta and under active development. This means: Features may evolve UI refinements are ongoing Feedback is welcome and appreciated Breaking changes are possible prior to 1.0 If you encounter issues or have suggestions, please post them here or open an issue on GitHub. 🛠️ Configuration Notes Trusted Proxies (TRUSTED_PROXIES)If you use a reverse proxy (Traefik, Nginx Proxy Manager, SWAG, etc.), ABAG needs to know which proxies it should trust when interpreting incoming request headers (IP address, HTTPS detection, etc.). Default behavior: The Docker image ships with TRUSTED_PROXIES="*" to simplify local and homelab deployments. This means all proxies are trusted unless you override the value. Variable Purpose TRUSTED_PROXIES Limit proxy trust when using reverse proxies If you expose ABAG publicly (not generally recommended): You should explicitly set one of the following: Empty string ("") — trust no proxies Comma-separated list — trust only specific proxies Amazon Product Images (OPENWEB_NINJA_KEY)ABAG will always attempt to retrieve a product image from any URL you enter when adding a gift idea. For most retailers this works automatically — but Amazon actively blocks direct image scraping, and their official Product Advertising API is not practical for most self-hosted users. To help with this, ABAG includes optional integration with OpenWeb Ninja, a lightweight Amazon metadata API. It supports a free tier (100 requests/month), which is more than enough for typical use. To enable Amazon image fetching, set: Variable Purpose OPENWEB_NINJA_KEY API key for OpenWeb Ninja’s Amazon metadata service If the key is not set, ABAG will still work normally — Amazon images will simply not be retrievable, while all other retailer URLs continue to function as usual. Single Sign-On via AuthentikABAG supports logging in through Authentik for users who prefer centralized authentication or SSO across their self-hosted services. Instead of duplicating setup steps here, please refer to the official guide in the project repository: 👉 Authentik Setup Guide: https://github.com/Indemnity83/always-bring-a-gift/blob/main/AUTHENTIK_SETUP.md This document walks you through: Creating the correct OAuth2 provider Registering an ABAG application in Authentik Configuring redirect URLs Setting the required environment variables in Unraid Once those variables are set, ABAG automatically enables Authentik login. 💬 Support & Feedback GitHub Issues: https://github.com/Indemnity83/always-bring-a-gift/issues Project Repository: https://github.com/Indemnity83/always-bring-a-gift README / Documentation: https://github.com/Indemnity83/always-bring-a-gift/blob/main/README.md Feel free to post below if you need help, have a feature request, or spot a bug. 🙌 Thank You Thanks for trying Always Bring a Gift on Unraid! Your feedback directly helps shape the app toward a polished 1.0 release.

Hey everyone, I've recently run into an issue where SABnzbd is unable to download files. The error I'm seeing is: Cannot connect to server news.usenetserver.com [Server name does not resolve] I first thought it might be related to my VPN setup (I'm using PrivadoVPN), so I tried switching to a different VPN server and cert, but that didn’t resolve the issue. Here’s what I’ve tried so far: Switched VPN servers and certificates: No change. Checked DNS functionality: The logs indicate that DNS is working correctly. For example, I see: [debug] DNS operational, we can resolve name 'www.google.com' to address '198.18.0.17' Tested general connectivity: I can access the web interface without any problems through a browser, so it seems like the application and routing itself is functional. Given the above, it seems like SABnzbd can't resolve the Usenet server's domain, despite DNS working for other services on my system. I'm at a bit of a loss for what might be causing this. Does anyone have any suggestions for further troubleshooting or know what might be causing the container to fail DNS resolution specifically for the Usenet server? Thanks in advance for any help you can provide!

I was able to identify the cause of the repeated log entries in the debug.log file for me were related to Plex's healthcheck. The --no-healthcheck option can be used to disable the healthcheck mechanism in Docker. By default, Docker performs a healthcheck on each container to ensure that the container's main process is running and healthy. If the healthcheck fails, Docker can take appropriate action, such as restarting the container. In my case, it seems that the healthcheck mechanism is causing repeated log entries in the debug.log file. Disabling the healthcheck seems to be a workaround for this issue, but it's more of a band-aid than a solution. If the main process of the container crashes or becomes unresponsive, Docker may not be able to detect the issue and take appropriate action. To implement the work-around, edit your Plex container, toggle the 'advanced' setting using the switch in the top right of the page, and add --no-healthcheck to the 'Extra Parameters'. I hope this helps others, but if somebody knows more about how to troubleshoot the actual problem where healthcheck causes excessive logging, I'd greatly appreciate it.

I realize this is a serious necropost, but wanted to give @maciekish a huge thank you for sticking with this after the responses he got. I'm using a reverse proxy with Nginx and had the same problem and this lead me to the same solution. So for anybody getting here from Google you'll want to add the following to your Nginx config to get things working again. You could be clever and only apply it to the locations that are broken, but since my reverse proxy is not even exposed outside my network I just disabled gzip for the whole server definition: server { gzip off; ... } As an FYI to all the doubters above, if they still hold their positions. A reverse proxy is a very handy way to make it so you don't have to remember unique port numbers of all your internal services. http://unraid.home.local or http://sonarr.home.local are totally valid internal domains if your DNS is setup right and will hint the server to your password database tool of choice so you don't have it offering up 30 passwords because everything is on the same IP address of the server.

This makes managing the files on the system really complicated. Unraid really expects all the content to be 99:100. Read through coppit's message below; is this something that can be adapted into your container? I'm willing to make the PR if its something you would support.