aptalca

Community Developer
  • Posts

    3064
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by aptalca

  1. Looks like you modified your confs and referenced a custom cert. Our image does not use such a cert out of the box.
  2. You shouldn't need that. The latest updates to nginx.conf and proxy.conf auto enable websockets when needed.
  3. Did you add your network subnet to the routing section in the gui settings?
  4. Everything's up to date. It's explained in the readme
  5. Both would work, but simply copying the mapped folders is sufficient (don't forget mariadb data if you're using that)
  6. If you already reverse proxied, you don't need to connect via host ip. Just use the domain
  7. No, only subfolder. The subdomain one is for serving it at https://heimdall.mydomain.com Try connecting to your domain on a cell phone with wifi turned off
  8. If swag and heimdall are on the same custom bridge network, you don't even need to map ports for heimdall as swag will connect directly to the heimdall container over the custom docker bridge network.
  9. Can you exec into the container and install the package "ocl-icd-opencl-dev", restart and see if it works?
  10. We'll look into it. It probably just needs some opencl packages added. We have other images that do that.
  11. Yes on my-net Emby can stay on host, in which case you have to put the ip in the upstream app variable. Or you can switch to my-net and keep the proxy conf as is.
  12. I don't think the image supports opencl. What feature is that?
  13. You are severely confused. This container IS the speedtest server, with a frontend gui. I suggest you read our documentation before you dig into librespeed's before you get even more confused.
  14. Don't run manual commands inside the container unless we ask you to. We don't support that.
  15. Some of your conf files are really old. Delete them and restart the container. Those are including nginx.conf, proxy.conf, ssl.conf, etc.
  16. Make sure your nginx confs (ssl, proxy, nginx, etc.) are up to date. If you didn't customize them, you can delete them and restart the container. There was recently a change regarding websockets.
  17. I'm not the author of that video and am not familiar with it. You'll have to contact the author. All the info we publish is in the github/docker hub readme (linked in the first post) and the docs article I linked above. Typically, if you already own your own domain name, you don't need duckdns. Duckdns is a free alternative to owning a domain name.