• Content Count

  • Joined

  • Last visited

Everything posted by jm9843

  1. This was bugging me as well. I was able to update to the latest version (v. 3.9.4) without issue by: Stop the container Edit/Update the container Change the repository value to rocketchat/ Apply the changes I'm not sure if it is necessary but I do have "Enable additional search results from dockerHub" in CA settings set to Yes.
  2. I just dealt with this and was able to get my installation back up. The issue is that the hostname in the MongoDB container changes when you do the update; breaking the replica set. My steps to resolve: Open a console window for the MongoDB container # hostname make a note of the hostname of your container # mongo rs01:OTHER> rsconf = rs.conf() rs01:OTHER> rsconf.members = [{_id: 0, host: "<hostname>:27017"}] where <hostname> is the value that step #2 returned rs01:OTHER> rs.reconfig(rsconf,
  3. Your suspicion is correct. After a bit of digging I stopped the other container using port 9000 (it doesn't expose this thru a port mapping as it uses Host network), changed LMS back to the default port, and it played on the Boom right away. Is this something that can be "fixed" on the LMS docker file or is the solution to reserve 9000 for LMS? If it's the latter, having the port mapping as part of the template can be error prone. In any event, thanks for the suggestion.
  4. I'm kinda stumped right now. In attempting to bring my Squeezebox Booms back into service I installed this Docker on my Unraid server. Everything went swimmingly at first; using the template defaults with the exception of changing the WebUI port mapping (9000 already in use) and specifying my Music path (using a public share at the typical location like /mnt/user/<sharename>/Music/Archive/). I can access the webui and have it scan my music library successfully. The problem comes when I actually try to play anything back on the Squeezebox Boom (I also tried Squee
  5. Thanks for the reply. I got it working again by using an edited vbios from TechPowerUp per Spaceinvader's instruction. I also left Hyper-V extensions turned off for good measure even though that alone didn't fix it. I have no idea why it worked okay for some time without the bios dump but requires it now. But I'm just glad to have my gaming vm functional again.
  6. This just happened to me. I was happily passing an Nvidia GPU thru to a Windows 10 VM when it began reporting error code 43 out of nowhere. I'm not sure if it was an Nvidia driver update (I'm in the habit of updating GPU drivers) or if it coincided with a recent (planned) server shutdown. It sucks and I'm not sure where to go from here. If it is the driver, is it possible to uninstall it and roll back until I find the last one that works? I'm assuming that I can download older driver packages from Nvidia?
  7. I got a chance to try this again with the same result. To test, I uninstalled the plugin and deleted its appdata folder. I then reinstalled the plugin and, per your suggestion, used the default settings (with the exception of specifying the Dynamic DNS address). I still see results like so in the openvpn server log: Thu Jan 25 01:16:05 2018 TLS: Initial packet from [AF_INET], sid=0773056c 1556308b Thu Jan 25 01:17:05 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network co$ Thu Jan 25 01:1
  8. I seem to be having the same issue with a Windows 10 vm. Can you expound on your fix?
  9. If I'm thinking of it correctly, bond0 is the default interface (per Spaceinvader One's YouTube tutorial on the docker container). Since I'm not sure how to go about removing interfaces and I don't want to break anything else, I'll likely wait and try your next version to see if it solves my TLS handshake problem.
  10. I'm trying to switch from the openvpn-as docker container to your plugin but haven't been able to connect to the server (getting "TLS key negotiation failed" error). The one difference that I noticed is that the default route interface is br0, while the one that I was using successfully with the container was bond0 (as it's the interface listed first under unRAID/Info/Network). Could this be the problem and, if so, how would I go about changing the interface used by openvpn server? Fwiw, I'm using all default "Server config" settings with the exception of "Redirect-gateway" set t