MrLinux

Members
  • Posts

    65
  • Joined

  • Last visited

Converted

  • Personal Text
    personal text here

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MrLinux's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Same here. Not sure what is needed to fix this. Do we need to add the username/password as a new field in the docker container settings?
  2. How do I change the path from https://1.2.3.4/zm to https://1.2.3.4 ?
  3. Were you able to get the GTX 1650 for a reasonable price? If so, mind sharing where? Thanks
  4. Following too. Has anyone gotten any Ryzen APU working?
  5. Just curious, what is the reason since this works in the official docker?
  6. Hi, I received this alert from Fix Common Problems When running mcelog, I get this error root@unraid:~# mcelog mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported From another thread, this may be expected behavior since it's just warning us it's not an Intel CPU. Is it safe to ignore these errors or is there an actual issue? Thanks unraid-diagnostics-20201202-1551.zip
  7. Oh. So those of us with AMD can ignore this error? Sent from my iPhone using Tapatalk
  8. What are we supposed to do when we get this error message? I see that the module is included root@unraid:~# lsmod | grep mce edac_mce_amd 32768 0 Does this mean we don't need to manually run anything and just provide our diag file?
  9. What did you do to get your binhex-plex docker registered with your Plex account? Whenever I would login to plex by going directly to http://ip:32400/, it would tell me to download/install the Plex Server instead of showing/connecting to the docker's Plex Server. I've tried to Manually expose all the port (run command parameters: -p 32400:32400 -p 1900:1900/udp -p 3005:3005/udp -p 5353:535/udp -p 8324:8324 -p 32410:32410 -p 32412:32412/udp -p 32414:32414/udp -p 3246:3246) Restart the docker several times Checked NAT settings in my pfSense router Blow away the docker and appdata config and reinstall Troubleshooting the script and docker files None of it worked until I just tried to use another container distro of Plex. FWIW, it was also showing me serverUui errors when using bridge mode. Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign
  10. I ended up getting it working by moving over to another Plex Docker release (plexinc Plex Media Server). Assign the claim variable Set the bridge and static ip (br0.255 in my case) Troubleshooting Some extra steps may be needed before it works Logout of plex first Restarted the container a few times Double check the NAT rule (pfSense) After logging in again, it should show you the Plex Server setup screen instead of a client without a source (your Docker's Plex Server)
  11. Did you ever get this working? I'd like put Plex in a vlan as well. It's only working when set to host mode.
  12. Closing this as solved as I'm no longer having issues, although it would be interesting to know if there are actually any config issues which lead up to the corruption in the first place. Would like to avoid this from happening again. Thanks again for all the help @trurl
  13. Thanks, so I'm not crazy...or we're crazy together