# Connection to HTTPS Server
**URL:** https://discourse.nodered.org/t/connection-to-https-server/68089
**Category:** Developing Nodes
**Tags:** docker, http-request, security
**Created:** [22 September 2022 18:14 UTC](https://discourse.nodered.org/t/connection-to-https-server/68089 "2022-09-22T18:14:46Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@andavin](https://discourse.nodered.org/u/andavin)
#### Post date: [22 September 2022 18:14 UTC](https://discourse.nodered.org/t/connection-to-https-server/68089/1 "2022-09-22T18:14:46Z")
I'm attempting to run an HTTPS request to an integrated server using a self-signed certificate within a docker compose environment.
The http request node is to `https://container_name/api/v2/`.
`Enable secure (SSL/TLS) connection` is checked with a blank TLS configuration.
The issue is that when I go to make a simple request I consistently get this error:
```auto
RequestError: write EPROTO 140190209620816:error:14094417:SSL routines:ssl3_read_bytes:sslv3 alert illegal parameter:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1545:SSL alert number 47
```
I'm assuming this has something to do with the self-signed certificate because if I simply change the URL to `https://google.com`, I get a response.
In addition, if I run an HTTPS request manually, outside of NodeRed, then I do get a response at `https://localhost/api/v2/`.
Note that I have to use HTTPS because this server will serve other clients as well.
I'm not sure if the issue is with NodeRed not trusting the certificate, the way I'm signing the certificate or with Docker networking.
Does anyone have insight on this error or what is causing the specific issue?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [21 November 2022 18:15 UTC](https://discourse.nodered.org/t/connection-to-https-server/68089/2 "2022-11-21T18:15:06Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.