saarg

Community Developer
 View Profile  See their activity

  • Posts

    5374

  • Joined

  • Last visited

  • Days Won

    8

 Content Type 

Everything posted by saarg

  1. saarg
    To be honest, I would recommend you to switch the backend. The kodi way just creates issues and the eternal update the database stuff. Do yourself a favour and switch to emby or Plex as the database. After I switched to emby and used the emby plugin, I haven't had any issues. I have completely stopped using kodi also now, as I use the emby clients. But then you have to pay for premiere.
  2. saarg
    Probably better to post in the nextcloud thread since this is related to nextcloud. And post exactly what you have done. Nobody can help when you don't supply detailed information.
  3. saarg
    Doesn't look like you read it all. Do you see the issues closed at the bottom? Is there anything you need in the newer releases that affect the headless function?
  4. saarg
    There is no default username/password for this container. And what is Yacy?
  5. saarg
    It only create one cert covering everything.
  6. saarg
    It's not integrated. It has the config files to use authelia. Follow the guide on our blog to set it up. https://blog.linuxserver.io
  7. saarg
    It's still maintained. See here https://github.com/linuxserver/docker-kodi-headless/issues/112
  8. saarg
    Follow this https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/
  9. saarg
    Unraid loads into RAM at boot and everything you do in the file system, except for the array disks, cache disk and under /boot is lost on a reboot. So what you are seeing is expected behaviour. This is not the correct subforum to post this in either, and posting multiple threads about the same issues isn't a good thing to do.
  10. saarg
    You have to fix your port forward or whatever it is that is blocking the connection.
  11. saarg
    No you can't, as nginx isn't started until you have a valid cert.
  12. saarg
    No it's not.
  13. saarg
    What do you mean by next? You only have stable and beta channel in the webui. There is info on updating using the command line in the first post.
  14. saarg
    It's the window that pops up when you update the container or change something in the template. You can trigger it by just erasing a character and entering it again in any of the fields and then hit apply.
  15. saarg
    If it's trying to get a new cert, you have not managed to use the same appdata folder as you did for letsencrypt.
  16. saarg
    It's still not correct even though you followed a guide. You do not own duckdns.org. you "own" blahblahblah.duckdns.org, so add that to domain name. Subdomains will be subdomain.blahblahblah.duckdns.org.
  17. saarg
    You can use the same container for both. Just create a new database for each instance that need it.
  18. saarg
    Your URL is not duckdns.org, it's your_user.duckdns.org. You don't own duckdns.org.
  19. saarg
    Perfect! Thanks for finding it.
  20. saarg
    Please bring back that function for guys that can't seem to hit the small balls. And I keep forgetting to hit the ball and not the title...
  21. saarg
    Not 100% correct. You can have multiple containers share the GPU, but you can't have a VM and containers use the GPU at the same time. To be able use the GPU for a container you have to unbind it from vfio so the drivers can be loaded.
  22. saarg
    Post the docker run command. Screenshots doesn't tell us everything.
  23. saarg
    Looks like you should check your disk for errors.
  24. saarg
    Post the screenshot so we can see that your port forwards are correct and also the other info missing.
  25. saarg
    The IP in the screenshot is the LAN adress. You have to find the WAN adress and compare it to the one provided by the webpage. If those two are not the same, then you are behind CGNAT. Hard to say if your port forward is correct as we don't see the description of the port forward table and we also don't have the docker run command of swag to see the validation method you have set up. It looks like you have not port forwarded to 80 to 180, but to 80.