mrbilky
-
Posts
460 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by mrbilky
-
-
Can someone tell me if they see why handbrake cannot see my dvd drive? (Solved!)
-
15 minutes ago, CHBMB said:
Was a fresh pull...... or at least that's what I asked for...
Yep it was its identical or so it appears as the first one I posted think I'll go to the extreme of pulling my 10GB nic is that is the only hardware change made to this and I had plex running on this server without issue several times when I first built it guess I should have left well enough alone but I was trying too many things at once and getting bogged down so I removed all but what I needed at the time the only other change is the updates anyone have the link to older versions namely 6.3.5 that was the version it ran on
-
23 minutes ago, CHBMB said:
Get rid of your plex appdata, remove the container and the image and reinstall. On the FIRST install, post your logs and your docker run command like I have below
docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/movies':'rw' -v '/mnt/user/tv/':'/tv':'rw' -v '/mnt/user/music/':'/music':'rw' -v '/mnt/disks/virtualisation/.appdata/plex-test':'/config':'rw,slave' 'linuxserver/plex'[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] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # preference file found, possibly first startup. # ##################################################### [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[272]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface veth73d18bc.IPv6 with address fe80::b0b3:3ff:feef:8ad4. New relevant interface veth73d18bc.IPv6 for mDNS. Joining mDNS multicast group on interface veth0c26bb0.IPv6 with address fe80::a88a:5cff:fe98:6b73. New relevant interface veth0c26bb0.IPv6 for mDNS. Joining mDNS multicast group on interface veth6e2d851.IPv6 with address fe80::2c7b:85ff:fe87:48d. New relevant interface veth6e2d851.IPv6 for mDNS. Joining mDNS multicast group on interface veth0b7125d.IPv6 with address fe80::801e:31ff:fede:bc8f. New relevant interface veth0b7125d.IPv6 for mDNS. Joining mDNS multicast group on interface vethe473a31.IPv6 with address fe80::f046:5bff:fecd:f333. New relevant interface vethe473a31.IPv6 for mDNS. Joining mDNS multicast group on interface vethc0ba8de.IPv6 with address fe80::1493:67ff:feaf:f9c4. New relevant interface vethc0ba8de.IPv6 for mDNS. Joining mDNS multicast group on interface veth023105f.IPv6 with address fe80::fc7a:3fff:fe08:b9bd. New relevant interface veth023105f.IPv6 for mDNS. Joining mDNS multicast group on interface veth3f99e43.IPv6 with address fe80::3c4c:dff:fe71:c4d7. New relevant interface veth3f99e43.IPv6 for mDNS. Joining mDNS multicast group on interface veth011c810.IPv6 with address fe80::f41b:7eff:fef4:7e16. New relevant interface veth011c810.IPv6 for mDNS. Joining mDNS multicast group on interface veth04bd526.IPv6 with address fe80::1c8a:63ff:fe45:49e7. New relevant interface veth04bd526.IPv6 for mDNS. Joining mDNS multicast group on interface veth16dee29.IPv6 with address fe80::c89b:17ff:fefe:96f0. New relevant interface veth16dee29.IPv6 for mDNS. Joining mDNS multicast group on interface vethe1a3273.IPv6 with address fe80::84e:3aff:fedc:b39a. New relevant interface vethe1a3273.IPv6 for mDNS. Joining mDNS multicast group on interface veth23bb0b2.IPv6 with address fe80::5099:eff:fe51:62eb. New relevant interface veth23bb0b2.IPv6 for mDNS. Joining mDNS multicast group on interface vethe0abaf8.IPv6 with address fe80::4461:79ff:fe8a:8fbd. New relevant interface vethe0abaf8.IPv6 for mDNS. Joining mDNS multicast group on interface veth51892a4.IPv6 with address fe80::60e2:eaff:febd:c4d2. New relevant interface veth51892a4.IPv6 for mDNS. Joining mDNS multicast group on interface veth21785d9.IPv6 with address fe80::6880:a5ff:fe8a:c531. New relevant interface veth21785d9.IPv6 for mDNS. Joining mDNS multicast group on interface veth47495d9.IPv6 with address fe80::742c:dfff:fe01:8c4d. New relevant interface veth47495d9.IPv6 for mDNS. Joining mDNS multicast group on interface veth3e45e33.IPv6 with address fe80::5c5c:2bff:fe15:c63f. New relevant interface veth3e45e33.IPv6 for mDNS. Joining mDNS multicast group on interface veth78c341e.IPv6 with address fe80::14e9:4fff:fed7:5345. New relevant interface veth78c341e.IPv6 for mDNS. Joining mDNS multicast group on interface vethf035633.IPv6 with address fe80::c004:6fff:fe9a:65fe. New relevant interface vethf035633.IPv6 for mDNS. Joining mDNS multicast group on interface vethafd8338.IPv6 with address fe80::ec3b:3aff:fe58:a5ab. New relevant interface vethafd8338.IPv6 for mDNS. Joining mDNS multicast group on interface veth0d2e265.IPv6 with address fe80::9c42:45ff:fed9:679e. New relevant interface veth0d2e265.IPv6 for mDNS. Joining mDNS multicast group on interface vethe6803dd.IPv6 with address fe80::c00b:5ff:fe22:a48a. New relevant interface vethe6803dd.IPv6 for mDNS. Joining mDNS multicast group on interface veth241b8af.IPv6 with address fe80::906d:87ff:feba:a655. New relevant interface veth241b8af.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:aeff:fe47:1dd2. New relevant interface docker0.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::5c97:34ff:fe2d:f7b9. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.1. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ae1f:6bff:fe1b:4d76. New relevant interface eth0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for fe80::b0b3:3ff:feef:8ad4 on veth73d18bc.*. Registering new address record for fe80::a88a:5cff:fe98:6b73 on veth0c26bb0.*. Registering new address record for fe80::2c7b:85ff:fe87:48d on veth6e2d851.*. Registering new address record for fe80::801e:31ff:fede:bc8f on veth0b7125d.*. Registering new address record for fe80::f046:5bff:fecd:f333 on vethe473a31.*. Registering new address record for fe80::1493:67ff:feaf:f9c4 on vethc0ba8de.*. Registering new address record for fe80::fc7a:3fff:fe08:b9bd on veth023105f.*. Registering new address record for fe80::3c4c:dff:fe71:c4d7 on veth3f99e43.*. Registering new address record for fe80::f41b:7eff:fef4:7e16 on veth011c810.*. Registering new address record for fe80::1c8a:63ff:fe45:49e7 on veth04bd526.*. Registering new address record for fe80::c89b:17ff:fefe:96f0 on veth16dee29.*. Registering new address record for fe80::84e:3aff:fedc:b39a on vethe1a3273.*. Registering new address record for fe80::5099:eff:fe51:62eb on veth23bb0b2.*. Registering new address record for fe80::4461:79ff:fe8a:8fbd on vethe0abaf8.*. Registering new address record for fe80::60e2:eaff:febd:c4d2 on veth51892a4.*. Registering new address record for fe80::6880:a5ff:fe8a:c531 on veth21785d9.*. Registering new address record for fe80::742c:dfff:fe01:8c4d on veth47495d9.*. Registering new address record for fe80::5c5c:2bff:fe15:c63f on veth3e45e33.*. Registering new address record for fe80::14e9:4fff:fed7:5345 on veth78c341e.*. Registering new address record for fe80::c004:6fff:fe9a:65fe on vethf035633.*. Registering new address record for fe80::ec3b:3aff:fe58:a5ab on vethafd8338.*. Registering new address record for fe80::9c42:45ff:fed9:679e on veth0d2e265.*. Registering new address record for fe80::c00b:5ff:fe22:a48a on vethe6803dd.*. Registering new address record for fe80::906d:87ff:feba:a655 on veth241b8af.*. Registering new address record for fe80::42:aeff:fe47:1dd2 on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for fe80::5c97:34ff:fe2d:f7b9 on br0.*. Registering new address record for 192.168.0.1 on br0.IPv4. Registering new address record for fe80::ae1f:6bff:fe1b:4d76 on eth0.*.
Here it is but I had to stop the docker or it would just keep posting "Starting Plex Media Server."
[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] 10-adduser: executing...
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...
#####################################################
# Login via the webui at http://<ip>:32400/web #
# and restart the docker, because there was no #
# preference file found, possibly first startup. #
#####################################################
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
Starting dbus-daemon
[services.d] done.
dbus[271]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Starting Plex Media Server.
Starting Avahi daemon
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface veth51be318.IPv6 with address fe80::204e:f2ff:febe:a047.
New relevant interface veth51be318.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:40ff:fe25:e4ec.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth2.IPv4 with address 192.168.51.2.
New relevant interface eth2.IPv4 for mDNS.
Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.50.2.
New relevant interface eth1.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ec4:7aff:fe81:28d3.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.154.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::204e:f2ff:febe:a047 on veth51be318.*.
Registering new address record for fe80::42:40ff:fe25:e4ec on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 192.168.51.2 on eth2.IPv4.
Registering new address record for 192.168.50.2 on eth1.IPv4.
Registering new address record for fe80::ec4:7aff:fe81:28d3 on eth0.*.
Registering new address record for 192.168.1.154 on eth0.IPv4.
Starting Plex Media Server.
Server startup complete. Host name is homeNAS.local. Local service cookie is 7152946.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface veth51be318.IPv6 with address fe80::204e:f2ff:febe:a047.
Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:40ff:fe25:e4ec.
Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Leaving mDNS multicast group on interface eth2.IPv4 with address 192.168.51.2.
Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.50.2.
Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::ec4:7aff:fe81:28d3.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.154.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
avahi-daemon 0.6.32-rc exiting.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting. -
-
1 hour ago, CHBMB said:
Looks like your getting IP addresses from 3 different ethernet adapters. What's the config of your Unraid server network settings?
Yeah I did see that that was why I was wondering if my 10GB nic was part of the issue here's the diags:
-
Just now, Squid said:
Yup. And now someone who uses/knows Plex can try and help you out
Thanks for the honest attempt
-
2 minutes ago, Squid said:
Nope. Plex runs in host mode so there's no ports per se to show.
The logs from the container (click on the uptime when its running from the docker page) might help.
is this the log you're suggesting?
-
49 minutes ago, trurl said:
Where are your volume mappings? There should be at least 2 Paths above the Container Variables. Have you read the Docker FAQ? If you don't understand volume mappings you will always be in the dark about how to make dockers work.
Maybe just start from a new linuxservio/plex install from Community Applications. I'm pretty sure the default template you will get that way will at least have some Paths to work with and we can go from there.
Thanks for the input I think I'm doing it right a couple months ago it worked just fine, can adding a 10GB nic interfere cause thats the only variable thats changed. I don't see a deployed host port for plex could that be a problem?
-
Can someone point me to a good tutorial for plex I'm on the latest stable version of unRAID and for some reason I can't get any plex docker to work, I had it installed in the past but now I'm ready to set it up for the family and now for the life of me can"t figure out how I did it? I'm not well versed in linux and the command prompt so either something has changed with the docker or I followed some tutorial that I can't seem to find on the net All attempts to start up plex has resulted in:
Strange thing is that I can access the server by just the ip just plex won't open I'm quite sure I'm missing allot of required entries here but this is where I'm at:
-
Quick question I have this working but do I need a vpn for security is this secure on its own?
-
7 minutes ago, DJRon said:
I installed this after my 3rd phone call to my provider in as many months about getting speeds as slow as 1.6 Mb/s when I am paying for 300. They called a few days later to "follow up" I told them then that I have loaded the program on my home server and have it monitoring my speeds throughout the day. Since then I have noticed consistently higher speeds. Still not always 300; but you can see a definite spike after that last "follow up" phone call.
That's great nice to see them getting caught
I guess they figure that the lay person will never know!
-
1 hour ago, wgstarks said:
Are you using a bonded network?
I like DuckDNS docker.
According to my settings yes it is set to bonding, should I change that? And if bridging isn't needed that is on as well from what I've read those 2 settings seem to be for VM use for which at this time I have no interest in if that helps
-
So I'm determined to make this work
my first question is I pulled down the docker and when its set to host it will not connect, if I set it to bridge it will and I can get to the setup for openVPN I did not change anything else in the setup screen, where do I find what I need to change so host will open or does it matter?
I am willing to pay for a dns account how is dyndns any opinions?
Idon't see anything pertinent in the syslog but I posted it anyway
-
On 6/12/2016 at 9:10 PM, archedraft said:
Honorable mention for the above banner, fits my all red theme thanks for the banner!
-
1
-
-
On 8/9/2017 at 5:43 PM, Squid said:
You're living the dream.
I've got the garage only for tool storage, and my office I have to share with our freezer and furnace.
When the last of the kids moved out I started making plans to relocate the office to one of the extra bedrooms and was told in no uncertain terms "No".
HaHa I had the same thought but low and behold as they moved out my wife broke out the tools and disassembled the beds so they had nowhere to sleep should they consider coming back, but I still didn't get my office I share my space with the chest freezer and several clothes storage closets
-
58 minutes ago, trurl said:
mc (Midnight Commander) is a built-in file manager you access from the command prompt. Google it.
Thanks for the advice I booted the server in gui mode and found mc seems clear enough will mess with it tomorrow also see that I can install it on my pc is there a benefit to running it from the server over my pc? Gonna start reading up command prompt programming looks like its gonna be needed more with unRAID
-
15 minutes ago, Squid said:
IIRC I was helping buddy earlier, and permissions show as -rw-r--r-- nobody:users which means that Plex itself can write but over smb Windows won't be able to.
Not entirely unexpected with a docker application, and the solution with any container is to access the appdata via the command prompt running as root.
Unfortunately that's where I fail miserably no experience with command prompt and command speak I'm outta my element there, will keep reading and looking
-
15 minutes ago, CHBMB said:
That's a permissions issue with Windows and Unraid smb shares, nothing to do with this container. Can't help you as I'm not a Windows user.
The crazy thing is the binhex version did allow me to install into the plugin folder from my desktop from web sourced files but I removed it because that version was not allowing the web tools plugin to open in my browser so it isn't windows in my opinion there must be some other source of permission holding me back and I did not change anything in unRAID as far as smb permissions to allow it to work I simply loaded a different docker version?
-
What needs to be added to this version in order to install plugins into the plugin folder from the net I have tried every version of plex and for some reason if I try to add plugins from the net my plugin folder has a an error preventing me from doing so there must be something I'm missing, I've tried all options in sharing settings a matter of fact it won't let me change any sharing rights in windows
-
1 hour ago, Hoopster said:
You want something like the OpenVPN Access Server docker. Search for openvpn in community applications. Most use the Linuxserver.io version, but, there are others. Its easy to setup. You'll want a dynamic DNS service for your unRAID server as well if you do not have a static IP from your ISP. I use No-IP (free) as it is supported natively by my router as is DynDNS, but, there are others. Configure OpenVPN Access Server on unRAID with your DDNS name and the IP address of your unRAID server. On your router, forward UDP/TCP port 1194 (the default) or another port you have configured for OpenVPN to the IP address of your unRAID server. Download from the OpenVPN Access Server a user-locked profile for the clients you want to be able to access your server and you are set. Now your clients can access your unRAID server securely over the Internet by DDNS server name on port 1194 (or other port you chose).
Got it thanks will give it a go in a few days trying to tighten up any loose ends I have before starting to use the NAS
-
14 minutes ago, 1812 said:
Best practice to access outside the network is run a vpn and not use port forwarding.
Aside from that, if port forwarding is the only option, forward only the single port that plex needs to the server.
Someone else can correct me if I'm wrong, but I believe 6.4 will have the ability to assign individual ip addresses to docker containers, meaning that plex can reside on its own IP on the network, isolated from the server. So then if there was a problem, someone can only go after that single port to the IP of the docker and not hit the server.
Well that sure would be nice I'm obviously uncomfortable with the idea of this being accessible as one could imagine, will change settings on the router and just deal with it until there's a workaround I have no media to view yet anyway
Just going through all the motions before going live with using this NAS daily. Oh and when you say VPN I have ipvanish on my pc is there a simple way to set that up on the NAS?
-
5 minutes ago, 1812 said:
this seems to originate from Russia:
2-62-156-89-bbc-dynamic.kuzbass.netSo, go look into locking down your router.
HaHa I swear there's no collusion here I haven't talked to the Russians and have no business ties with them
Seriously I'll go look into my router settings as I did fool with port forwarding for plex is there a work around that is out there or just live with it only being inside the home network environment?
-
15 minutes ago, 1812 said:
:
That means tell us how you have the server connected: to a router? Directly to a cable modem? Ports forwarded? Can't tell you anything without knowing how you've set it up.
--
post the entire diagnostics zip file.
My setup is a Verizon fios wifi router connected by ethernet cable heres the router setup info:
homeNAS
192.168.1.151
HTTP TCP Any -> 80Active
Ok well it's not a zip file but I'll post it anyway
-
24 minutes ago, 1812 said:
If your server is sitting on the open internet, stop that for starters.
also post your diagnostics and describe your networking setup.
How do I find out if I'm on the open internet the only thing that I set up over defaults would be plex and it is set to allow remote access
I did the diagnostics thing which particular file would be helpful, the one that looks like it has the most is syslog.txt but its like a mile long is that the one?
I guess they figure that the lay person will never know!
Just going through all the motions before going live with using this NAS daily. Oh and when you say VPN I have ipvanish on my pc is there a simple way to set that up on the NAS?
[Support] Djoss - HandBrake
in Docker Containers
Posted · Edited by mrbilky
Sounds reasonable enough where would that be located I searched in Krusader but didn't get a hit?