[GH-ISSUE #204] Feature request: Link Check - allow insecure/selfsigned https:// links to be checked #134

Closed
opened 2026-03-15 12:47:29 +03:00 by kerem · 4 comments
Owner

Originally created by @wadabum on GitHub (Nov 1, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/204

My QA-Env. has "real" domains bent back to itself in /etc/hosts, using a self-signed certificate.

  • LinkCheck results in "all errors" with Cannot connect to server
  • DevTools/API reveals this as StatusCode: 0, Status: "certificate signed by unknown authority" in the json-response

As minimal fix, some general "link-check-ignore-https-errors" flag would be nice. (as example Puppeteer´s "ignoreHTTPSErrors")

The ultimate fix would also allow to directly specify the to-be-allowed-certificate/CA
(imagine --link-check-no-verify [false]|true|/etc/ssl/certs/ssl-cert-snakeoil.pem) (as example see Guzzle´s verify options)

Originally created by @wadabum on GitHub (Nov 1, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/204 My QA-Env. has "real" domains bent back to itself in /etc/hosts, using a self-signed certificate. - LinkCheck results in "all errors" with `Cannot connect to server` - DevTools/API reveals this as `StatusCode: 0, Status: "certificate signed by unknown authority"` in the json-response As minimal fix, some general "link-check-ignore-https-errors" flag would be nice. (as example [Puppeteer´s "ignoreHTTPSErrors"](https://devdocs.io/puppeteer/#puppeteerconnectoptions)) **The ultimate fix would also allow to directly specify the to-be-allowed-certificate/CA** (imagine `--link-check-no-verify [false]|true|/etc/ssl/certs/ssl-cert-snakeoil.pem`) (as example see [Guzzle´s verify options](https://docs.guzzlephp.org/en/stable/request-options.html#verify))
kerem 2026-03-15 12:47:29 +03:00
Author
Owner

@wadabum commented on GitHub (Nov 1, 2023):

in addition to that I´ve noticed:

  • HTML screenshots exhibits the same issue (in /proxy?url=... URLs)
    Get "https://...": tls: failed to verify certificate: x509: certificate signed by unknown authority

so when adding a flag for allowing link-checker this should be implemented here too,
-> with either the same --arg-switches or one for each I dont know ;-)

<!-- gh-comment-id:1789210335 --> @wadabum commented on GitHub (Nov 1, 2023): in addition to that I´ve noticed: - **HTML screenshots** exhibits the same issue (in `/proxy?url=...` URLs) `Get "https://...": tls: failed to verify certificate: x509: certificate signed by unknown authority` so when adding a flag for allowing link-checker this should be implemented here too, -> with either the same --arg-switches or one for each I dont know ;-)
Author
Owner

@axllent commented on GitHub (Nov 2, 2023):

@wadabum I am really trying to minimize the number of CLI arguments (and environment variables), so I am in favour of a single generic flag, something like --ignore-tls-errors which one can optionally apply, and be used for multiple things (including SMTP). I need to give this some thought first as it should be clear what it does (and not confuse users).

<!-- gh-comment-id:1790005896 --> @axllent commented on GitHub (Nov 2, 2023): @wadabum I am really trying to minimize the number of CLI arguments (and environment variables), so I am in favour of a single generic flag, something like `--ignore-tls-errors` which one can optionally apply, and be used for multiple things (including SMTP). I need to give this some thought first as it should be clear what it does (and not confuse users).
Author
Owner

@axllent commented on GitHub (Nov 11, 2023):

@wadabum I have added an option for this in v1.10.0 (env MP_ALLOW_UNTRUSTED_TLS or --allow-untrusted-tls). Please confirm this solves your issue?

<!-- gh-comment-id:1806787287 --> @axllent commented on GitHub (Nov 11, 2023): @wadabum I have added an option for this in [v1.10.0](https://github.com/axllent/mailpit/releases/tag/v1.10.0) (env `MP_ALLOW_UNTRUSTED_TLS` or `--allow-untrusted-tls`). Please confirm this solves your issue?
Author
Owner

@wadabum commented on GitHub (Nov 11, 2023):

Working perfectly (for html&linkcheck)
Thank you very much 👌

<!-- gh-comment-id:1806944290 --> @wadabum commented on GitHub (Nov 11, 2023): Working perfectly (for html&linkcheck) Thank you very much 👌
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mailpit#134
No description provided.