erikm101

NM. I found my solution. It was as follows. Credit to user "trurl" from this thread. Go to Windows Control Panel, Credential Manager, and delete any Unraid credentials so they can be renegotiated. Then, be sure to try to access the private share before trying to access any other share. With Windows, you only get one login per network resource and you must make sure that one login is the one needed for the private share. Windows won't use another login even if it prompts you. Edit: I should note that I did have to create a new windows credential for accessing the shares. In that credential, the only way I could access the shares with full permissions (that is, be able to write) was to incorporate the workgroup (as set in SMB Settings) to the user name. Example: workgroup\username

I am experiencing the same issues. UnRaid shares inaccessible from Win11 machines. All was working until some update in late September/early November. Has anyone solved this yet?

This suggestion did not work for me.... I am having similar issues as the OP. I can access all of my shares from any Win10 machine, but am unable to from Win11. Interesting to note is that I was previously able to access my shares from Win11 - lost that ability within the last couple of weeks. Nothing changed on the UnRaid side recently - though several windows updates have processed in the last few weeks. UnRaid 6.10.1

While I never did find any error entries of fatal or corruption, I was not able to resolve even after trying a db restore from backup (manual method). In the end, I had to remove the container, manually delete the appdata folder for PlexPass and then clean re-install the container. Plex is now happily rescanning my libraries and should hopefully be up and streaming again shortly. Thanks @binhex for pointing me to the support FAQ on github, that was helpful.

Thanks. I reviewed the logs and found no corruption or fatal entries. I did find a few error relating to parsing xml. Please see below. The last lines for parsing device schema are referencing an NVidia ShieldTV device. I changed the IP to read x.x.x.x. This series of errors repeats several times. Line 20475: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: Entity: line 1: Line 20476: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: parser Line 20477: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: error : Line 20477: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: error : Line 20478: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: Start tag expected, '<' not found Line 20479: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: status=ok Line 20480: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: ^ Line 20481: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing content. Line 20481: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing content. Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file. Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file. Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file. Line 20483: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - SSDP: Error parsing device schema for http://x.x.x.x:9080 Line 20483: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - SSDP: Error parsing device schema for http://x.x.x.x:9080

Hello Binhex, Thanks for your many excellent docker apps! Today I experienced an issue with plexpass. I noticed that my clients could not connect and that I could not launch the webUI either. Checking the logs, there were some errors reported. I checked for docker updates and found none available. I then updated UnRaid to 6.10.1. Still no joy. I have tried restarting the docker and UnRaid several times with no change. Below is the log output from the latest restart of the docker. Please let me know if you (or anyone else in the community reading this) knows what this error means and how to correct it. One note possibly of interest. The following line was seen in every log after a restart with the same PID 8 reported. Not sure if that is relevant. 2022-05-24 20:30:17,034 INFO reaped unknown pid 8 (exit status 0) Thanks for your assistance. It is truly appreciated. 2022-05-24 20:30:14.855153 [info] Host is running unRAID 2022-05-24 20:30:14.902874 [info] System information Linux UR-Lord 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 GNU/Linux 2022-05-24 20:30:14.960139 [info] OS_ARCH defined as 'x86-64' 2022-05-24 20:30:15.014212 [info] PUID defined as '0' 2022-05-24 20:30:15.081963 [info] PGID defined as '0' 2022-05-24 20:30:15.154679 [info] UMASK defined as '000' 2022-05-24 20:30:15.206388 [info] Permissions already set for '/config' 2022-05-24 20:30:15.269332 [info] Deleting files in /tmp (non recursive)... 2022-05-24 20:30:15.324308 [info] TRANS_DIR defined as '/config/transcode' 2022-05-24 20:30:15.383938 [info] Starting Supervisor... 2022-05-24 20:30:16,022 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2022-05-24 20:30:16,022 INFO Set uid to user 0 succeeded 2022-05-24 20:30:16,028 INFO supervisord started with pid 7 2022-05-24 20:30:17,031 INFO spawned: 'plexmediaserver' with pid 64 2022-05-24 20:30:17,033 INFO spawned: 'shutdown-script' with pid 65 2022-05-24 20:30:17,034 INFO reaped unknown pid 8 (exit status 0) 2022-05-24 20:30:17,308 DEBG 'plexmediaserver' stderr output: Plex Media Server is already running. Will not start... 2022-05-24 20:30:17,308 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-05-24 20:30:17,310 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282496 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)> 2022-05-24 20:30:17,310 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23110440282448 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)> 2022-05-24 20:30:17,310 INFO exited: plexmediaserver (exit status 1; not expected) 2022-05-24 20:30:17,311 DEBG received SIGCHLD indicating a child quit 2022-05-24 20:30:18,313 INFO spawned: 'plexmediaserver' with pid 70 2022-05-24 20:30:18,353 DEBG 'plexmediaserver' stderr output: Plex Media Server is already running. Will not start... 2022-05-24 20:30:18,356 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282736 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)> 2022-05-24 20:30:18,356 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440282784 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)> 2022-05-24 20:30:18,357 INFO exited: plexmediaserver (exit status 1; not expected) 2022-05-24 20:30:18,357 DEBG received SIGCHLD indicating a child quit 2022-05-24 20:30:20,361 INFO spawned: 'plexmediaserver' with pid 74 2022-05-24 20:30:20,401 DEBG 'plexmediaserver' stderr output: Plex Media Server is already running. Will not start... 2022-05-24 20:30:20,403 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282544 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)> 2022-05-24 20:30:20,403 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440274912 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)> 2022-05-24 20:30:20,403 INFO exited: plexmediaserver (exit status 1; not expected) 2022-05-24 20:30:20,403 DEBG received SIGCHLD indicating a child quit 2022-05-24 20:30:23,408 INFO spawned: 'plexmediaserver' with pid 78 2022-05-24 20:30:23,447 DEBG 'plexmediaserver' stderr output: Plex Media Server is already running. Will not start... 2022-05-24 20:30:23,449 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282640 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)> 2022-05-24 20:30:23,449 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440282448 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)> 2022-05-24 20:30:23,449 INFO exited: plexmediaserver (exit status 1; not expected) 2022-05-24 20:30:23,450 DEBG received SIGCHLD indicating a child quit 2022-05-24 20:30:24,451 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

