# Hint to letsdebug.net in error message **URL:** \ **Category:** Feature Requests\ **Created:** [October 31, 2018, 11:41am UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236 "2018-10-31T11:41:56Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![ohlr](https://avatars.discourse-cdn.com/v4/letter/o/76d3ee/32.png) [@ohlr](https://community.letsencrypt.org/u/ohlr)\ **Post date:** [October 31, 2018, 11:41am UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/1 "2018-10-31T11:41:56Z")
Hi, when certbot issues this error message, ``` To 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. ``` you could add a hint to [letsdebug.net](http://letsdebug.net). Users might find it helpfull because it can detect issues with DNS settings. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [October 31, 2018, 2:25pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/2 "2018-10-31T14:25:53Z")
Hi @ohlr > [@ohlr](#): > > you could add a hint to [letsdebug.net](http://letsdebug.net) thanks. Letsdebug helps in such a case. > [@Certbot http-01 challenge fails for non-www pages](https://community.letsencrypt.org/t/certbot-http-01-challenge-fails-for-non-www-pages/76216): > > M… But there was an older topic with the same idea. @schoen wrote, that there are a lot of older certbots in use. So creating a link to a third-party tool may be a problem, if the tool isn't longer available. -- But: I think there is another solution. A new topic, pinned under #Help with a list of tools with annotations. Closed, with no replies. There are a lot more tools (CT-logs, Ssllabs, Sslmate, a Mozilla Cipher check etc.). Then it's possible to check such a third-party tool and remove it, if it's not longer active. ---
**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\ **Post date:** [October 31, 2018, 2:33pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/3 "2018-10-31T14:33:59Z")
> [@JuergenAuer](#): > > But: I think there is another solution. A new topic, pinned under #Help with a list of tools with annotations. Closed, with no replies. There are a lot more tools (CT-logs, Ssllabs, Sslmate, a Mozilla Cipher check etc.). I really like that idea! ---
**Author:** ![ohlr](https://avatars.discourse-cdn.com/v4/letter/o/76d3ee/32.png) [@ohlr](https://community.letsencrypt.org/u/ohlr)\ **Post date:** [October 31, 2018, 3:00pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/4 "2018-10-31T15:00:10Z")
That’s a good idea too. However, currently certbot also references third-party tools. When succesfully obtaining a certificate it references SSllabs. ``` The new certificate covers the following domains: ... You should test your configuration at: https://www.ssllabs.com/ssltest/analyze.html?d=... ``` Since [letsdebug.net](http://letsdebug.net) is part of Let’s Encrypt (if I m not mistaken) it’s not even a third party. Maybe doing both, pinned topic + modified error message is the right way to go. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [October 31, 2018, 4:07pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/5 "2018-10-31T16:07:26Z")
> [@ohlr](#): > > Since [letsdebug.net](http://letsdebug.net) is part of Let’s Encrypt (if I m not mistaken) it’s not even a third party. It is in-fact a third party and not hosted by or built by Let's Encrypt staff 🙂 ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [October 31, 2018, 4:28pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/6 "2018-10-31T16:28:33Z")
> [@JuergenAuer](#): > > A new topic, pinned under #Help with a list of tools with annotations. Closed, with no replies. There are a lot more tools (CT-logs, Ssllabs, Sslmate, a Mozilla Cipher check etc.). I think this is a great idea! Are you interested in starting the topic? I would try to pitch in with some links 🙂 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [October 31, 2018, 4:38pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/7 "2018-10-31T16:38:53Z")
> [@cpu](#): > > Are you interested in starting the topic? Yep, I'm writing something. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [October 31, 2018, 4:39pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/8 "2018-10-31T16:39:44Z")
Thank you @JuergenAuer, you’re a huge help! ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [November 1, 2018, 2:46pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/9 "2018-11-01T14:46:41Z")
So, there is the list: Third-party-Tools to check your configuration (closed) > [@Third-party-Tools to check your configuration](https://community.letsencrypt.org/t/third-party-tools-to-check-your-configuration/76272): > > I… And a second thread, if someone has a question or new ideas: Third-party-Tools to check your configuration - discussion > [@Third-party-Tools to check your configuration - Discussion](https://community.letsencrypt.org/t/third-party-tools-to-check-your-configuration-discussion/76354): > > M… ---
**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\ **Post date:** [November 1, 2018, 4:40pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/10 "2018-11-01T16:40:34Z")
@JuergenAuer you didn’t pinned the [Third-party-Tools to check your configuration](https://community.letsencrypt.org/t/third-party-tools-to-check-your-configuration/76272) topic, is it voluntarily? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [November 1, 2018, 5:00pm UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/11 "2018-11-01T17:00:31Z")
> [@tdelmas](#): > > you didn’t pinned the [Third-party-Tools to check your configuration](https://community.letsencrypt.org/t/third-party-tools-to-check-your-configuration/76272) topic, is it voluntarily? Yep, thanks - now it's done. ---
**Author:** ![JAz](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@JAz](https://community.letsencrypt.org/u/JAz)\ **Post date:** [November 5, 2018, 1:46am UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/12 "2018-11-05T01:46:59Z")
Awesome thread guys. Bunch of tools I didn’t know about. Perhaps, if you want the thread to make the most impact, certbot should link to the thread in it’s help messages (instead of tools like [letsdebug.net](http://letsdebug.net), [ssllabs.com](http://ssllabs.com), etc.) That way help messages point to a “living” document instead of one tool. As certbot ages and ppl maybe using older versions, the help messages still point to new/current list of help tools. Also maybe can influence other authors to point to same tools thread. Just a thought. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [December 5, 2018, 1:47am UTC](https://community.letsencrypt.org/t/hint-to-letsdebug-net-in-error-message/76236/13 "2018-12-05T01:47:05Z")
Closed on December 5, 2018, 1:47am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.