bondoo0
-
Posts
161 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bondoo0
-
-
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).
-
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.
-
24 minutes ago, dlandon said:
I see this in the log:
Nov 16 13:14:06 unraid-server1 unassigned.devices: Mounting 'Auto Mount' Remote Shares... ... Nov 16 13:19:36 unraid-server1 unassigned.devices: Cannot 'Auto Mount' Remote Shares. Network not available!The startup check for the network to be available before auto mounting remote shares is taking over 5 minutes to determine the network is not available. There is an issue on the network available script that causes this lengthy time, and because it is in an Unraid startup event, the Unraid GUI will not be available until it completes the network check. I have a fix applied, but it is not released yet.
When you reboot Unraid, the GUI will eventually come up after the 5 minute delay caused by this issue.
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).
-
20 hours ago, dlandon said:
Post a screen shot of the UD page when it is working. Also post your diagnostics.
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.
.thumb.png.c341c9c09ce8647095b0de174f3d35e8.png)
.thumb.png.05406743e9aa76a6db6b702bcdf64127.png)
-
12 minutes ago, dlandon said:
You said you could see Dockers. What webpage does not show? Just UD? Do you get a blank screen?
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.
-
12 minutes ago, trurl said:
Have you tried other browsers?
Yes, multiple browsers, multiple PC's
-
14 hours ago, dlandon said:
Can you post a screen shot so we can see what you are talking about.
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.
-
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:
-
So the plugin causing this for me appears to be unassigned devices, once I removed that the Web UI is back to normal function on boot.
-
I'll give that a try, I guess I should be clear (after looking at the boot menu for the first time in ???). When I say GUI, I am actually referring to the Web UI, not the GUI option from the boot menu.
I tried the Safe mode with no plugins, and the GUI loads, so it looks like I have an issue with a plugin
. Now to determine which one...
-
I have not tried safe mode (keyboard issue on the server doesn't allow me to select options, so may need a new keyboard, although it works after bootup?, just not on the selection screen). I have discovered that on bootup the nginx service reports that it isn't running if I telnet in. If I restart nginx using the rc.d script it reports running, and gives me a 500 server error but if run nginx a couple of times (which comes up with port already in use errors) the GUI does seem to come up on either RC 30 or RC 35.
-
I just tried to upgrade from RC 30 to RC 35. When I did, I have no GUI, but it appears everything else is up and running (can view my dockers, telnet, and access shares). I reverted to RC 30, and I still had no GUI, but I was able to restart NGINX from the command line in /etc/rc.d. So I reinstalled RC 35, and same issue, no GUI. I tried starting the GUI from the command line, and could only get a 500 error. I didn't see anything in the syslog that stood out to me, so I'm hoping someone else will have a suggestion.
I have attached the diagnostics from the first failed install of RC 35.
-
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.
You are not using our container [emoji33]
Sent from my SM-G955U using Tapatalk
-
Here is the docker command, I have tried with both latest and plexpass for version
Everything looks normal. Post the docker run command.
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
-
Same issue here, info in the post right above yoursAnyone else having issues with this not updating to the latest plexpass version (Version 1.12.3.4973)? I have tried restarting the docker etc and still no luck. Looks like a newer version has been available for days now. Thanks!
Sent from my SM-G955U using Tapatalk
-
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. -
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
-
1 minute ago, aptalca said:54 minutes ago, bondoo0 said:The link is going to the unraid IP, I would be surprised if unraid knows which IP goes to the container, since I think with macvlan there is no communication between the host and docker, but I could be wrong. I'm actually on 6.3.5, so not one of the RC's.
I'm thinking it is something with the docker template (maybe), since the only system change was getting the updated version of the docker. Here's a link about where it used to be, which is under docker config advanced settings, Either way, it's not a big issue, since the docker works fine, Just annoying when I try to use the built in link.
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.
-
19 minutes ago, saarg said:
If the link is going to the unraid IP when you click it, you should post this in the 6.4 forum (I assume you use the RC?)
I don't remember now if unraid knows which IP is given to the the container or not, but it might be something @bonienl needs to impement.
The link is going to the unraid IP, I would be surprised if unraid knows which IP goes to the container, since I think with macvlan there is no communication between the host and docker, but I could be wrong. I'm actually on 6.3.5, so not one of the RC's.
I'm thinking it is something with the docker template (maybe), since the only system change was getting the updated version of the docker. Here's a link about where it used to be, which is under docker config advanced settings, Either way, it's not a big issue, since the docker works fine, Just annoying when I try to use the built in link.
-
1 minute ago, CHBMB said:
Is this referring to macvlan networking? Hopefully someone else will chip in, but not something we can really support.
Sent from my LG-H815 using Tapatalk
It is macvlan. Basically the change is allowing a different URL when webui link is clicked, which I thought was configured in the setup options of the plex docker, but maybe it was somewhere else, just odd that it was working, and now stopped, and not that big of a deal.
-
Having a problem with the "webui link" from dashboard or docker page. I have my network set to none, and my docker is assigned an IP ending in 48 (unraid is 198). I had this working with a config setting until the last update or 2, but now I don't see anywhere to set this.
-
I actually found a way that ended up working (at least for me) without having to change the vm's settings (other than increasing the size in the unraid GUI.
I installed parted to expand the usage to the new size (for some reason I had to display the partition info, then "fix" it to see the whole space available, instead of just being able to use fdisk), then used fdisk (deleted existing partition, created a new one), then since it's an LVM partition, I then used pvresize/lvextend to increase the size of the lvm partition's physical and logical volumes, and finally used resize2fs to expand the file system to the newly available space.
So in the end I was able to expand the size from 15G to 25G with no data loss (and without having to rebuild my plex db).
-
I need to expand the size of my ubuntu vdisk. I saw a few posts about expanding the size in the GUI, and I've been able to do that, but I'm not sure how to make the space available (saw a mention of booting to GRUB). I tried going into GRUB, going to the command line and using gparted, but it won't start in the NoVNC session (get a no display error), so I was hoping someone would be able to guide me into making more space available to my VM. I'm running Unraid 6.2, and Ubuntu Server 16.04 LTS if that matters.
-
I'm getting the tput: unknown terminal "screen" error with the beta version. The non-beta version appears to work correctly. I did verify screen is setup/working when I login via SSH as root. Any suggestions?
Which version of unRAID you're using?
6.1.9
.png.271bc963621639fa11d982ad5b41dbee.png)
.png.6faf2a5568ee55ee4eb2a25fe78c97a4.png)
. Now to determine which one...
Windows Shares, possible NTLM issue
in General Support
Posted
Here is the output: