Selfhosted

40198 readers

672 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

[solved] Getting "internal error" when trying to create SSL certificate in NGINX (lemmy.kde.social)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

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 Challenge as 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!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 10 months ago (1 children)

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 😅

[–] [email protected] 1 points 10 months ago (1 children)

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...

[–] [email protected] 2 points 10 months ago

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!