Townsey 1 Posted December 8, 2018 Posted December 8, 2018 (edited) Hi @Luke and @makarai Ok an update to my problem earlier. I have updated (a full clean install) of FreeNas to the release version of 11.2. Installed Emby as per instructions an all is well and Fanart etc is downloaded fine. Subtitles is another issue and it looks like Denmark is blocking downloads from opensubtitles.org You can connect view and list etc but when you try to download direct it is blocked. So not an Emby issue it looks like our government does not think its legal in their eyes. So thanks for your help and advice Emby works fine except for the subtitles as described above. Have a good weekend. Edited December 8, 2018 by Townsey 1
Luke 42077 Posted December 8, 2018 Author Posted December 8, 2018 Interesting info, thanks for the feedback !
makarai 109 Posted December 8, 2018 Posted December 8, 2018 Hi @Luke and @makarai Ok an update to my problem earlier. I have updated (a full clean install) of FreeNas to the release version of 11.2. Installed Emby as per instructions an all is well and Fanart etc is downloaded fine. Subtitles is another issue and it looks like Denmark is blocking downloads from opensubtitles.org You can connect view and list etc but when you try to download direct it is blocked. So not an Emby issue it looks like our government does not think its legal in their eyes. So thanks for your help and advice Emby works fine except for the subtitles as described above. Have a good weekend. The danish goverment blocking the download from a specific site ? u sure ?
Townsey 1 Posted December 8, 2018 Posted December 8, 2018 (edited) The danish goverment blocking the download from a specific site ? u sure ? Yup works fine if you hide, not going to do that for that for Emby Edited December 8, 2018 by Townsey
Eddie 12 Posted December 8, 2018 Posted December 8, 2018 Where do the new packages for freenas 11.2 come from.... are they being maintained along with all the other platforms or do you have to do extra work to get it to work on freenas 11.2 like it was with 11.1 and before
makarai 109 Posted December 8, 2018 Posted December 8, 2018 (edited) Where do the new packages for freenas 11.2 come from.... are they being maintained along with all the other platforms or do you have to do extra work to get it to work on freenas 11.2 like it was with 11.1 and before The Plugin part from freenas is not maintained. If you like to check whats up with emby you should check this https://github.com/MediaBrowser/Emby.Releases/releases If you want to install the recent version withing the iocage system (will be displayed in the gui) just try this cd /tmp wget https://raw.githubusercontent.com/ma-karai/iocage-plugin-emby/beta/emby-server-beta.json iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server-beta.json --branch 'master' It'll install the latest version of emby to the stable freenas 11.2 (stable) in under 3 minutes Edited April 26, 2019 by makarai
Eddie 12 Posted December 8, 2018 Posted December 8, 2018 Ty for the reply And who is maintaining this software? Is this official emby team or another person donating time for the project?
Luke 42077 Posted December 8, 2018 Author Posted December 8, 2018 Ty for the reply And who is maintaining this software? Is this official emby team or another person donating time for the project? I would instead use the instructions in the first post. It is officially maintained by us and will give you the latest stable release, rather than a beta. Following the Emby Server 3.6 stable release, we will look to get the freenas catalog updated and take over ownership of it. Thanks !
Luke 42077 Posted December 8, 2018 Author Posted December 8, 2018 @@makarai, just to make sure users get the right package that they're looking for, I would suggest only steering them towards your beta packages once we know they actually want the beta server. Most probably just want stable and they're not sure how to install it right now. Thanks !
someperson 3 Posted December 9, 2018 Posted December 9, 2018 (edited) I've had Emby installed from the rather old Emby 3.3.1.0 plugin included with FreeNAS 11.1 for a while, and finally got around to upgrading everything today. I used the Backup plugin to create a backup of Emby's configuration, upgraded FreeNAS to 11.2, and tried to use the steps in the first post to get a jail set up with the newest version of Emby. I got the Backup plugin installed on this new Emby instance, but there's a problem: the page to restore the backup is failing to load properly. I just get a never-ending spinny wheel, where there should be options to select what I want to restore. This happens in all browsers, and I don't think it's a problem with the backup itself because the restore page loads fine on my old Emby instance (I've kept it around for now, just in case). What should I do? Edited December 9, 2018 by someperson
Luke 42077 Posted December 9, 2018 Author Posted December 9, 2018 How did you install the backup plugin?
someperson 3 Posted December 9, 2018 Posted December 9, 2018 How did you install the backup plugin? In the new Emby instance? From the Catalog.
Luke 42077 Posted December 9, 2018 Author Posted December 9, 2018 Ok, can you check the browser debug console, does it show any errors?
someperson 3 Posted December 9, 2018 Posted December 9, 2018 Ok, can you check the browser debug console, does it show any errors? It does: Requesting url without automatic networking: http://192.168.1.189:8096/emby/MBBackup/Backups VM322:26 (2) [{…}, {…}] VM322:67 Uncaught (in promise) TypeError: Cannot read property 'length' of undefined at Object.renderUserData (<anonymous>:67:55) at <anonymous>:45:47 renderUserData @ VM322:67 (anonymous) @ VM322:45 Promise.then (async) load @ VM322:25 (anonymous) @ VM322:7 dispatch @ jquery.slim.min.js?v=3.5.3.0:2 v.handle @ jquery.slim.min.js?v=3.5.3.0:2 onViewChange @ viewmanager.js?v=3.5.3.0:1 (anonymous) @ viewmanager.js?v=3.5.3.0:1 Promise.then (async) ViewManager.loadView @ viewmanager.js?v=3.5.3.0:1 loadContent @ router.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 execCb @ alameda.js?v=3.5.3.0:1 defineModule @ alameda.js?v=3.5.3.0:1 depFinished @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 Promise.then (async) waitForDep @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 main @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 Promise.then (async) req @ alameda.js?v=3.5.3.0:1 loadContentUrl @ router.js?v=3.5.3.0:1 onNewViewNeeded @ router.js?v=3.5.3.0:1 sendRouteToViewManager @ router.js?v=3.5.3.0:1 onInitComplete @ router.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 execCb @ alameda.js?v=3.5.3.0:1 defineModule @ alameda.js?v=3.5.3.0:1 main @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 Promise.then (async) req @ alameda.js?v=3.5.3.0:1 initRoute @ router.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 Promise.then (async) authenticate @ router.js?v=3.5.3.0:1 handleRoute @ router.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 (anonymous) @ page.js?v=3.5.3.0:1 nextEnter @ page.js?v=3.5.3.0:1 nextExit @ page.js?v=3.5.3.0:1 page.dispatch @ page.js?v=3.5.3.0:1 page.show @ page.js?v=3.5.3.0:1 (anonymous) @ router.js?v=3.5.3.0:1 show @ router.js?v=3.5.3.0:1 (anonymous) @ site.js?v=3.5.3.0:1 execCb @ alameda.js?v=3.5.3.0:1 defineModule @ alameda.js?v=3.5.3.0:1 depFinished @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 Promise.then (async) waitForDep @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 main @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 Promise.then (async) req @ alameda.js?v=3.5.3.0:1 (anonymous) @ site.js?v=3.5.3.0:1 navigate @ site.js?v=3.5.3.0:1 onclick @ index.html?start=wizard:1 datetime.js?v=3.5.3.0:1 Uncaught (in promise) TypeError: Cannot read property 'match' of undefined at Object.parseISO8601Date (datetime.js?v=3.5.3.0:1) at <anonymous>:31:83 at Object.execCb (alameda.js?v=3.5.3.0:1) at defineModule (alameda.js?v=3.5.3.0:1) at Object.depFinished (alameda.js?v=3.5.3.0:1) at alameda.js?v=3.5.3.0:1 parseISO8601Date @ datetime.js?v=3.5.3.0:1 (anonymous) @ VM322:31 execCb @ alameda.js?v=3.5.3.0:1 defineModule @ alameda.js?v=3.5.3.0:1 depFinished @ alameda.js?v=3.5.3.0:1 (anonymous) @ alameda.js?v=3.5.3.0:1 site.js?v=3.5.3.0:1 RequireJS error: TypeError: Cannot read property 'match' of undefined. Failed modules: apphost.js?v=3.5.3.0:1 app is hidden apphost.js?v=3.5.3.0:1 triggering app resume event
someperson 3 Posted December 9, 2018 Posted December 9, 2018 (edited) I was eventually able to get the restore to work using an iOS device. Not sure why it wouldn't work in Safari, Firefox, or Chrome on macOS. EDIT: Ran into another problem. Many videos won't play, and this error shows up in the logs: Shared object "libx264.so.152" not found, required by "libavcodec.so.58" Edited December 9, 2018 by someperson
makarai 109 Posted December 9, 2018 Posted December 9, 2018 (edited) I would instead use the instructions in the first post. It is officially maintained by us and will give you the latest stable release, rather than a beta. Following the Emby Server 3.6 stable release, we will look to get the freenas catalog updated and take over ownership of it. Thanks ! Yeah you are right,i will stop promoting the beta version. On a further note: FreeNAS has finaly release the 11.2-Stable Production Release (this is awesome) https://www.freenas.org/blog/freenas-11-2-has-arrived/ Maybe its time to change the created jail to 11.2, to avoid future issues on the stable! If you need me to do a couple test installs let me know and I try it out. Edited December 9, 2018 by makarai
makarai 109 Posted December 9, 2018 Posted December 9, 2018 (edited) @@LukeThe first page should display the followingEmby For FreeNAS-Stable (11.2)Simple Installation Requires FreeNAS 11.2 Stable This Installation method will create a Jail that is fully configurable via the FreeNAS GUI LATEST STABLE (3.5.3.0) cd /tmp wget https://raw.githubusercontent.com/ma-karai/iocage-plugin-emby/master/emby-server.json iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master' LATEST BETA (3.6.0.75) cd /tmp wget https://raw.githubusercontent.com/ma-karai/iocage-plugin-emby/beta/emby-server-beta.json iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'beta' Except with your repos that need to be updated as they are not working atm. Edited April 26, 2019 by makarai
someperson 3 Posted December 9, 2018 Posted December 9, 2018 LATEST STABLE (3.5.3.0) cd /tmp wget https://raw.githubusercontent.com/bott0r/iocage-plugin-emby/master/emby-server.json iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master' I tried these instructions, but still get this error: Shared object "libx264.so.152" not found, required by "libavcodec.so.58" What should I do?
makarai 109 Posted December 9, 2018 Posted December 9, 2018 I tried these instructions, but still get this error: Shared object "libx264.so.152" not found, required by "libavcodec.so.58" What should I do? I am guessing, you downloaded an emby-server.json before hand and its still in your folder. check if there are any other emby-server.json files there and delete them. Just to make sure, you are on the newest FreeNAS version?
someperson 3 Posted December 9, 2018 Posted December 9, 2018 (edited) I am guessing, you downloaded an emby-server.json before hand and its still in your folder. check if there are any other emby-server.json files there and delete them. Just to make sure, you are on the newest FreeNAS version? I am on the newest FreeNAS version, and I made sure to wipe out any other emby-server.json files in the folder first. It was definitely using the version from that GitHub repository. EDIT: I did some poking around, and noticed that there are two Emby 3.5.3.0 binaries for FreeBSD out there: https://github.com/MediaBrowser/Emby.Releases/releases/tag/3.5.3.0 The one that ends in .txz is the one that these scripts are using. It does not contain a copy of libx264. The one that ends in .tar.xz has a completely different structure inside and does contain a copy of libx264. I have to wonder if this was, perhaps, an attempt to update the release that didn't go quite right? EDIT 2: I replaced the contents of "/usr/local/opt/emby-server" in the jail with the contents of "emby-server-freebsd_3.5.3.0_amd64.tar.xz". This resulted in a working version of Emby. Edited December 9, 2018 by someperson
makarai 109 Posted December 9, 2018 Posted December 9, 2018 I am on the newest FreeNAS version, and I made sure to wipe out any other emby-server.json files in the folder first. It was definitely using the version from that GitHub repository. EDIT: I did some poking around, and noticed that there are two Emby 3.5.3.0 binaries for FreeBSD out there: https://github.com/MediaBrowser/Emby.Releases/releases/tag/3.5.3.0 The one that ends in .txz is the one that these scripts are using. It does not contain a copy of libx264. The one that ends in .tar.xz has a completely different structure inside and does contain a copy of libx264. I have to wonder if this was, perhaps, an attempt to update the release that didn't go quite right? EDIT 2: I replaced the contents of "/usr/local/opt/emby-server" in the jail with the contents of "emby-server-freebsd_3.5.3.0_amd64.tar.xz". This resulted in a working version of Emby. have you tried giving the beta a shot?
makarai 109 Posted December 9, 2018 Posted December 9, 2018 (edited) I am on the newest FreeNAS version, and I made sure to wipe out any other emby-server.json files in the folder first. It was definitely using the version from that GitHub repository. EDIT: I did some poking around, and noticed that there are two Emby 3.5.3.0 binaries for FreeBSD out there: https://github.com/MediaBrowser/Emby.Releases/releases/tag/3.5.3.0 The one that ends in .txz is the one that these scripts are using. It does not contain a copy of libx264. The one that ends in .tar.xz has a completely different structure inside and does contain a copy of libx264. I have to wonder if this was, perhaps, an attempt to update the release that didn't go quite right? EDIT 2: I replaced the contents of "/usr/local/opt/emby-server" in the jail with the contents of "emby-server-freebsd_3.5.3.0_amd64.tar.xz". This resulted in a working version of Emby. @@Luke, can you check the stable release, as the previous poster is right, something is not right in the 3.5.3.0 tarbal. I know the beta inatalls fine and plays all the content. Edited December 9, 2018 by makarai
Mael 5 Posted December 11, 2018 Posted December 11, 2018 LATEST BETA (3.6.0.75) cd /tmp wget https://raw.githubusercontent.com/bott0r/iocage-plugin-emby/beta/emby-server.json iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'beta' Running the wget command throws a 404 Not Found error.
Mael 5 Posted December 11, 2018 Posted December 11, 2018 Running the wget command throws a 404 Not Found error. I figured it out... it should be... wget https://raw.githubusercontent.com/bott0r/iocage-plugin-emby-beta/master/emby-server.json
makarai 109 Posted December 11, 2018 Posted December 11, 2018 Sorry, I fixed my link, I updated my repo yesterday and changed the naming, both should work now
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now