ERR_SSL_PROTOCOL_ERROR when i try to connect with localhost

Question

I'm beginning to study node js and im trying to connect an ionic app with my backend nodejs app that i have created but im getting this error:

OPTIONS https://localhost:3000/insert net::ERR_SSL_PROTOCOL_ERROR

import { Component, OnInit } from '@angular/core';
import { Http } from '@angular/http';
import { map } from 'rxjs/operators';

@Component({
  selector: 'app-cadastro-unidade',
  templateUrl: './cadastro-unidade.page.html',
  styleUrls: ['./cadastro-unidade.page.scss'],
})

export class CadastroUnidadePage implements OnInit {

  constructor(private http: Http) { }

  ngOnInit() {

  } 

  InsereDados(){
    let data = {
    };

    this.http.post('https://localhost:3000/insert', data).pipe(
            map(res => res.json())
        ).subscribe(response => {
            console.log('POST Response:', response);
        });
  }

}

app.get('/insert', function(req, res, next) {
var uri = "xxxx"
    MongoClient.connect(uri,{ useNewUrlParser: true }, function(err,client){const collection = client.db("test").collection("teste");
    console.log("connected");

    var ins={DataEntrada:"x",DataSaida:"x",HorarioEntrada:"x",HorarioSaida:"x",Prontuario:"x",TipoSaida:"x"};

    collection.insertOne(ins, function(err,res){
      console.log("data inserted");

    })

    client.close();
    })
    res.render(res)
});

Are you running a HTTPS server on localhost / port 3000?

andypotato
– andypotato

2019-09-19 04:27:02 +00:00
Commented Sep 19, 2019 at 4:27 — andypotato
– andypotato, Commented Sep 19, 2019 at 4:27

Steffen Ullrich · Accepted Answer · 2019-09-19 04:55:57Z

18

Port 3000 is commonly used for plain HTTP and not HTTPS and this is likely true in your setup too. It does not magically turn into HTTPS if you use https:// instead of http:// in the URL.

The error messages is a result of your client speaking the wrong protocol (HTTPS, i.e. HTTP over TLS) and that the answer from the server (plain HTTP, without TLS) is not the valid TLS message which is expected by the client - i.e. ERR_SSL_PROTOCOL_ERROR.

`

answered Sep 19, 2019 at 4:55

Steffen Ullrich

125k11 gold badges155 silver badges194 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Muktadir Khan Over a year ago

So how to fix it?

Steffen Ullrich Over a year ago

@MuktadirKhan: If port 3000 is not HTTPS but HTTP then you should not use https://...:3000/... to access it in the code but http://...:3000/... instead.

Washington Guedes Over a year ago

Which port should be used for HTTPS?

Steffen Ullrich Over a year ago

@WashingtonGuedes: "Which port should be used for HTTPS" - ports don't magically turn up to be HTTPS, so the question should not be which port to use but how to configure HTTPS in the server. Then use the port which has HTTPS configured. Common choices are ports with something like 443 in it (like 8443) since 443 is the default port for HTTPS.

Washington Guedes Over a year ago

Actually, port 3000 worked here when I added the https module following this post: github.com/nuxt/nuxt.js/issues/146#issuecomment-273509831 .. my use case is just to test secure cookies for SSO in localhost domains, but thank you for the explanation :)

Collectives™ on Stack Overflow

ERR_SSL_PROTOCOL_ERROR when i try to connect with localhost

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related