Cant find my domain or something

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: baaasty.de

I ran this command: sudo certbot certonly --apache (then baaasty.de)

It produced this output:

root@baaasty:~# sudo certbot certonly --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): baaasty.de
Requesting a certificate for baaasty.de

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: baaasty.de
  Type:   dns
  Detail: No valid IP addresses found for baaasty.de

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible 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.

My web server is (include version):

root@baaasty:~# apache2 -version
Server version: Apache/2.4.38 (Debian)
Server built:   2021-06-10T10:13:06

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

root@baaasty:~# lsb_release -d
Description:    Debian GNU/Linux 10 (buster

My hosting provider, if applicable, is: https://deinserverhost.de/

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

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

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

root@baaasty:~# certbot --version
certbot 1.20.0```
1 Like
2

baaasty.de doesn't have any IP address attached (NS record pointed to ns1.dnslinq.de . did you update your dns provider on registror?

actually, I don't think ns1.dnslinq.de respond to any quary.. (times out), maybe they have problem?

1 Like
3

Maybe it's because I just assigned the domain to the IP. I'll wait until tomorrow and try again.

4

Screenshot_1

The discord stuff is already working.

It can also be that the domain has to be connected to the complete server. And not just Minecraft stuff.

5

looks like my ISP is on blocklist of dnslinq.de

1 Like
6

So what can i do now?

7

why you are requesting a cert for? IIRC minecraft server would need one and you said discord was already running
have a actual webpage? (from --apache)

1 Like
8

But at the moment the need to type http://discord.baaasty.de/. I want https://discord.baaasty.de/

9

then you what certificate for discord.baaasty.de LE will follow CNAME, so challenge should Done on server that host discord

1 Like
10 
root@baaasty:/home/baaasty/Discord_Bot# sudo certbot certonly --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): discord.baaasty.de
Requesting a certificate for discord.baaasty.de

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: discord.baaasty.de
  Type:   dns
  Detail: Fetching http://discord.gg/XMmAz33JrR: No valid IP addresses found for discord.gg

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible 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.
11

ah now I get it.
your redirect is hosted on redirect.center, which is catch-all redirect by parsing CNAME record. they don't know about your host until requested, and can't have certificate valid for all domains it may get CNAMEed request from(redirect.centor won't reply with your certificate) and actually won't reply https request at all :
if you want this to be https you will need to host your redirect by a hosting you actually control and prepare a certificate.

2 Likes
13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.