<div dir="ltr">If you manually do a DNS lookup from both the failing and non-failing machine, do you get the same IP address for the hostname?<div><br></div><div>Maybe one has something in /etc/hosts that is giving an old/bad address?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 7, 2021 at 6:58 PM Grand Rapids Linux Users Group <<a href="mailto:grlug@grlug.org">grlug@grlug.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Doing more testing with another system that is the same distro, version,<br>
and application (i.e. both run Nagios):<br>
<br>
Original machine Test machine<br>
================ ============<br>
<br>
lynx <a href="http://usam.com" rel="noreferrer" target="_blank">usam.com</a> lynx <a href="http://usam.com" rel="noreferrer" target="_blank">usam.com</a><br>
<fails> <works!><br>
ldd lynx <same library versions!!><br>
<br>
curl <a href="http://usam.com" rel="noreferrer" target="_blank">usam.com</a> curl <a href="http://usam.com" rel="noreferrer" target="_blank">usam.com</a><br>
<fails> <returns the redirect HTML><br>
ldd curl <same libraries & vers!!><br>
<br>
repositories <exactly the same><br>
update status <exactly the same><br>
<br>
My original hypothesis that the problem could be traced to the last<br>
letsencrypt update does not appear valid, as there are other sites with<br>
newer certs that DO work properly.<br>
<br>
As there is no code difference between tools on these two machines, how<br>
can the cause of this site failure be isolated?<br>
<br>
Thanks!<br>
-- <br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="https://shinobu.grlug.org/mailman/listinfo/grlug" rel="noreferrer" target="_blank">https://shinobu.grlug.org/mailman/listinfo/grlug</a><br>
</blockquote></div>