Skip to content

MQTTS Verify=No does not ignore self-signed certificates #802

@skellycode

Description

@skellycode

📣 Notification Service(s) Impacted

  • MQTTS

🐞 Describe the bug

  • Setting the verify flag to 'No' still rejects insecure connections (self-signed certificate)

💡 Screenshots and Logs
image

💻 Your System Details:

  • changedetection.io docker container running on a TrueNAS SCALE host (Debian-based, I think?)

🔮 Additional context

  • I have other services which connect to and use this MQTT server (with the Verify=no argument) so I know the server itself is configured correctly and functioning.
  • I also tried setting the apprise URL to ?verify="/datastore/server.crt" (with correct permissions), however this just defaults to ?verify=No in the debug log.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions