[GH-ISSUE #101] firefox ssl length error #55

New issue

Closed

opened 2026-02-25 22:32:29 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:32:29 +03:00

Owner

Originally created by @brycedorn on GitHub (Jan 7, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/101

hey! thanks for making this - been looking for a local SSL solution for a while so hoping to add this to my workflow. I just added the url to the local url (test.localhost), but getting this error using firefox:

SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

did some digging, and dropping firefox's TLS version from 1.3 to 1.2 (in about:config changing security.tls.version.max from 4 to 3) was a proposed solution, but this didn't work for me. any ideas? I searched issues here and haven't seen anyone else experience this.

Originally created by @brycedorn on GitHub (Jan 7, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/101 hey! thanks for making this - been looking for a local SSL solution for a while so hoping to add this to my workflow. I just added the url to the local url (`test.localhost`), but getting this error using firefox: > SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG did some digging, and dropping firefox's TLS version from 1.3 to 1.2 (in `about:config` changing `security.tls.version.max` from **4** to **3**) was a proposed solution, but this didn't work for me. any ideas? I searched issues here and haven't seen anyone else experience this.

kerem

2026-02-25 22:32:29 +03:00

closed this issue
added the
TLS stack issue
label

kerem commented

2026-02-25 22:32:29 +03:00

Author

Owner

@twhite96 commented on GitHub (Jan 8, 2019):

Having the same issue, both FF and Chrome.

@twhite96 commented on GitHub (Jan 8, 2019): Having the same issue, both FF and Chrome.

kerem commented

2026-02-25 22:32:29 +03:00

Author

Owner

@FiloSottile commented on GitHub (Jan 8, 2019):

Are you running an HTTPS server at test.localhost:443? Sounds like this might be the result of connecting to a plain HTTP server.

Anyway, it's likely this is an issue with the TLS implementation you are using, not with the mkcert certificates.

@FiloSottile commented on GitHub (Jan 8, 2019): Are you running an HTTPS server at test.localhost:443? Sounds like this might be the result of connecting to a plain HTTP server. Anyway, it's likely this is an issue with the TLS implementation you are using, not with the mkcert certificates.

kerem referenced this issue

2026-02-25 22:33:18 +03:00

[PR #55] [CLOSED] Support for CSRs (Certificate Signing Requests) #372