Jump to content

LordShad0w

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LordShad0w

  • Rank
    Advanced Member
  • Birthday 05/09/1978

Converted

  • Gender
    Male
  • Location
    California

Recent Profile Visitors

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

  1. Just to update and add, I had similar issue after the 6.5.1 update. All I had to do was re-map the port bindings so that there was no conflict. (In this case the contested port was 443 which is also used by nginx, even though it was not an issue before.) Rebuilt the image and now all is well. TL:DR Check your port mappings and bindings before complaining about stuff not working. Also, support threads FTW./
  2. Any chance you would be able to point me to a solid resource on getting MQTT talking to another docker then?
  3. Thanks for the quick reply. I was actually able to do it much more simply. I went in to CMD then MC and then into the MQTT directory and used ```touch passwords.txt``` to create the file then I edited it and saved and restarted the docker. So, that worked. However, I can not for the life of me get MQTT to actually contol what is happening in Homeassistant. Using MQTTfx, I can see that both the HA docker and the MQTT docker are talking to each other as evidenced by me hitting a switch to activate a device from within HA. The input is shown in MQTT.fx but there is no actual state change for the device I am trying to control. Very odd. By state change, I mean the physical device does not actually respond in any way, ie. turn on/off.
  4. I am also trying to get MQTT working in Homeassistant and can not seem to do it. I have it working perfectly on my Pi3 but in my UNraid docker it refuses to work. Also, since my install is in appdata/mqtt/ I can not run dockersafe new permissions. Which is rough because I also can not see any files inside that directory even though it is shared. If I use MC, I can see everything but I don't know enough to get in and create the new file for passwords in there. Any assistance would be appreciated.
  5. @Squid All went well, thank you again for your time! :thumbsup:
  6. @Squid Will do that now, thank you for your help.
  7. Not to sound like a complete tool but how do I do that and will it nuke all my metadata and other info for my dockers? @Squid
  8. My cache is a single drive and is formatted as btrfs same as in the docs and all my data drives are xfs. I literally have not changed a thing and it was all showing good the day before so I am lost on what could be the issue.
  9. I am also having this issue. I appended the changes you linked above @Squid I would appreciate it if you could take a look at my logs though. Hoping it is nothing serious.... tower-diagnostics-20170911-0813.zip
  10. I just got the same thing when I checked today. Any help would be appreciated as I have not changed anything in my configuration and things have been running well. tower-diagnostics-20170911-0813.zip
  11. I know I am into some serious thread necro here, but I had to post to say, you sir, are my hero. This fixed the issues I was having after a botched install of another docker. Sadly, my backups did not migrate back over as I had hoped , but all else went smooth as silk. Thank you!
  12. OK I got into it via MC and it shows 192.168.1/255.255.255.0 after LAN networks bandwidth? it's a bit hard to read in there.
  13. It won't let me access it. let me try from MC.
  14. This is what I found in the main plexmediaserver.log one
  15. Ill, check now which log is it specifically? There are like 30 different ones in there.