jm9843

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/rocket.chat 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.

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, {force: true}) rs01:OTHER> rs.status() should return the details of your valid replica set (e.g. "ok" : 1) Cross your fingers and start your Rocket.Chat container These steps assume that you followed the general guidance in this thread (e.g. default port of 27017, replica set named 'rs01').

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.

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 SqueezePlayer on an Android phone). There is no sound and on the player display, the time never progresses. On the webui, the time does progress but when it gets to ~3 seconds remaining it loops back to ~8 seconds remaining and it does that in a loop, never progressing to the next track. My initial thought was that it's a permissions problem. But the directories/files at the above path are nobody:users and 777 and, as stated above, can be scanned by LMS correctly. Viewing the container logs doesn't reveal much, only seemingly unrelated errors and the odd warning about missing files in playlists or a malformed id3 tag in my library: [19-02-10 14:56:38.8050] Slim::Display::Lib::Fonts::__ANON__ (85) Warning: Unable to load TrueType font support: Can't locate loadable object for module Font::FreeType in @INC (@INC contains: /config/cache/InstalledPlugins /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/5.22.1/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22.1/x86_64-linux-gnu-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-gnu-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22 /usr/share/squeezeboxserver/lib /usr/share/squeezeboxserver/CPAN /usr/share/squeezeboxserver /usr/share/squeezeboxserver/CPAN /usr/share/squeezeboxserver /usr/sbin /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Slim/Display/Lib/Fonts.pm line 84. Compilation failed in require at /usr/share/perl5/Slim/Display/Lib/Fonts.pm line 84. Setting up systemd (229-4ubuntu21.16) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Operation failed: No such file or directory Any thoughts on what could be wrong? Fwiw, I tested using an old Windows 10 install on another physical machine on the same network with its own local music library and the Booms were able to playback from there fine. I should also add that I have Plex Media Server on the same Unraid box pointing to the same share/path and the music plays back okay on the Plex app.

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.

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?

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 192.168.86.1:43312 TLS: Initial packet from [AF_INET]192.168.86.1:43312, sid=0773056c 1556308b Thu Jan 25 01:17:05 2018 192.168.86.1:43312 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network co$ Thu Jan 25 01:17:05 2018 192.168.86.1:43312 TLS Error: TLS handshake failed Thu Jan 25 01:17:05 2018 192.168.86.1:43312 SIGUSR1[soft,tls-error] received, client-instance restarting On log page in bottom red text, I see br0 as the network interface (see screenshot). However, if I look at unRAID System Info, it appears to show bond0 (see screenshot). I'm unsure how to proceed.

I seem to be having the same issue with a Windows 10 vm. Can you expound on your fix?

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.

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 to "redirect-gateway def1". I'm also seeing the TLS error showing up in /var/log/openvpnserver.log which seems to confirm that traffic is being forwarded by the router correctly. Thanks.