[GH-ISSUE #130] Secure connection failed #78

New issue

Closed

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

kerem commented

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

Owner

Originally created by @iampeterbanjo on GitHub (Feb 5, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/130

I tried using mkcert with these steps

Install mkcert CA and certificates

mkcert -install 
mkcert "*.site.localhost" site.localhost localhost 127.0.0.1 ::1

open Firefox and go to https://localhost

But then I got the error

Secure Connection Failed
An error occurred during a connection to localhost:8080. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.

Originally created by @iampeterbanjo on GitHub (Feb 5, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/130 I tried using `mkcert` with these steps - Install mkcert CA and certificates ``` bash mkcert -install mkcert "*.site.localhost" site.localhost localhost 127.0.0.1 ::1 ``` - open Firefox and go to https://localhost But then I got the error > Secure Connection Failed > An error occurred during a connection to localhost:8080. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG > The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. > Please contact the web site owners to inform them of this problem.

kerem

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

closed this issue
added the
TLS stack issue
label

kerem commented

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

Author

Owner

@FiloSottile commented on GitHub (Feb 5, 2019):

Are you actually configuring your server to use the certificates and support HTTPS? That looks like the server is trying to answer with plain HTTP.

@FiloSottile commented on GitHub (Feb 5, 2019): Are you actually configuring your server to use the certificates and support HTTPS? That looks like the server is trying to answer with plain HTTP.

kerem commented

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

Author

Owner

@iampeterbanjo commented on GitHub (Feb 5, 2019):

Thanks for the quick response.

I'm using a Node.js server and I've done export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem".

Is that enough?

@iampeterbanjo commented on GitHub (Feb 5, 2019): Thanks for the quick response. I'm using a Node.js server and I've done `export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"`. Is that enough?

kerem commented

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

Author

Owner

@FiloSottile commented on GitHub (Feb 5, 2019):

No, that's sufficient to configure clients to trust mkcert certificates, not to configure servers to use them. I'm afraid I can't help you configure your server as I know next to nothing about the Node.js ecosystem, sorry.

@FiloSottile commented on GitHub (Feb 5, 2019): No, that's sufficient to configure clients to trust mkcert certificates, not to configure servers to use them. I'm afraid I can't help you configure your server as I know next to nothing about the Node.js ecosystem, sorry.