<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Okay so using a site I know was returning everything correctly in the previous installation, the http task reports the following:</div><div><br></div><div><div>red <a href="https://something.co.uk/">https://something.co.uk/</a> - Bad Request</div><div>HTTP/1.1 400 Bad Request<br></div><div>Server: cloudflare-nginx</div><div>Date: Wed, 08 Nov 2017 10:01:34 GMT</div><div>Content-Type: text/html</div><div>Content-Length: 275</div><div>Connection: close</div><div>CF-RAY: -</div><div>Seconds: 0.002278000<br></div></div><div><br></div><div>Looking at the access logs I can see Xymon hitting the server(s), that looks somethign like this</div><div><br><a href="http://something.co.uk:443">something.co.uk:443</a> 1.2.3.4 - - [08/Nov/2017:06:40:05 +0000] "GET / HTTP/1.0" 400 0 "-" "-"</div><div><br></div><div>If I perform a curl to the URL <a href="https://something.co.uk">https://something.co.uk</a> I get back what I'm expecting, if I perform the curl as <a href="http://something.co.uk:443">something.co.uk:443</a> I receive the 400 error with the message... The plain HTTP request was sent to HTTPS port. This is expected I believe, note that the affected site are all set up to redirect from 80 to 443 and there are no issues with the sites that I have noticed.</div><div><br></div><div>Running xymonnet in the console doesn't really return much...</div><div>
<p class="gmail-p1"><span class="gmail-s1">echo 5.4.3.2 <a href="http://something.co.uk">something.co.uk</a> # <a href="https://something.co.uk">https://something.co.uk</a> | (HOSTSCFG=/dev/stdin /usr/local/xymon/server/bin/xymonnet --debug --no-update --noping --dns=ip )</span></p><p class="gmail-p1"><span class="gmail-s1">Returns:</span></p><p class="gmail-p1"><span class="gmail-s1">
</span></p><p class="gmail-p1">5.4.3.2 <a href="http://something.co.uk">something.co.uk</a><br><br>Any ideas?</p><p class="gmail-p1"><span class="gmail-s1"><br></span></p></div><div><br></div><div><br></div><div><br><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On 7 November 2017 at 21:27, Jeremy Laidman <span dir="ltr"><<a href="mailto:jlaidman@rebel-it.com.au" target="_blank">jlaidman@rebel-it.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Rich<div><br></div><div>All of the SSL checks are enabled by default, so yes, probably related. However check the command-line parameters for xymonnet (in tasks.cfg) to ensure you don't have "--no-ssl" or something like that. I suspect the "400" response code indicates a problem that is also preventing Xymon from processing the certificate.</div><div><br></div><div>Check the web servers' logs to see if they are reporting a fault from the Xymon probe, which might give clues to the cause of the problem.</div><div><br></div><div>Can you provide the exact message that Xymon shows? It may indicate which part of the code is reporting the error, and hence the problem that's triggering it. And what version of Xymon did you upgrade to?</div><div><br></div><div>It might be worth running xymonnet with the "--debug" option, to see if it shows more detail in the xymonnet.log file. You can do some reasonably painless diagnostics by running xymonnet from the command-line, like so:</div><div><br></div><div>echo "1.2.3.4 <a href="http://someurl.com" target="_blank">someurl.com</a> # <a href="https://someurl.com" target="_blank">https://someurl.com</a> COMMENT:somecomment" | ( HOSTSCFG=/dev/stdin /usr/lib/xymon/server/bin/<wbr>xymonnet --debug --no-update --noping --dns=ip )</div><div><br></div><div>This will show you everything xymonnet is doing, but it will only test as per the details in the "echo" command, and it will report its result to you rather than updating the status in Xymon.</div><div><br></div><div>Note that, even though --dns=ip is set here, xymonnet still performs a DNS lookup against the hostname part of the URL to determine where to connect. The debug output will show this. You can force it to connect to a different IP address by using a URL such as <a href="https://someurl.com" target="_blank">https://someurl.com</a>=1.2.3.99.</div><div><br></div><div>J </div><div><br></div><div class="gmail_extra"><div class="gmail_quote"><div><div class="gmail-h5">On 8 November 2017 at 04:16, Richard Jones <span dir="ltr"><<a href="mailto:rich@corporationpop.co.uk" target="_blank">rich@corporationpop.co.uk</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-h5"><div dir="ltr">Hi all,<div><br></div><div>Have finally got around to upgrading our Xymon installation, mostly all good (still some plugins and extensions to add in), however I'm seeing a strange issue where the http test is returning a HTTP/1.1 400 Bad Request for all sites using https. This used to work in our previous (admittedly VERY out-of date) instance. Any ideas?</div><div><br></div><div>Hosts.cfg looks something like this for the affected rows:</div><div><br></div><div>1.2.3.4 <a href="http://someurl.com" target="_blank">someurl.com</a> # <a href="https://someurl.com" target="_blank">https://someurl.com</a> COMMENT:somecomment</div><div><br></div><div>While I'm at it, I can't recall how to get the ssl certificate test to work and show the expiry dates, is this related?</div><div><br></div><div>Cheers, Rich</div><div><div><div class="gmail-m_-623194080138020685gmail-m_-2628078030735834635gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"></div></div></div></div></div></div></div></div></div></div></div>
</div></div>
<br></div></div>______________________________<wbr>_________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman<wbr>/listinfo/xymon</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div></div>