Is it possible to get test access (via HTTPS) to that URL?
On 19 Sep 2016, at 14:35, Moshe Cohen <address@hidden> wrote:
I am on 5.19.0 (the latest)
On Mon, Sep 19, 2016 at 3:03 PM, Martin Pala <address@hidden> wrote:
Which monit version it is? (monit -V)
If you test HTTPS, the ServerNameIndication (SNI) TLS extension may be required, so monit can talk to name based virtual SSL server. Support for SNI was added on monit 5.13.
Best regards,
Martin
> On 17 Sep 2016, at 22:20, Moshe Cohen <address@hidden> wrote:
>
> I have the following url, that when called with https, return 200 as shown here:
>
> > curl -i https://arogacentertest.norbltd2.com:443/checkalive
> HTTP/1.1 200 OK
> Cache-Control: no-cache, no-store, must-revalidate, max-age=0
> Content-Type: application/json; charset=utf-8
> Date: Sat, 17 Sep 2016 20:09:39 GMT
> Content-Length: 0
>
>
> The following Monit test fails :
>
> # Check ArogaCenter is alive
> check host ArogaCenter with address arogacentertest.norbltd2.com
> if failed
> port 443 protocol https
> request /checkalive
> status = 200
> then alert
>
> The log message is:
>
> [UTC Sep 17 20:14:05] error : 'ArogaCenter' failed protocol test [HTTP] at [arogacentertest.norbltd2.com]:443/checkalive [TCP/IP SSL] -- HTTP error: Server returned status 404
>
> Since the response is a 404, it seems the server is reached but for some reason it is looking for another path that does not exist.
>
>
>
>
>
>
>
>