Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Squid last won the day on October 1

Squid had the most liked content!

Community Reputation

2703 Hero

About Squid

  • Rank
    What would Chode do?


  • Gender
  • Personal Text
    AKA Flesh Gordon

Recent Profile Visitors

24542 profile views
  1. Can you post your diagnostics so that I can see why my tests are failing for you.
  2. Can you show me a screen shot of that...
  3. Probably best to ask in the Let's Encrypt / SWAG support threads so that other users who do use Unraid like this can see and possibly help.
  4. Tested this on 6.9 Beta 30 (ish) and it works perfectly. Looks like you've done two things here The template shows <WebUI>redacted.duckdns.org/</WebUI> and the applicable config line shows <Config Name="WebUI" Target="8080" Default="8080" Mode="tcp" Description="WebUI - Default 8888" Type="Port" Display="al> Now, the complete line isn't there (you've cut off the end of it), but what you did is that at some point, you edited the app, switched to advanced view, and then edited that URL to be what you've got above. You can change the port all day long when you edit the Port, but because the actual URL you've changed previously to the duckdns address doesn't include a reference to either the IP or the Port, nothing is ever going to happen. The appropriate line for WebUI is http://[IP]:[PORT:8080] Set up like that, the system will properly adjust the webUI in the drop down to reflect the IP address and the Port number you've selected. or, if you want it to go to a particular reverse proxy, then http://redacted.duckdns.com:[PORT:8080] Note that the 8080 IS correct in the above lines, regardless of whatever you change the port to be. It refers to the CONTAINER port, and when changing the port mapping you're adjust the host port.
  5. Fyi, a 512 Meg flash drive can be used in the array rather than burning a hard drive for this.
  6. https://forums.unraid.net/topic/57181-docker-faq/#comment-564314
  7. AFAIK, you need to in the router supply a route back to the server to communicate with containers that are on a separate IP.
  8. At the bottom of the page that's linked from Collabora's support link on the dropdown, there's a link to it's own forum. Probably your best bet for advice / help
  9. If there's a problem getting to the site (dockerHub), then not unavailable will appear
  10. Without going through the massively complicated directions, since you're using 6.9, instead of utilizing an unassigned device for things, you're better off (and it's going to just plain work better) if you had instead created a new cache pool. But, for the execution error, edit the container, make a change any change, revert it then hit apply. The exact reason why it's failing will appear following the docker run command that appears.
  11. How did you upgrade? via the nVidia plugin or via Tools - Update OS? Only upgrading via nVidia will keep the ability to hardware transcode
  12. What is the actual problem? The video just shows that it was in the middle of extracting
  13. Any chance you're running through a proxy?