Does DynDns.org support Lets Encrypt having troubles with it

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: *.daddykins.mine.nu

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:
dyndns.org my person Nginx and pfsense
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):

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

so i dunno what to fill out
but Nginx doesnt offer Dyndns.org as an option for Lets Encrypt
Pfsense my router for Lets Encrypt ACME certificate offers only dyn.com but not dyndns.org so pfsense cant create lets encrypt certificate

i using *.daddykins.mine.nu as the domain as i wanna setup opencloud and other things but i can not see option for dyndns.org is it not supported? i been with dyndns.org for 20 years but yet its not an option.. so any help be great

You could try using other challenge methods, such as http-01 or tls-alpn-01, but that would require you to specify individual hostnames in the certificate request (should be fine for small number of these).

If you positively need a wildcard certificate, try DNS Alias Mode | pfSense Documentation and point DNS to a provider that pfSense has support for.

@Patryk well i already point my dyndns.org dns address to pfsense already for 10 years using there dynamic dns updater... but cuz i want to use like opencloud and convert home assistant http to https i need i guess nginx and in nginx doesnt have dyndns... and seems every video you find on youtube all uses cloudflare.. but i wanted to avoid that incase when it goes down my address still be up but things wont work just to get a https using lets encrypt ngix and cloudflare tunnel..

i have tried the http-01 as its an toggle in the nginx but always gives internal error.. when i dont offer a dns chellege... it sucks when videos are made just for cloudflare tunnel and u gotta try to reverse enginineer it to work for your own dns address when doesnt show up in the drop down lol

but ill check out that dns alias mode and read up on that

i appreciate your response.. as i was just getting frustrated and nothing but cloudflare tunnel videos

I'd recommend switching away from using wildcard certificate to one or many certificates with individual hostnames. That way you could use certbot with nginx integration to use http-01 challenge method, which does not need DNS support.

Or, you could use Caddy web server instead of nginx, which has Automatic HTTPS — Caddy Documentation, and aside from easier config, it'll order certificates effectively automatically.

Are you talking about Nginx Proxy Manager (NPM)?

2 Likes

ah ok the *. i used as i want to use
opencloud.daddykins.mine.nu
homeas.daddykins.mine.nu
unraid.daddykins.mine.nu
testserver.daddykins.mine.nu
and some others.. so then they would all be https and get diverted to each comp.. but so far its just cloudflare tunnel the videos mostly of

as i have the different dns that point to my pfsense but and for the most part standard http or domain address going towards a certain minecraft server.. works but i wanted to do opencloud and opencloud cant be used without a https and all this headache to setup certs..

i did try a video for ACME and haproxy but the acme wasnt working right on pfsense i wasnt getting the cert from lets encypt.. either cuz my internet poor or what not

then watched video for pfsense nginxy proxy manager.. but that didnt work either cuz they use the cloudflare tunnel and i just trying to use my dyndns.org account

but ill give that a shot the certbot or the caddy webserver

as the opencloud on unraid you need a working https connection cant use ip address cant be http has to be https://example.com

but ill read up on both those things

oh forgot to ask

so you wouldnty make a *.daddykins.mine.nu as a certificate
but youd do

cert for opencloud.daddykins.mine.nu
cert for unraid.daddykins.mine.nu and so on

Both are possible.
The wildcard "*." requires DNS authentication.
The individual names don't require DNS authentication.

3 Likes