Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running gulp serve gives "ERR_SSL_PROTOCOL_ERROR" error #357

Closed
2 tasks
muges01 opened this issue Nov 4, 2017 · 6 comments
Closed
2 tasks

Running gulp serve gives "ERR_SSL_PROTOCOL_ERROR" error #357

muges01 opened this issue Nov 4, 2017 · 6 comments

Comments

@muges01
Copy link

muges01 commented Nov 4, 2017

I have recently installed new SharePoint framework 1.3.4. Now when i scaffold a new SPFx react solution and run gulp serve (https://localhost:4321/temp/workbench.html), it gives "ERR_SSL_PROTOCOL_ERROR" error.

Category

  • Question
  • [x ] Bug
  • Enhancement

Expected or Desired Behavior

Ability to scaffold SPFx project and run it on HTTPS

Observed Behavior

If i change the serve.json to serve it on http instead of https than it is working but i couldn't load on the https://[domain].sharepoint.com/_layouts/15/workbench.aspx.

Environment Configuration
  • NodeJs - (version 8.9.0)
  • NPM (version 5.5.1)
  • Gulp (version 3.9.1)
  • YO (version 2.0.0)
  • SPFx framework (version 1.3.4)
  • Typescript (version 2.6.1)

Steps to Reproduce

  • Run SharePoint Yeoman generator to create a new SPFx solution using react framework
  • Run gulp serve
  • When it serve to the browser, you will see the following error

This site can’t provide a secure connection
localhost sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR

Thank you
Mugilan

@muges01
Copy link
Author

muges01 commented Nov 5, 2017

Hi everyone,

I found another similar issue been raised under sp-dev-docs ( SharePoint/sp-dev-docs#1013 and SharePoint/sp-dev-docs#1002).

I seems that, the issue is with NodeJs 8.9.0. I have revert back to NodeJs 6.11.5 and i can run gulp serve without any problem.

@waldekmastykarz
Copy link
Member

@muges01 have you tried applying the workaround mentioned in SharePoint/sp-dev-docs#1002?

@muges01
Copy link
Author

muges01 commented Nov 22, 2017

Hi @waldekmastykarz, sorry for the late reply, i didn't see your message until today. I was expecting to receive an email notification when someone comment here.

However, i just tried the workaround by setting the NO_NODE_HTTP2 environment variable to 1 and it's worked. Thank you.

@waldekmastykarz
Copy link
Member

Great to hear you got it to work @muges01

@vasavidurgaprasad
Copy link

I made NO_NODE_HTTP2 environment variable to 1. but it is not working.
I am using SPFx framework 1.8 and Node 10.16.2

@michalhainc
Copy link

michalhainc commented Sep 23, 2019

Hi @waldekmastykarz, for me this doesnt fix the issue as well as like for @vasavidurgaprasad ...

image

my package json:

{
  "name": "helloworld-webpart",
  "version": "0.0.1",
  "private": true,
  "main": "lib/index.js",
  "engines": {
	"node": ">=0.10.0"
  },
  "scripts": {
	"build": "gulp bundle",
	"clean": "gulp clean",
	"test": "gulp test"
  },
  "dependencies": {
	"@microsoft/sp-core-library": "~1.1.0",
	"@microsoft/sp-webpart-base": "~1.1.0",
	"@microsoft/sp-lodash-subset": "~1.1.0",
	"@microsoft/sp-office-ui-fabric-core": "~1.4.0-0",
	"@types/webpack-env": "1.13.1",
	"@types/es6-promise": "0.0.33"
  },
  "devDependencies": {
	"@microsoft/sp-build-web": "~1.1.0",
	"@microsoft/sp-module-interfaces": "~1.1.0",
	"@microsoft/sp-webpart-workbench": "~1.1.0",
	"gulp": "~3.9.1",
	"@types/chai": "3.4.34",
	"@types/mocha": "2.2.38",
	"ajv": "~5.2.2"
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants