HTTPS resolves somewhere else ?

We have just bound an SSL certicate to our new .NET website at a new host --
   Browsing to "" works fine.
   Browsing to "" gives an error.  

Our web developer uses his Visual Studio debugger, and when he browses to "" he sees "Wordpress" errors being returned.   Our old website was in Wordpress, hosted at another webhost.

I checked our "A" records.  There are 3 ( www, @, *) and they point to the proper IP address (which is a load balancer above our two web servers).

Is there some way to see where "https" is pointing, or why it is getting these weird Wordpress errors?

Rob RudloffIT Development SpecialistAsked:
Who is Participating?
Zephyr ICTCloud ArchitectCommented:
It will be difficult to test if it is impossible to connect to the website, using curl I get a connection refused message.
Maybe it's the load balancer? Which brand is it? Did you open port 443 on your firewall/load balancer?
Rob RudloffIT Development SpecialistAuthor Commented:
We are thinking it is the load balancer.  SSL at this host prefers to be installed on the Load Balancer, rather than the servers.
Zephyr ICTCloud ArchitectCommented:
Rackspace presumably... Good luck!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.