saarg

All traffic between the client and letsencrypt are using ssl if you are using our preset configs. They only listen for traffic on port 443.

With that info, we can't say what is wrong, but you have not set it up correctly. How did you set it up? Following space Invaders video is not a valid answer.

Sorry. Didn't see that py3-pip was only in the build dependencies and removed. Python 3 is included.

You don't need to change the port in the container. You change the host port in the template, which you have already done as you have changed it to 8297. That is all you have to do.

You can try to add it by opening command line of the container and issue: pip3 install pyopenssl Then restart the container. That should fix the issue until we push a new build.

You should not set it to host or use privileged. The template should have the correct settings already, so it's just the ports you need to set. I have not watched the video and will not do it either, so you have to tell us what you have done. You have set the local subnet in openvpn-as?

You have the gateway on 192.168.4.1? Your A record and cnames are correct?

You can't test the port forwarding to letsencrypt as nginx isn't started until a cert is created. You can use our nginx container to test. Use this blog post for troubleshooting https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Can you also show us the port forward?

You can use any SSH client or the terminal in the webui of unraid.

I'm not talking about our documentation, butrhe tvheadend documentation, which is easily found using the help button in the tvheadend webui or using Google.

You need to read the documentation on how this works as you have not configured it correctly. How do I know this? You don't have the EPG grabber modules tab. So read the documentation or find some guide on the internet for how to set up grabbing. The XML file doesn't go in the /config folder. It goes in /config/data and you use the tv_grab_file grabber. But first read up on how to enable that module in tvheadend.

What does the log say? You also have to connect the EPG data to the channels. It's not always done automatically if the name of the channel in tvheadend and the guide.xml is not the same.

/config/data is inside the container. So the /config folder is the same as /many/user/appdata/tvheadend. You have to add the guide.xml to that folder and then tvheadend adds the guide to it's internal EPG when the tv_grab_file grabber is set to run. You also have to enable it in tvheadend. Did you copy the tv_grab_file in the data folder? That is not needed there.

Read my previous post.

Huh? Wsl? If you are not running unraid, this is not the correct place for support. Containers running on windows isn't something we really support either. We only test on Linux. So go to our forum or join our discord.

There is nothing to configure. It grabs the XML file in /config/data/

I can't help with app issues. You have to ask jellyfin about that. If it's working, no need to ping jellyfin. Pinging from inside the letsencrypt container is simply: ping jellyfin It uses the container name to communicate, as that stays the same. The IP changes inside the docker network on reboots and updates to containers.

Use the extra domain variable and replace jellyfin with the IP of the windows 10 computer in the proxy-conf. Don't remember the variable name now, but it's the one above the port. Might be host.

You need to have jellyfin on the same custom bridge as nextcloud and letsencrypt for it to work. Change jellyfin to use the proxynet network, if that is what you have set. Then exec into the letsencrypt container, either through command line or the console link in the unraid docker UI and do a ping jellyfin. Does it answer? What exactly did you do in the jellyfin documentation you linke to? You shouldn't need to read that toge it working. All you need to do is mentioned in the jellyfin proxy-conf in the letsencrypt container.

You can add it yourself in the template.

Nothing we can do to help either with that info.

Did you read the readme on GitHub? It's explained there.

You have changed the port in HABridge from 8080 to 80 and then in the template only changed the host port. You need to change both host and container port if you change the port in HABridge. The port mapping is mapping port 80 on the host to 8080 inside the container, so it will never work.

Do you have both letsencrypt and freshrss on the same custom bridge? If they are on the same custom bridge, you don't have to change to IP or change the port.