Re: [Monit± Protocol test on high port returns 404 even if website is present

[shadow]

Thanks Martin,

for that awesome support. It's working now. Had to do a full monit
reload not only a service monit reload .

Thanks a ton

On 31.05.2017 16:47, Martin Pala wrote:
> Yes, the configuration works for me, debug mode excerpt:
> 
> 'jabber-register-website' succeeded testing protocol [HTTP] at 
> [jabber.systemli.org]:5281/register_web [TCP/IP TLS] [response time 181.739 
> ms]
> 'jabber-register-website' connection succeeded to 
> [jabber.systemli.org]:5281/register_web [TCP/IP TLS]
> 
> 
>> On 31 May 2017, at 16:40, shadow <address@hidden> wrote:
>>
>> Thanks Martin,
>>
>> that's interesting. I see the same behavior with CURL (Get --> Site is
>> present , HEAD --> 404 ).
>>
>> I used your example (reloaded and restarted monit), but the check is
>> still failing. I assume you tested it and the problem is on my side.
>>
>> On 31.05.2017 16:06, Martin Pala wrote:
>>> check host jabber-register-website with address jabber.systemli.org
>>>   if failed
>>>      port 5281
>>>      protocol https
>>>      method GET
>>>      request "/register_web"
>>>      for 2 times within 3 cycles
>>>   then alert
>>
>> -- 
>> best regards | viele Gruesse, address@hidden
>>
>> receive my key:
>> gpg --keyserver zimmermann.mayfirst.org --recv-keys 0x5C6B6ED4248C1F32
>>
>>
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
> 

-- 
best regards | viele Gruesse, address@hidden

receive my key:
gpg --keyserver zimmermann.mayfirst.org --recv-keys 0x5C6B6ED4248C1F32

signature.asc
Description: OpenPGP digital signature