# I can't create certificate **URL:** \ **Category:** Help\ **Created:** [January 13, 2025, 8:44pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967 "2025-01-13T20:44:19Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 13, 2025, 8:44pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/1 "2025-01-13T20:44:19Z")
My domain is: panel.mcbest.pl I ran this command: sudo certbot certonly --standalone -d panel.mcbest.pl It produced this output: ```nohighlight 1 actionable task: 1 executed maks@maks-B550M-AORUS-ELITE:~/Pulpit/Minecraft-nodes-minecraft/minecraft-nodes-master/nodes$ sudo certbot certonly --standalone -d panel.mcbest.pl [sudo] hasło użytkownika maks: Saving debug log to /var/log/letsencrypt/letsencrypt.log Requesting a certificate for panel.mcbest.pl Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: panel.mcbest.pl Type: connection Detail: 5.173.148.59: Fetching http://panel.mcbest.pl/.well-known/acme-challenge/9l3PyRql-1lYBoSK2_Tb9yrtbLf9VK97KfnMtNqEnlE: Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections 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): nginx version: nginx/1.24.0 (Ubuntu) The operating system my web server runs on is (include version): No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.1 LTS Release: 24.04 Codename: noble My hosting provider, if applicable, is: its my own machine, i bought static ip from my internet provider I can login to a root shell on my machine (yes or no, or I don't know): no, disabled 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): certbot 2.9.0 ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [January 14, 2025, 12:49am UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/2 "2025-01-14T00:49:01Z")
Hello @embe1, welcome to the Let's Encrypt community. 🙂 Given that you are using the option > [@embe1](#): > > --standalone the best I can find is > [@embe1](#): > > Timeout during connect ( **likely firewall problem** ) ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 14, 2025, 2:49am UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/3 "2025-01-14T02:49:17Z")
> [@embe1](#): > > nginx version: nginx/1.24.0 (Ubuntu) Usually if you have an nginx server running you do not use --standalone. Instead, use --webroot or --nginx options. But, if your nginx is running now it is not available from the public internet. This test site is excellent to help debug new servers and comms setups: [https://letsdebug.net](https://letsdebug.net) ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:28pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/4 "2025-01-14T15:28:03Z")
```nohighlight maks@maks-B550M-AORUS-ELITE:~$ sudo certbot certonly --nginx -d panel.mcbest.pl Saving debug log to /var/log/letsencrypt/letsencrypt.log Error while running nginx -c /etc/nginx/nginx.conf -t. 2025/01/14 16:27:26 [emerg] 117393#117393: cannot load certificate "/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem, r) error:10000080:BIO routines::no such file) nginx: configuration file /etc/nginx/nginx.conf test failed The nginx plugin is not working; there may be problems with your existing configuration. The error was: MisconfigurationError('Error while running nginx -c /etc/nginx/nginx.conf -t.\n\n2025/01/14 16:27:26 [emerg] 117393#117393: cannot load certificate "/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem, r) error:10000080:BIO routines::no such file)\nnginx: configuration file /etc/nginx/nginx.conf test failed\n') ``` ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:29pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/5 "2025-01-14T15:29:20Z")
i have firewall disabled on both router and machine ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 14, 2025, 3:35pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/6 "2025-01-14T15:35:53Z")
> [@embe1](#): > > ```nohighlight > 2025/01/14 16:27:26 [emerg] 117393#117393: > cannot load certificate "/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem": > BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/panel.mcbest.pl/fullchain.pem, r) error:10000080:BIO routines::no such file) > nginx: configuration file /etc/nginx/nginx.conf test failed > > ``` Your nginx configuration names a file that does not exist. You must remove that reference. Did you delete the certificate(s) you got previously without removing them from nginx? See this for how to safely delete certs: [User Guide — Certbot 3.2.0.dev0 documentation](https://eff-certbot.readthedocs.io/en/latest/using.html#safely-deleting-certificates) Also show: ```nohighlight sudo certbot certificates ``` ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:36pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/7 "2025-01-14T15:36:31Z")
no certificates found ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 14, 2025, 3:37pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/8 "2025-01-14T15:37:08Z")
> [@embe1](#): > > no certificates Where did they go? I can see from your history you got certs before ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:37pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/9 "2025-01-14T15:37:25Z")
i also think this might be happeing because of wrong configuration of static ip, this was my first time doing this bc i was my whole life doing this on hetzner ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:37pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/10 "2025-01-14T15:37:55Z")
on other machine ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 14, 2025, 3:38pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/11 "2025-01-14T15:38:35Z")
Then you need to remove the invalid certificate references from nginx. See that link I provided about Safely Deleting Certs ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:47pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/12 "2025-01-14T15:47:49Z")
No certificate found with name panel.mcbest.pl (expected /etc/letsencrypt/renewal/panel.mcbest.pl.conf). ---
**Author:** ![Mad182](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mad182/32/77719_2.png) [@Mad182](https://community.letsencrypt.org/u/Mad182)\ **Post date:** [January 14, 2025, 3:48pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/13 "2025-01-14T15:48:24Z")
If it's a home connection with a router in front of the machine, you may need to set up port forwarding on the router. Did you do that? The address in your log ([http://panel.mcbest.pl/](http://panel.mcbest.pl/)) doesn't seem to be accessible from the internet. ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:50pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/14 "2025-01-14T15:50:09Z")
i didn't port-forward it, could you help me with it? ![obraz](https://global.discourse-cdn.com/letsencrypt/original/3X/6/0/6010dce2b0ef73b421456d0db009faaaf428cf5c.png) ---
**Author:** ![Mad182](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mad182/32/77719_2.png) [@Mad182](https://community.letsencrypt.org/u/Mad182)\ **Post date:** [January 14, 2025, 3:55pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/15 "2025-01-14T15:55:24Z")
WAN port 80-80 LAN port 80-80 LAN IP - the IP assigned to the server in the local network The rest is not important I think. and then the same for port 443, for HTTPS. It would probably be a good idea to also configure a static IP address to the machine in local network, otherwise it may assign it a different one after a restart or over time. ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 3:57pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/16 "2025-01-14T15:57:07Z")
i think i have set the static ip in my machine ![obraz](https://global.discourse-cdn.com/letsencrypt/original/3X/c/0/c0efb3154597f5d4e81238c63c76d095dab329af.png) ---
**Author:** ![Mad182](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mad182/32/77719_2.png) [@Mad182](https://community.letsencrypt.org/u/Mad182)\ **Post date:** [January 14, 2025, 3:59pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/17 "2025-01-14T15:59:01Z")
OK, that's good. You may also want to configure this IP to be static in the router config, so it doesn't assign this IP to some other device if the server is not online. ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 4:00pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/18 "2025-01-14T16:00:17Z")
that is the only option i have in the dhcp ![obraz](https://global.discourse-cdn.com/letsencrypt/original/3X/2/d/2db713cd34d9dde6ba40be8c5418c3364cdce321.png) ---
**Author:** ![embe1](https://avatars.discourse-cdn.com/v4/letter/e/b2d939/32.png) [@embe1](https://community.letsencrypt.org/u/embe1)\ **Post date:** [January 14, 2025, 4:02pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/19 "2025-01-14T16:02:58Z")
still happens the same… ```nohighlight maks@maks-B550M-AORUS-ELITE:~$ sudo certbot certonly --standalone -d panel.mcbest.pl Saving debug log to /var/log/letsencrypt/letsencrypt.log Requesting a certificate for panel.mcbest.pl Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: panel.mcbest.pl Type: connection Detail: 94.254.163.7: Fetching http://panel.mcbest.pl/.well-known/acme-challenge/N3IkIBYwhy1do8c8nvIlBxYQLmCk3cu_iVfoOvCdJiI: Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections 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. ``` ---
**Author:** ![Mad182](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mad182/32/77719_2.png) [@Mad182](https://community.letsencrypt.org/u/Mad182)\ **Post date:** [January 14, 2025, 4:05pm UTC](https://community.letsencrypt.org/t/i-cant-create-certificate/231967/20 "2025-01-14T16:05:11Z")
Did you restart the router? I don't know what kind of router you have, but at least mine requires a restart after setting up port forwarding IIRC. [Next page](https://community.letsencrypt.org/t/i-cant-create-certificate/231967.md?page=2)