Jump to content

Djoss

Community Developer
  • Content Count

    1420
  • Joined

  • Last visited

  • Days Won

    9

Djoss last won the day on April 12

Djoss had the most liked content!

Community Reputation

263 Very Good

4 Followers

About Djoss

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The container's log is the place to look to see what happening with the automatic disc ripper.
  2. Ah, with the automatic disc ripper turned on, a disc is automatically ripped when inserted. So you cannot use the UI at the same time...
  3. Also, try to add a trailing slash ("/") to the "Forward Hostname / IP" field of your custom location.
  4. The guide you read is probably not for this container, as like you said, you don't need an external database. Which GUI you are talking about? The GUI of unRAID itself or NginxProxyManager?
  5. To confirm that you get the right certificates, run the following command: docker exec NginxProxyManager sh -c 'openssl s_client -connect <DNS NAME>:443 -showcerts </dev/null' And to verify the container resolves to the correct IP: docker exec NginxProxyManager nslookup <DNS NAME>
  6. You can try to remove it from the "SSL Certificates" page. Then re-create it from the proxy host settings.
  7. I guess you set the proxy url in the container settings? Also, since it seems to be an issue with bootstack not running properly behind a reverse proxy, maybe you could have better luck by seeking help from the app's support thread?
  8. You can look at the container's log to make sure that the devices didn't change. If not, then maybe this thread could help: https://www.makemkv.com/forum/viewtopic.php?f=1&t=19590 If you look at the MakeMKV forum, there are a couple instances of people reporting this error.
  9. Looks like a certificate is corrupted.... You can check if you can read the certificate at /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-1/fullchain.pem.
  10. If the certificate is not from Letsencrypt, then you are probably not reaching the container... or are you using a DNS service that could interfer?
  11. I would also check the log for your proxy host under /mnt/user/appdata/NginxProxyManager/log/nginx/ to see if you can get more details. Do you have the issue only when you access the domain name from your own network?
  12. If you re-insert the same disc, is it recognized? Did you try to just restart the container to see if this help?
  13. The umask setting was not used by the AMC script... this is now fixed.
  14. Thanks for your feedback. Both issues are now fixed