question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERR_SSL_PROTOCOL_ERROR when using `gatsby develop --https`

See original GitHub issue

Description

When using gatsby develop --https, I see a lot of ERR_SSL_PROTOCOL_ERROR errors in the console, for what seems to be socket.io related requests. I am using the (currently) latest version of Gatsby.

image

It happens about every 5 seconds, which makes it annoying to use the console to debug other things. The page seems to work fine, and HMR works without issues too, regardless of the errors.

Steps to reproduce

Go to this repo and follow the instructions: https://github.com/Mrtenz/gatsby-https-issue

Alternatively, run this in an existing Gatsby project:

  1. Run gatsby develop --https
  2. Open the page and check the console

Expected result

There shouldn’t be any SSL errors.

Actual result

There are SSL errors.

Environment

  System:
    OS: Linux 5.8 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 3800X 8-Core Processor
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 12.18.3 - /tmp/yarn--1602600057219-0.43846647488335666/node
    Yarn: 1.22.10 - /tmp/yarn--1602600057219-0.43846647488335666/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
  Languages:
    Python: 3.8.6 - /usr/bin/python
  Browsers:
    Firefox: 81.0.1
  npmPackages:
    gatsby: ^2.24.76 => 2.24.76
    gatsby-plugin-canonical-urls: ^2.3.13 => 2.3.13
    gatsby-plugin-create-client-paths: ^2.3.13 => 2.3.13
    gatsby-plugin-layout: ^1.3.13 => 1.3.13
    gatsby-plugin-manifest: ^2.4.34 => 2.4.34
    gatsby-plugin-offline: ^3.2.31 => 3.2.31
    gatsby-plugin-react-helmet-async: ^1.1.0 => 1.1.0
    gatsby-plugin-react-redux: ^1.1.0 => 1.1.0
    gatsby-plugin-robots-txt: ^1.5.3 => 1.5.3
    gatsby-plugin-s3: ^0.3.5 => 0.3.5
    gatsby-plugin-sitemap: ^2.4.16 => 2.4.16
    gatsby-plugin-styled-components: ^3.3.14 => 3.3.14
    gatsby-plugin-ts-config: ^1.1.0 => 1.1.0
    gatsby-plugin-typescript: ^2.4.21 => 2.4.21
    gatsby-plugin-typescript-checker: ^1.1.1 => 1.1.1
    gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.13 => 1.1.13

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:3
  • Comments:16 (9 by maintainers)

github_iconTop GitHub Comments

5reactions
valeeumcommented, Jul 20, 2022

I’m experiencing these issues again but this time on the develop server so the localhost dev server never loads to begin with. The problem doesn’t exist when I reference “gatsby”: “4.14.1” in package.json but does when I specify “gatsby”: “^4.14.1”. Depending on the version of gatsby I install i get one of the following errors:

image image
3reactions
github-actions[bot]commented, Nov 10, 2020

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to enable https for GatsbyJS development server
I'll show you how to self-sign a SSL cert, and run gatsby develop in https. ... If embedded on a site running on...
Read more >
Gatsbyjs Local HTTPS getting browser security errors
When I open https://localhost:8000/ in Chrome I get ERR_SSL_PROTOCOL_ERROR and in Firefox I get Error code: SSL_ERROR_RX_RECORD_TOO_LONG . Any ...
Read more >
Local HTTPS - Gatsby
Gatsby provides a way to use a local HTTPS server during development, thanks to devcert. When you enable the https option, a private...
Read more >
How to Fix the ERR_SSL_PROTOCOL_ERROR - Kinsta
A step-by-step guide on how to fix the ERR_SSL_PROTOCOL_ERROR message. This is typically due to a cached SSL state or misconfigured ...
Read more >
ERR_SSL_PROTOCOL_ERROR: 3 Easy Steps to Resolve It
ERR_SSL_PROTOCOL_ERROR may appear because of an issue with the website's SSL certificate or the client's browser. Although the main reason ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found