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.
I ran this command:sudo certbot --apache --agree-tos --redirect --hsts --staple-ocsp --email [redacted] -d jaco.ddns.net
It produced this output:unauthorized, o fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address
My web server is (include version): apache2 last version
The operating system my web server runs on is (include version): debian 11
My hosting provider, if applicable, is: NO-IP
I can login to a root shell on my machine (yes or no, or ): 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
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
2023-01-25 15:18:44,905:DEBUG:certbot._internal.main:certbot version: 1.12.0
2023-01-25 15:18:44,905:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/bin/certbot
2023-01-25 15:18:44,905:DEBUG:certbot._internal.main:Arguments: ['--apache', '--agree-tos', '--redirect', '--hs>
2023-01-25 15:18:44,905:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apach>
2023-01-25 15:18:44,915:DEBUG:certbot._internal.log:Root logging level set at 20
2023-01-25 15:18:44,916:INFO:certbot._internal.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2023-01-25 15:18:44,916:DEBUG:certbot._internal.plugins.selection:Requested authenticator apache and installer >
2023-01-25 15:18:44,960:DEBUG:certbot_apache._internal.configurator:Apache version is 2.4.54
2023-01-25 15:18:45,159:DEBUG:certbot._internal.plugins.selection:Single candidate plugin: * apache
Description: Apache Web Server plugin
Interfaces: IAuthenticator, IInstaller, IPlugin
Entry point: apache = certbot_apache._internal.entrypoint:ENTRYPOINT
Initialized: <certbot_apache._internal.override_debian.DebianConfigurator object at 0x7f5b74aa1550>
Prep: True
2023-01-25 15:18:45,160:DEBUG:certbot._internal.plugins.selection:Selected authenticator <certbot_apache._inter>
2023-01-25 15:18:45,160:INFO:certbot._internal.plugins.selection:Plugins selected: Authenticator apache, Instal>
2023-01-25 15:18:45,200:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/directory.
2023-01-25 15:18:45,202:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencryp>
2023-01-25 15:18:45,398:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "GET /directory H>
2023-01-25 15:18:45,399:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Wed, 25 Jan 2023 20:18:45 GMT
Content-Type: application/json
Content-Length: 659
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800
{
"jaqgMR7aU5g": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",
"keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
"meta": {
curl ifconfig.io
70.48.118.46
sudo apachectl -t -D DUMP_VHOSTS
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
*:80 is a NameVirtualHost
default server 127.0.1.1 (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost 127.0.1.1 (/etc/apache2/sites-enabled/000-default.conf:1)
port 80 namevhost debian3 (/etc/apache2/sites-enabled/jellyfin.conf:4)
I just realized that the other server I have (also apache), which is mostly configured like this one and works fine, but it's also configured on ports 80 and 443 in the vhost config file. I guess that's a problem? if it's the case, can I use other ports (to be forwarded)?
That was the problem. I made some small adjustments in my router's port forwarding and finally received my certificates.
Thank you for your precious help
