Skip to content

Self signed certificate or invalid certificate not ignored when using client.insecure #1455

@acirep

Description

@acirep

Describe the bug

I have set client.insecure to true on a local network IP address that has synology https certficate. However, gatus is still reporting that IP is down and is not ignoring certificate mismatch.

Am I missing something here?

What do you see?

Gatus reporting local IP as being down

What do you expect to see?

client.insecure to ignore certificate mismatch and proceed.

List the steps that must be taken to reproduce this issue

Add endpoint that is on local network and has certificate that is not matching that configured IP

Version

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions