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

problem with self signed certificats #71

Open
shayh opened this issue Aug 26, 2014 · 8 comments
Open

problem with self signed certificats #71

shayh opened this issue Aug 26, 2014 · 8 comments

Comments

@shayh
Copy link

shayh commented Aug 26, 2014

I have a self signed certificate on a https site I point the proxy to.
I get the following error:
Fatal error: Parse Error
Fatal error: socket hang up

my configuration is:

proxies: [{
        context: '/api', // the context of the data service
        host: 'my-https-api-site', // wherever the data service is running
        port: 443,
        https: true,
        xforward: true,

      }],
livereload: {
        options: {
          open: {target: 'http://localhost:9000'},
          base: [
        '.tmp',
        '<%= yeoman.app %>'
        ],

please help,
Shay

@lukeman
Copy link

lukeman commented Aug 27, 2014

I think your cert isn't the issue, as this is consistent with what I'm seeing. See #70 for SSL issues with 0.1.11. Downgrading to 0.1.10 worked for me.

@paulsouche
Copy link

Same issue here ! Downgrading worked for me too...

@SyntaxStacks
Copy link

I also had a similar issue where I would get a 400 with the message "HTTP request sent to a HTTPS port". After rolling back to 0.1.10 the error was resolved.

@shayh
Copy link
Author

shayh commented Aug 31, 2014

thanks, it does work in 0.1.10
after digging around it loos like a problem with the underling node-http-proxy that changed it's behavior after a certain version.

@brianmriley
Copy link

+1 worked for me too.

@kaczynskid
Copy link

Thx guys! Took me a while to find this page, but worked like a charm. Had HTTP 400: The plain HTTP request was sent to HTTPS port response and downgrading fixed it!

@hummorsa
Copy link

+1 in the downgrade ! after a day I found this page !

@Stratus3D
Copy link

Thanks everyone. Downgrading to version 0.1.10 worked for me as well.

nkala added a commit to Opetushallitus/osaan.fi that referenced this issue Jan 29, 2018
isaul32 pushed a commit to Opetushallitus/osaan.fi that referenced this issue Oct 24, 2018
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

8 participants