undefined | Better HN

0 pointsnpodbielski8mo ago0 comments

No, I do not think so. In the linked page there is mention:

"Point a subdomain named ferrondemo of your domain name (for example, ferrondemo.example.com) to either: CNAME demo.ferron.sh or A 194.110.4.223"

This is really strange and make my Spidey sense tingle. If the goal is to just point your domain to this server it should not require DNS auth. Just HTTP is fine. DNS sure if you want optimize reverse proxy, because that would be also possible to do via http auth for every subdomain separately. If you just need some www server quickly pointing your domain to some other dude domain is not the way to go.

This feels weird.

0 comments

2 comments · 1 top-level

dorianniemiec8mo ago· 1 in thread

> If you just need some www server quickly pointing your domain to some other dude domain is not the way to go.

Yeah. But as I said before, people installing Ferron on their servers don't need to use this demo. Oh, and people using this demo don't need to install Ferron on their servers.

I just added two notices to this demo:

> Note: After completing the demo, it's recommended to delete the subdomain you have just created to prevent security issues.

> This demo setup is optional and exists only to demonstrate automatic TLS functionality. You do not need to point any subdomain to demo servers for normal use of Ferron.

npodbielskiOP8mo ago

Oh you are the author.

I think we do not understand each other. Look at this: https://letsencrypt.org/docs/challenge-types/#http-01-challe...

If this is for demo, even more DNS is not necessary. Just code your web server to serve challenge for that particular Uri, and you are done. I do not think so that you need wildcard cert for the demo. Just fixed subdomain is fine. Also you do not have to wait for DNS to propagate with HTTP method.

j / k navigate · click thread line to collapse