Jellyfin installation problems

Help
1

on jellyfin installation i have some problems

My domain is: ?

I ran this command:
sudo certbot certonly --agree-tos --email user@email.com --no-eff-email --webroot -w /var/www/html -d media.hwdomain.io

It produced this output:
Requesting a certificate for media.hwdomain.io

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: media.hwdomain.io
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for media.hwdomain.io - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for media.hwdomain.io - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

Here i am :slight_smile: i am not familar with linux... i try to install jellyfin from this link (So installierst du Jellyfin Media Server unter Ubuntu 22.04 – HowtoForge)

**i can run commands that is my expertise in linux XD **

My web server is (include version):

The operating system my web server runs on is (include version): ubuntu 24.04.2 LTS

My hosting provider, if applicable, is: local

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): terminal

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): i dont know

letsencrypt.txt (40.1 KB)

change it from *.log to *.txt

2

Shouldn't that be media.hwdomain.io? Howcome the answer to this question is "?" while further down the questionnaire you've used media.hwdomain.io in the command?

Do you actually own the domain hwdomain.io / subdomain media.hwdomain.io?

I can see the domain hwdomain.io exists in the WHOIS information, registered on 2023-05-26T07:01:19Z, but also expired on 2025-05-26T07:01:19Z?

The .io TLD nameservers also do not know any domain hwdomain.io.

2 Likes
3

I've bolded the important part--the command you've run requires that you have published DNS records (and also that port 80 is open), and you don't have them. You'll need to create them.

2 Likes
4

You missed some critical points in that guide:

Bevor du beginnst, stelle sicher, dass du Folgendes hast:

  • Einen Domainnamen, der auf eine Server-IP-Adresse zeigt.

Achte darauf, dass du die E-Mail-Adresse und den Domainnamen mit deinen Daten änderst.

You need your own domain name to follow this guide as written.

I'd also note that that guide makes your life much more complicated than it needs to be by using Apache as a reverse proxy--Caddy is vastly easier to configure, and also takes care of the TLS stuff automagically. But it still would require that you have your own domain name, DNS records pointing to your server IP address, and ports 80/443 open to your server.

4 Likes
5

ok that is way over my capebilitys... i look for another way to install jellyfin :smiley:

Thanks for your knowlage and help

6

The problem is not with Jellyfin itself. You just tried to get a certificate for an expired domain name which, most likely, is not even yours?

3 Likes
7

Quite certainly--OP just blindly followed the guide, copying and pasting everything in it, including the domain name it gives.

5 Likes
8

Oh wow.. I haven't looked at the guide at all, but that's.. Well.. Next level I guess.

Note to OP: trying to get certificates for domains one does not actually control does not have anything to do with familiarity with Linux nor the guide in question. It comes down to a basic understanding of how the web PKI works.

And also: always, ALWAYS learn what the commands of a guide are doing. NEVER blindly just follow a guide without knowing what the step actually does. And never, NEVER just blindly copy/paste a command if you're not familiar it.

Also note that even though Certbot might have lead you here to this Community, this is the Let's Encrypt community and is not a support channel for Jellyfin in general.

1 Like