j0nnymoe

Members
  • Posts

    353
  • Joined

  • Last visited

Everything posted by j0nnymoe

  1. Looks like corrupted database. Restore a backup.
  2. All you do is create a subdomain at your DNS - point it to your IP and then browse to https://subdomain.domain.com:portnumber .
  3. Again as per the readme, it states `need to change both sides` aka the container port and host port to match and you haven't done this.
  4. Did you create a new mapped port for the container?
  5. I assume you read this section of our readme https://github.com/linuxserver/docker-qbittorrent/blob/master/README.md#webui_port-variable
  6. It's not like we've got a forum / discord server or even IRC..
  7. Your guess is as good as mine, I'm not involved with them.
  8. Nothing - the latest tag hasn't been updated yet. https://hub.docker.com/r/emby/embyserver/tags
  9. You'll have to check the nvidia support list for the driver installed. We only have a handful of cards we can test in the group.
  10. You've hit the request limit: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: linnaeus.duckdns.org,linnio.duckdns.org,lserv.duckdns.org: see https://letsencrypt.org/docs/rate-limits/ Need to wait for that to reset which I believe is 7 days.
  11. There is a config included with our letsencrypt container.
  12. Run tvheadend in host instead of bridge. As per the documentation: https://github.com/linuxserver/docker-tvheadend#host-vs-bridge
  13. Glad to here it's working you. I'm planning on digging into this properly myself soon. I guess you could use something like dbeaver to read the dB?
  14. Correct, you just access it from your web browser.
  15. Of course, just have to connect a usb barcode scanner to your computer. The fact it's in a docker container doesn't limit that.
  16. Eh nothing too major to worry about IMO. The only one relevant is CVE‑2018‑6260 and you need physical access to the machine. Rest of the CVE's are windows.
  17. I would seek support from unifi directly. No one within the team will be able to test as we don't have any USG's.
  18. All the information to configure the convert plugin is here: https://beets.readthedocs.io/en/v1.4.7/plugins/convert.html
  19. Just using normal EmbyServer which is on v4. Beta just gets you some newer features earlier but with the possibility of breakage. I've never used plex let along plexpass so I can't compare.
  20. Can confirm, it doesn't remove the ability to pass through the iGPU. I have both my Nvidia card and iGPU passed to my Emby container. (There is a screenshot I posted further back in this thread)
  21. ahh I see, just remove the pass through for your iGPU and only give it the nvidia gpu
  22. SSH to your unraid server and run it from there? I've got both my iGPU and nvidia gpu enabled on my server and I've got a console no problem. Also no idea if plex does this but Emby allows you to have multiple GPU transcoders: