Local access server

Local access means that, for example, the Jellyfin server is not publicly accessible and/or the skill is not publicly accessible. This is a very common setup, but don't worry you can still use this skill very easily. The public access is generally necessary for the use of an selfhosted Alexa Skill. So if you don't have a domain with TLS/SSL certificate, then you can use several external services that allow you to use this skill by tunneling the public request to you private accessible server. The only requirements for a service to be suitable is a valid TLS/SSL certificate with a domain and https over port 443 must be possible. No specific services are mentioned here, but there are many great projects (some open source and/or free) you can find in the summary of this very good list.

Select one of your favorite tunnel service and follow its installation until you get a public address. Make sure you tunnel the correct port on you server. You can change the default port 1456 of this skill in the skill.config file as the web_app_port value.

Now you just have to enter the domain in the skill.conf file under as the skill_endpoint value and you can start and use the skill. If your Jellyfin server is also not public, then also tunnel its port with the service and add the new domain as the jellyfin_endpoint value in the config file before you start the skill.

Your skill is now ready and you can move on to the usage description.