-
Windows Shares, possible NTLM issue
-
Windows Shares, possible NTLM issue
Yes, it is the correct user and domain, and there are no different user/same machine issues. It definitely appears related to NTLMv1, since I just switched to "Send NTLMv2 response only" on one machine and that solved the issue, but creates the issue I can't connect to anything needing NTLMv1 (like my Windows Home Server).
-
bondoo0 started following Hang on reboot, fine on cold boot , Windows Shares, possible NTLM issue , SOLVED - No Web Interface after upgrade and 2 others
-
Windows Shares, possible NTLM issue
I just updated to 6.1.1.0 RC5, and lost access to my private windows shares (public works fine). I tried downgrading back to RC4, and that didn't seem to fix it either with a quick test. When I attempt to access a share with my credentials I get "invalid user/password" message I assume it is perhaps related to either: samba: version 4.16.5 or more likely "SMB: remove NTLMv1 support since removed from Linux kernel" mentioned in the change list, but I have not been able to fix it. I did find a setting "LAN Manager Authentication Level" on the Windows machines, which was set to Send LM & NTLM – use NTLMv2 session security if negotiated, but I'm hesitant to change that to NTLMv2 only since I still have a Windows Home Server (based on Windows Server 2003) that doesn't natively support NTLMv2.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Okay, that makes sense, thanks for looking into this for me, and thanks for all your work on this plugin (and also explains why when I manually restarted nginx I still had to wait 5 minutes or so for the GUI to come up).
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Here are my diagnostics and a screen shots. I wasn't sure if you wanted the UD config page (I believe I left everything at the default) or the page showing the UD tab from main. I have one drive that is used for offline backups, so it isn't typically connected, but is still shown/remembered. unraid-server1-diagnostics-20201116-1320.zip
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Sorry, I should have been clear. I get a timeout page going to the unraid home page (or other unraid pages such as Dashboard, UD, Main, etc). However, I have dockers, such as Plex that publish their own web page outside of unraid, and those pages are available. The only way to get the unraid pages to come back up is to login via SSH, and start nginx, which shows as not running on system boot when I have UD installed, and I believe is what provides the unraid web front end.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
Yes, multiple browsers, multiple PC's
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I'm not clear what the screen shot you are asking for would be. In my case when I have unassigned devices plugin installed, after a reboot, there is no unraid web page to display, and when I telnet in nginx isn't running, I can manually start nginx, and after a couple minutes unraid's web page comes up, and all appears normal, until the next reboot.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
I'm not sure if anyone else has upgraded to 6.9.0 RC 35 with this installed, but it seems to create an issue for the web console (nginx). When I upgraded to RC 35, the console wouldn't come up, and after some trial and error I determine that it was due to something in unassigned devices plugin (I don't have the plus installed if that helps narrow it down). I could get the Web UI to start by restarting nginx, and waiting about 5 minutes. I verified this by re-adding the unassigned devices plugin, and once again the problem showed up, remove the plugin and the problem goes away. Any suggestions would be appreciated. Here is the link (hopefully this comes through) to the thread I started with my diagnostics.zip attached:
-
[Support] Linuxserver.io - Plex Media Server
Doh, I feel stupid, I had tried the plexinc one before and didn't like it, but the template on unraid still existed. Once I picked the correct template, all is good again. Thanks for helping me find the issue. Sent from my SM-G955U using Tapatalk
-
[Support] Linuxserver.io - Plex Media Server
Here is the docker command, I have tried with both latest and plexpass for version Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='PlexMediaServer' --net='br0' --ip='192.168.1.193' --privileged=true -e TZ="America/Denver" -e HOST_OS="unRAID" -e 'PLEX_CLAIM'='claim-bDUEs3yvUDapqqBy8Cnz' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -v '/tmp/':'/transcode':'rw' -v '/mnt/user/':'/data':'rw' -v '/mnt/user/Apps/PlexMediaServer':'/config':'rw' 'plexinc/pms-docker' 0f5bdb8dc802e820c3c8f960f5aedad35923076f84b471563674f4086f041ca7 The command finished successfully Sent from my SM-G955U using Tapatalk
-
[Support] Linuxserver.io - Plex Media Server
Same issue here, info in the post right above yours Sent from my SM-G955U using Tapatalk
-
[Support] Linuxserver.io - Plex Media Server
I'm running into a plex update issue after having to remove/recreate the docker image. I ended up switching the fixed IP address (from .48 to .193). After recreating the docker, everything seems to work (I can play media, plex shows it is configured for remote access, and plex can determine there is a plex update available), but it doesn't update plex when I restart the docker container, and the log is much shorter than it was previously. I'm including the whole log file here to see if that triggers anything, my first thought was the container doesn't have outside access, but I would think that would mean no notification of update, and no remote access, so I'm kind of lost here. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 40-plex-first-run: executing...Plex Media Server first run setup complete[cont-init.d] 40-plex-first-run: exited 0.[cont-init.d] 50-plex-update: executing...[cont-init.d] 50-plex-update: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.Starting Plex Media Server.[cont-finish.d] executing container finish scripts...[cont-finish.d] done.[s6-finish] syncing disks.[s6-finish] sending all processes the TERM signal.[s6-finish] sending all processes the KILL signal and exiting.[s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 40-plex-first-run: executing...[cont-init.d] 40-plex-first-run: exited 0.[cont-init.d] 50-plex-update: executing...[cont-init.d] 50-plex-update: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.Starting Plex Media Server.
-
[Support] Linuxserver.io - Plex Media Server
Found it, it's the advanced view (not advanced settings) accessed by the slider in the top left of the screen, then just update the URL there
-
[Support] Linuxserver.io - Plex Media Server
Edit the container settings, open advanced view and you'll see the field for web ui. Plug the ip in there I don't see that under advanced view, with the latest version of the docker, The only thing there is container path.
bondoo0
Members
-
Joined
-
Last visited