Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Qesaru

Members
  • Joined

  • Last visited

Everything posted by Qesaru

  1. First of all, thanks for your replies. I used to use DynDNS on my router, but because that led to difficulties, it's now running on my Unraid box via die qmcgaw/ddns-updater Docker container. My registrar is Strato, if that matters. I don't know what you mean by targeting the NPM container. I don't quite understand what you mean with that. Could you reframe the quesion? I can't figure out what my IPv6 is supposed to be. My router once ran IPv4 via DS-Lite, but I made my ISP set me to native IPv4 (as far as I know at least) because I couldn't get things working with DS-Lite. Interestingly my router doesn't show any IPv6 Interface-ID for my server and therefore doesn't let me do any IPv6 settings. I can also not forward any ports to IPv6, only to IPv4. Other devices on my network however do have an IPv6 Interface-ID and have changable settings under the IPv6 section in the port forwarding menu. That seems to be the best solution to me. How do I do this? Thank you for your patience, I know my reply is probably not as helpful, but I hope you can help me fix this problem and get a better understanding of it.
  2. Thank you for your help! For readability I put the code at the end. I've also attached the anonymized file, but this seems to be the relevant part. According to the hint letsencrypt needs some sort of file that's created by my certbot, however I don't know what I need to do in order to make it available. { "identifier": { "type": "dns", "value": "sub.mydomain.com" }, "status": "invalid", "expires": "2025-09-19T22:29:59Z", "challenges": [ { "type": "http-01", "url": "https://acme-v02.api.letsencrypt.org/acme/chall/1951384786/582604934051/680gKQ", "status": "invalid", "validated": "2025-09-12T22:29:59Z", "error": { "type": "urn:ietf:params:acme:error:connection", "detail": "2001:###:####:####:####:####:####:3736: Fetching https://sub.mydomain.com/.well-known/acme-challenge/#########################: Error getting validation data", "status": 400 }, "token": "#########################", "validationRecord": [ { "url": "http://sub.mydomain.com/.well-known/acme-challenge/#########################", "hostname": "sub.mydomain.com", "port": "80", "addressesResolved": [ "46.###.###.###", "2001:###:####:####:####:####:####:3736" ], "addressUsed": "2001:###:####:####:####:####:####:3736" }, { "url": "http://sub.mydomain.com/.well-known/acme-challenge/#########################", "hostname": "sub.mydomain.com", "port": "80", "addressesResolved": [ "46.###.###.###", "2001:###:####:####:####:####:####:3736" ], "addressUsed": "46.###.###.###" }, { "url": "https://sub.mydomain.com/.well-known/acme-challenge/#########################", "hostname": "sub.mydomain.com", "port": "443", "addressesResolved": [ "46.###.###.###", "2001:###:####:####:####:####:####:3736" ], "addressUsed": "2001:###:####:####:####:####:####:3736" } ] } ] } 2025-09-13 00:30:01,203:DEBUG:acme.client:Storing nonce: z38KXhlRljrs_ghQTq4a7sG4IqZVTPmWQ-0xnHhhaT3LR9gy4dw 2025-09-13 00:30:01,204:INFO:certbot._internal.auth_handler:Challenge failed for domain sub.mydomain.com 2025-09-13 00:30:01,204:INFO:certbot._internal.auth_handler:http-01 challenge for sub.mydomain.com 2025-09-13 00:30:01,204:DEBUG:certbot._internal.display.obj:Notifying user: Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: Domain: sub.mydomain.com Type: connection Detail: 2001:###:####:####:####:####:####:3736: Fetching https://sub.mydomain.com/.well-known/acme-challenge/#########################: Error getting validation data Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet. 2025-09-13 00:30:01,205:DEBUG:certbot._internal.error_handler:Encountered exception: Traceback (most recent call last): File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort) File "/opt/certbot/lib/python3.11/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations raise errors.AuthorizationError('Some challenges have failed.') certbot.errors.AuthorizationError: Some challenges have failed. letsencrypt.log
  3. Hello, I'm using the NPM container in Unraid for quite a while and I'm quite happy with how it works. However I do encounter a strange problem that I can't find a solution for: Whenever I want to renew an existing certificat, I get this Error: This Error occurs when I try to manually renew a certificat via certbot. My container log just gave me an error while trying to auto-renew (referring to the letsencrypt log, that I don't understand. I can share it if you want). Creating a new certificat for that same host however is no problem. I checked the things you recommended. My Port is reachable I get a result by entering my IPv4: And the target container is reachable via NPM:
  4. Hey, I don't know if you can help me with this, but I'll try anyways. I want to run the Handbrake Container from jlesage (you can see my settings in the screenshot) to convert movies to H.265 using the iGPU. I'm running a self built system with an i3 12100. Everything on my system works fine, only Handbrake doesn't show the option for H.265 (QSV). However H.264 (QSV) works just fine, which means that the container can access the iGPU. I've already asked jlesage for help by starting an issue on github. https://github.com/jlesage/docker-handbrake/issues/265 She said that the container doesn't seem to detect the hardware properly, but she doesn't seem to know a solution. I've seen a Reddit thread where someone said that updating their graphics driver fixed a similar issue for them. Since the closest I have to a graphics driver is your Intel GPU-TOP Plugin, and because I'm quite desperate to get this working, I'm asking if you have any advice - even though I know you're probably not responsible for this. qserver-diagnostics-20230630-1439.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.