This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

HTTPS hostname wrong: should be 1.2.3.4  RSS feed

 
Jeremy Thornton
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I'm trying to post data to a secure webserver. If I run the webserver and my client application on the same box then all is ok (using a key created for localhost).
If I generate a key for the webserver for my IP address and then try to hit it from another machine, the handshake seems to go ok until I get a
"HTTPS hostname wrong: should be <my ip address>" (where my ip address is my actual IP address.
In the past when I've seen this error it has been followed by
", but cert says <host>" or something similar.
The IP address used in the public key seems to match the IP I'm specifying as the address "https://my ip address:442/testwebserver".
I'm confused... any suggestions?
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!