Hello! I just installed jellyfin and wanted to access it with https. So, as I did yesterday for other apps (immich) in nginx proxy host I created a new proxy host, set the domain (jellyfin.mydomain.duckdns.org), set “create new SSL certificate”, “I agree on let’s encrypt stuff” and clicked save. Ports 80 and 443 are the only ports exposed on my router.
After some loading, internal error. searching on the web I tried the followings:
- tried with and without “force SSL”
- open port 81 on the router [source]
- checked
Use a DNS Challengeas explained here
but internal error was always there. Any idea what could be the problem? and why yesterday everything worked flawlessly?
EDIT: I rebooted and then i couldn’t even log in, bad gateway error. after some troubles I do not remember I achieved to log in, and now the SSL certificate has been added correctly!
Well, I’m guessing your are using nginx proxy manager, and if so please close that port 81 ASAP :-) you don’t need it open in any way
Can you restart the container and the db (if using Mariadb and not sqlite) and try again exactly how you did it the first time?
You can also see the issue by going through the logs and tell us what they say, would be a bit more helpful that internal error on the web interface 😅
please close that port 81 ASAP :-)
yes I closed it XD
Can you restart the container and the db (if using Mariadb and not sqlite) and try again exactly how you did it the first time?
I rebooted the system and now I can’t log in, it says
bad gateway…I don’t know how I managed to log in after some troubles and now it added the SSL certificate without problems… I’m confused, but it worked so it’s good ahahaah
thanks for the help!
let’s encrypt has always been a repeating bugaboo for me on multiple synology nas/routers through the years, sometimes it flies through flawlessly, and sometimes (oftentimes) it doesn’t on the first try
deleted by creator
