@@digital_aloha would you be looking at creating video about hardware transcoding? i know my 220+ supports it but i cannot get my 4k content to work despite looking at several tutorials allready
Thank you so much for putting this together. I'm purchasing a DS423+ and planning on installing Jellyfin on it, and this tutorial is exactly what I was looking for. Question: I see Jellyfin's official Synology installation instructions use "add from URL" to install from a container image. Is there a reason why your tutorial (and others) use the .yml code instead? The container image seems less scary for a noob like myself at first glance :)
You're welcome!! Hopefully this tutorial helps you with installing Jellyfin on your DS423+. Regarding your question, I actually did check out Jellyfin's Synology installation guide and it is actually dated. The way they describe installing Jellyfin is probably what you would do prior to DSM 7.1 (I think) or whenever Synology changed over from the Docker package to Container Manager. If you are using Container Manager, then you probably want to install Jellyfin, and any other Docker containers, using Projects and the .yml configuration file. Hope this information helps and good luck to you in your setup.
This is a great video. I have had jellyfin up and running for a little while, so I'm just using this as a reference to allow remote access. I think I was able to follow along with your instructions for the most part. I set up the ddns, the wildcard certificate, the reverse proxy, assigned the certificate to my domain, and set up port forwarding on my router. When I try to access it though, I get a connection timeout. Any idea where I may have gone wrong with this?
Thanks for the compliment on the video!! Regarding your question, if you can do an nslookup or dig on the subdomain you created and it returns your public ip address then the issue is likely with the reverse proxy setup or port forwarding. If not, double check that you've done the DDNS setup correctly. Hopefully that points you in the right direction. Good luck to you!!
I have a question to the remote access, is it possible to share a public link to be viewable by everybody without to log in? I want to create my own personal RUclips like server, where I can share with my friends our personal videos from our parties, concerts, events etc. without the crap of strikes on RUclips BCS of the music in the background. Is Jellyfin the right option for it, or do you have any other tip, how to achieve this? :)
At that point I've logged on to my Synology NAS through SSH. I have a video on SSH if you aren't familiar with it -> ruclips.net/video/t213x-sne6A/видео.html. Hope that helps?
Hi thank you for your video, very clear and easy to follow. However, while adding the reverse proxy for jellyfin, instead of loading the jellyfin login page is loading the DSM login screen :o I followed step by step the steps and I end up in a different login page then expected , why is this happening? I tried the same also with emby (with jellyfin container stopped so does not make use of the same port) and also in this case I end up in the same situation with DSM login page instead of emby login page Any suggestions? thank you in advance
Greetings. Isn’t it easier to follow the option recommended by Synology and Jellyfin, which involves installing it through the image? I see that this way is simpler and less complicated. What advantages does the method you’re showing have compared to the one recommended by Synology and Jellyfin for installing it on a Synology NAS?
I think you are referring to the instructions from this link -> jellyfin.org/docs/general/installation/synology/. If so, it is essentially the same install that I went through in the video but using the older Docker package that Synology used to provide. If you have Container Manager the recommended install method is what I've covered in this video. Either way works though so pick the installation method that feels more comfortable to you. Good luck!!
could you explain more on the port forwarding. you glazed over that and i dont know how to do it. i dont understand where to put the number 443 or the other number i need. yours looks different than my router please help if you can. thank you
Hey, what about the "data" and "log" folder? I have a previous jellyfin install (synology community package version of jellyfin), do I need to add those as well (lives in appdata like cache and config)
Hello sir, i have a nas asustor model AS1102TL, in hardware acceleration of jellyfin, have options, ex; amd amf, nvidia, intel quicksync, video acceleration api, rockchip, etc.. what option i need choose to work encode and decode hardware?
Actually network center is from my Synology router. What I'm saying here is that you need to setup your router with port forward similar to what I've setup. This is just an example.
Good question... The version displays what Docker Compose version is supported. Version 3.x seems to be what I'm seeing in most recent projects in their docker-compose.yml files which seems to be used for compatibility reasons. Hope that helps?
Are you using a Synology DDNS hostname? It should work if you did. If not, that's still fine, but you can't setup a wildcard certificate like the error says.
I love your videos, I'm pretty new to NAS stuff and I think you're one of the best educators on yt in this area, keep up the great work.
Great to hear that you love my videos and I appreciate the compliment!! More videos to come for sure.😀
Thank you so much - straight forward easy to follow. I will now be looking at replacing Plex.
wow what a fantastic tutorial ive been waiting for it for ages! great help and worked 100%
Awesome... happy the tutorial worked for you!!
@@digital_aloha would you be looking at creating video about hardware transcoding? i know my 220+ supports it but i cannot get my 4k content to work despite looking at several tutorials allready
I am planning a video with a setup with hardware transcoding. Look for it in the next few weeks.
@digital_aloha makes the best synology tutorials
You are amazing! Thank you!
You're welcome!! Thanks for the compliment!!
Thank you so much for putting this together. I'm purchasing a DS423+ and planning on installing Jellyfin on it, and this tutorial is exactly what I was looking for.
Question:
I see Jellyfin's official Synology installation instructions use "add from URL" to install from a container image. Is there a reason why your tutorial (and others) use the .yml code instead? The container image seems less scary for a noob like myself at first glance :)
You're welcome!! Hopefully this tutorial helps you with installing Jellyfin on your DS423+.
Regarding your question, I actually did check out Jellyfin's Synology installation guide and it is actually dated. The way they describe installing Jellyfin is probably what you would do prior to DSM 7.1 (I think) or whenever Synology changed over from the Docker package to Container Manager. If you are using Container Manager, then you probably want to install Jellyfin, and any other Docker containers, using Projects and the .yml configuration file.
Hope this information helps and good luck to you in your setup.
@@digital_aloha Makes sense! I suspected that might be the case. A well earned subscription.
@@Wesden7 Much appreciated!!
This is a great video. I have had jellyfin up and running for a little while, so I'm just using this as a reference to allow remote access. I think I was able to follow along with your instructions for the most part. I set up the ddns, the wildcard certificate, the reverse proxy, assigned the certificate to my domain, and set up port forwarding on my router. When I try to access it though, I get a connection timeout. Any idea where I may have gone wrong with this?
Thanks for the compliment on the video!! Regarding your question, if you can do an nslookup or dig on the subdomain you created and it returns your public ip address then the issue is likely with the reverse proxy setup or port forwarding. If not, double check that you've done the DDNS setup correctly. Hopefully that points you in the right direction. Good luck to you!!
I have a question to the remote access, is it possible to share a public link to be viewable by everybody without to log in? I want to create my own personal RUclips like server, where I can share with my friends our personal videos from our parties, concerts, events etc. without the crap of strikes on RUclips BCS of the music in the background. Is Jellyfin the right option for it, or do you have any other tip, how to achieve this? :)
Where are you at 2:08 !! I'm lost
At that point I've logged on to my Synology NAS through SSH. I have a video on SSH if you aren't familiar with it -> ruclips.net/video/t213x-sne6A/видео.html. Hope that helps?
i dont have a router from synology / the network center what can i do ?
Hi thank you for your video, very clear and easy to follow.
However, while adding the reverse proxy for jellyfin, instead of loading the jellyfin login page is loading the DSM login screen :o
I followed step by step the steps and I end up in a different login page then expected , why is this happening?
I tried the same also with emby (with jellyfin container stopped so does not make use of the same port) and also in this case I end up in the same situation with DSM login page instead of emby login page
Any suggestions?
thank you in advance
Greetings. Isn’t it easier to follow the option recommended by Synology and Jellyfin, which involves installing it through the image? I see that this way is simpler and less complicated. What advantages does the method you’re showing have compared to the one recommended by Synology and Jellyfin for installing it on a Synology NAS?
I think you are referring to the instructions from this link -> jellyfin.org/docs/general/installation/synology/. If so, it is essentially the same install that I went through in the video but using the older Docker package that Synology used to provide. If you have Container Manager the recommended install method is what I've covered in this video. Either way works though so pick the installation method that feels more comfortable to you. Good luck!!
could you explain more on the port forwarding. you glazed over that and i dont know how to do it. i dont understand where to put the number 443 or the other number i need. yours looks different than my router please help if you can. thank you
Hey, what about the "data" and "log" folder? I have a previous jellyfin install (synology community package version of jellyfin), do I need to add those as well (lives in appdata like cache and config)
Hello sir, i have a nas asustor model AS1102TL, in hardware acceleration of jellyfin, have options, ex; amd amf, nvidia, intel quicksync, video acceleration api, rockchip, etc.. what option i need choose to work encode and decode hardware?
I'm getting an error to the config after creating the project
Hello ! Now, at 5:23 I can't find "network center" in the package center...
Actually network center is from my Synology router. What I'm saying here is that you need to setup your router with port forward similar to what I've setup. This is just an example.
@@digital_aloha ok thx
I'm à noob in this domain 😅
@@theophanedebet7965 You're welcome! Good luck to you in your set up.
What is the "Version: 3.5" referring to?
Good question... The version displays what Docker Compose version is supported. Version 3.x seems to be what I'm seeing in most recent projects in their docker-compose.yml files which seems to be used for compatibility reasons. Hope that helps?
I had to remove the :latest from the image name to get the yaml to work.
Thanks for your feedback! Hopefully others can benefit from your comment.
I have emby installed on my synology DS 423+. When I enter the nas ip address, instead of jellyfin opening, emby is? Help
Sounds like you need to assign jellyfin to a different port. Or maybe turn off emby and try it again? Good luck!!
So I deleted emby and jellyfin open up with no problem. Working like a charm. Thanks
@@gregorymclaughlin7616 You're welcome. Glad that did the trick!
4:52 does not work. Error: "Only domains of Synology DDNS support wildcard certificates issued by Let's Encrypt."
Are you using a Synology DDNS hostname? It should work if you did. If not, that's still fine, but you can't setup a wildcard certificate like the error says.