As it says.
I have the Emby-Stable plugin running in a jail on Core 13.0-U6
It doesn’t auto-start.
My other jails and plugins do, just not this one.
Plugin is marked boot:
Jail is set to auto start:
How can I track this down?
Well, sorry for being a broken record, but the answer is to not use plugins, but create a jail and install emby using pkg.
1 Like
Or even better, use Jellyfin instead!
Except that is broken now as well.
Also, if you really insist on getting Emby working, make sure that there’s an init script in /usr/local/etc/rc.d in the jail which will start the server when the jail boots.
I never used the plugin but installed it from the original repo that “Thefrank” created.
You didn’t install via pkg install jellyfin?
My bad. Jellyfin works. I had forgotten about the mlock setting.
I’m good with Emby, no need to switch. This is just a minor annoyance.
You really think installing from pkg will do it?
Absolutely.
Create a jail, then enter these commands. The first one needs to be run outside the jail
iocage set allow_mlock=yes jailname
Then these from inside the jail
pkg update
pkg install emby-server
sysrc emby_server_enable=yes
service emby-server start
and just restore via the Emby gui?
Yes if you have the backup.
Don’t delete the plugin until you know it is working.
Also don’t forget to set the block setting.
iocage set allow_mlock=yes jailname
ha ha I started trying this- I created a blank jail, called ‘Emby’, then set the block setting.
Then, for fun, I rebooted - and my NEW jail failed to start, whereas my Emby_Stable jail started automaticaly - for the first time in 2 years.
I wonder if this is a Jail issue, not a plugin issue?
Is the auto start box ticked?
yes. It’s strange.
And I assume the IPs are different?
Are you using a VNET jail?
yes, and yes.
I think this is just some startup something-not-ready
I tried enabling Netwait, but no change.
I think I just need to accept it, and manually start it every time 
You can start it manually though, can’t you?