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

Comments

Projects
None yet
8 participants
@shayh

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

This comment has been minimized.

Show comment
Hide comment
@lukeman

lukeman 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.

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

This comment has been minimized.

Show comment
Hide comment
@paulsouche

paulsouche Aug 27, 2014

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

paulsouche commented Aug 27, 2014

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

@SyntaxStacks

This comment has been minimized.

Show comment
Hide comment
@SyntaxStacks

SyntaxStacks Aug 29, 2014

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.

SyntaxStacks commented Aug 29, 2014

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

This comment has been minimized.

Show comment
Hide comment
@shayh

shayh 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.

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

This comment has been minimized.

Show comment
Hide comment
@brianmriley

brianmriley Oct 10, 2014

+1 worked for me too.

brianmriley commented Oct 10, 2014

+1 worked for me too.

@kaczynskid

This comment has been minimized.

Show comment
Hide comment
@kaczynskid

kaczynskid Feb 23, 2015

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!

kaczynskid commented Feb 23, 2015

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

This comment has been minimized.

Show comment
Hide comment
@hummorsa

hummorsa Mar 24, 2015

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

hummorsa commented Mar 24, 2015

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

@Stratus3D

This comment has been minimized.

Show comment
Hide comment
@Stratus3D

Stratus3D Apr 9, 2015

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

Stratus3D commented Apr 9, 2015

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment