# Error: Hostname/IP doesn't match certificate's altnames
**URL:** https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837
**Category:** General
**Tags:** security
**Created:** [7 December 2022 21:23 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837 "2022-12-07T21:23:44Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@benhelps](https://discourse.nodered.org/u/benhelps)
#### Post date: [7 December 2022 21:23 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837/1 "2022-12-07T21:23:44Z")
Recently I started getting the below from an external endpoint.
"Error: Hostname/IP doesn't match certificate's altnames: "Host: [wap.tplinkcloud.com](http://wap.tplinkcloud.com). is not in the cert's altnames: DNS:rbictg.com, DNS:\*.rbictg.com""
I presume it most likely they've done something dumb at their end, however in any case for the moment my intent is assume they'll eventually fix it ans to set node-red to ignore the errors and process anyway.
But, how?
I've tried
NODE\_TLS\_REJECT\_UNAUTHORIZED=0
and then
pm2 stop node-red
pm2 start node-red
to no avail. Ideas?
(I saw an earlier post on here with similar issue but no outcome)
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [7 December 2022 22:41 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837/2 "2022-12-07T22:41:13Z")
Assuming this is caused by using an http request node, you can set `rejectUnauthorized` to `false` to ignore certificate errors, although this is not recommended, unless tplink is actually changing to rbictg.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [8 December 2022 09:36 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837/3 "2022-12-08T09:36:40Z")
In these cases, you should always check the certificate details. It could indicate that something has intercepted your link and substituted the cert.
This can happen if you are on a corporate network and the organisation is monitoring connections. But, of course, there are also more nefarious reasons too.
---
### Author:  [@benhelps](https://discourse.nodered.org/u/benhelps)
#### Post date: [8 December 2022 20:24 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837/4 "2022-12-08T20:24:16Z")
Thanks, `rejectUnauthorized` false in the previous node solved that issue, however I no longer trust those devices (and it now returns a 503) so I'll replace them with another type.
I feel like kasa have likely abandoned that endpoint. The tapo brand ones still work (and via talking to the local IP).
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [22 December 2022 20:25 UTC](https://discourse.nodered.org/t/error-hostname-ip-doesnt-match-certificates-altnames/71837/5 "2022-12-22T20:25:15Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.