I tired that, but did not find the new path available. But it turns out this is me being dumb....I never restarted the docker!! SMH at myself. Thanks trurl.

Hello. I love your dockers! Thanks for your time in creating and maintaining them. I want to add my photos and my music to my PMS, however these files are currently stored in completely different folder structures on my server. SHort of moving those files to a common media folder, is there a way I can add additional media paths to the docker so I can add these libraries to Plex?

I see, didn't realize that was a separate thing. Thanks for the info.

@sturgismike I totally disabled all aspects of BitDefender but still have same issue. I can confirm it is not CA, since I tried from a different machine with different AV and it acted as expected. Which particular settings in BD did you change, just for clarity?

Sorry if this is covered elsewhere in the thread. CA auto updated sometime in the last few weeks and I now find that when I install a new docker I don't see the progress. The browser (FF) simply spins in "loading page" mode and does not show the details of the package pulls and install until it either completes or fails. Is this by design? Is there a setting somewhere to change back to old behavior? I really liked watching it as it progressed vs sitting there wondering what is happening.

Thanks a lot @itimpi!! That did the trick.

Thanks. virbro is the only option I have available in the setup page. Maybe I'm misunderstanding where the network change would need to be applied?

@itimpi

Ah, I see. It is setup as virbr0. I left that at default, which is why I didn't remember the setting

@itimpi I'm not sure I understand the question. I don't recall any settings specifically related to network when I set it up.

Hello,' Apologies in advance for n00b questions. I installed a VM with Ubuntu Server 18.04 LTS. I have properly (I think) edited the network /yaml file. But I am unable to ping this VM, neither can I ping from the VM to anything else. Can't SSH into it, though the VNC seems to be working fine. Netplan settings are applied. Any help getting this VM on my network properly would be greatly appreciated. An ifconfig reveals what appears to be appropriate settings: My Unraid server is at 10.0.1.201. My router is at 10.0.1.1. There are no conflicting IPs on this network. Net config file looks like so:

Hello. Just completed my first cycle of preclear on two drives. Results file attached. This is my first build, still in preproduction config/testing, first two drives that will be added to the array. While both drives precelared successfully with no reallocations, I am a little concerned over the apparent power loss to the drives 7 times. Both drive's results show 7 start/stops, 7 power cycles and 7 power off retracts. Both drives are powered through a single SATA power cable from the Seasonic modular PS. The only draws on the PS are the two drives and the mobo/cpu. BTW, I am aware of the high temps on both drives. I had disconnected the front intake fan for noise purposes and to see how the temps fared. I stupidly started the preclear without reconnecting the fan and was 12+ hours in when I realized my mistake. I went ahead and let the preclear run its cycle without the fan. I watched it pretty closely during the warmer parts of the day and saw temps peak at 42/43C (sda/sdb). Front fan is now back in and idle temps are back to around 27C and falling, so I the feel heat issue is resolved, but wonder if the heat had anything to do with the power downs. Any insight on the power downs (or any other standout items in the results) would be greatly appreciated. I am now starting cycle #2 on both drives. I have also attached a syslog from about 24 hours ago during the write process. I shut down the server to reinstall the front fan and do not have any log data after the attached (again stupid, but I hope not to make these mistakes again). TIA, erik preclear_results_6-5-11_cycle1.txt syslog.txt.html.zip