Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Djoss last won the day on April 12 2019

Djoss had the most liked content!

Community Reputation

318 Very Good


About Djoss

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

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

  1. Where are you restoring the files ? If you are restoring at their original location, you first need to make /storage read/write (it is read only by default). You can change this in the container's settings (don't forget to toggle to the Advanced View).
  2. For HandBrake to display these kind of characters, you need to edit the container's settings and add a new "Variable" named "ENABLE_CJK_FONT" with a value of "1".
  3. You need to edit the container settings and add a new "Path". This basically maps a path from the host (unRAID) to a path in the container.
  4. WebSocket support must be enabled only when your proxied application requires it. When enabling Cache Assets, some assets, like images, will be served by NPM instead of your proxied application. I guess this can provide some performance improvements when a lot of them need to be loaded.
  5. @Rejserr, the web server is not starting because of the missing certificate file. If the certbot command suggested by @mattie112 doesn't fix the problem, you should try to edit the file under /mnt/user/appdata/NginxProxyManager/nginx/proxy_host/ that contains the following lines: ssl_certificate /etc/letsencrypt/live/npm-9/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-9/privkey.pem; And comment them: # ssl_certificate /etc/letsencrypt/live/npm-9/fullchain.pem; # ssl_certificate_key /etc/letsencrypt/live/npm-9/privkey.pem;
  6. You could verify if the time inside the container is correct: docker exec CloudBerryBackup date
  7. Look at /mnt/user/appdata/NginxProxyManager/log/letsencrypt/letsencrypt.log for more details about the challenge failure. Probably that NginxProxyManager is not reachable from the Internet ?
  8. The custom config you put there is inserted under the "server" context. The "log_format" statement is not allowed to be defined there. You could try to add "log_format" to /mnt/user/appdata/NginxProxyManager/nginx/http.conf. However, I'm not sure if it will work well since the log format is already defined somewhere else.
  9. The problem seems to be the ownership of /dev/sr5, which is root/root On my machine, I have: crw-rw---- 1 root cdrom 21, 1 Sep 8 19:08 /dev/sg1 Do you have something that change the ownership of the device ? You can try to set the group back to "cdrom" with: chgrp cdrom /dev/sg5 You can also run MakeMKV as root by setting the User ID and Group ID to 0, but that's not ideal.
  10. So if I understand correctly, the “Network Type” is not set to “Bridge”, but to “Custom : br0”? If this is the case, you are correct in saying that port 8080 can’t be changed. Container’s ports can be mapped to something else only with a “Bridge” network type. You can try to login to the container (docker exec -ti NginxProxyManager sh) and see if you can ping your other container from there.
  11. For some reason NPM is not able to access 170.63. Is NPM using the default bridge network ? What about 170.63 ?
  12. Which error are you getting exactly ? Are you accessing your site locally or remotely ?
  13. Can you try to run "tail -f /mnt/user/appdata/NginxProxyManager/log/proxy_host-XX.log", on the log file for your proxy host? Then access the site and see what is being logged.
  14. Correct, a license is required, unless you stick with an old version. See https://github.com/jlesage/docker-filebot#donation-supported-version