FAtBalloon's questions

I'm sure I'm just missing a step, but I can't figure out how to get server to resolve to new elastic IP address. I appreciate everyone for their help. I've been trying to figure this out for a while now and can't seem to get it.

This is the response for IP Address 2 when typing IP directly into the browser (New Elastic IP Address)

This is the correct response that I'm getting with IP Address 1

Here's the settings for my instance. As you can see it has IP Address 1 as the public and elastic IP addresses:

Here's the security settings for "WebServerSG" security group.

And here's the elastic IP settings where you can see that IP Address 2 is set to the VPC and the instance and also you can see the private IP address that's referenced as the secondary IP addresses field of my instance details.

I'm setting up server that will host multiple SSL domains across a wide range of load balanced EC2 instances and being a programmer who really sucks at network/infrastructure stuff I had some questions:

I'm assuming that by using ELB I only have to setup HTTPs one time under the ELB and install the certificate there and not on the actual instances?

For SSL, do I still need separate IP addresses for each site when using ELB or does the communication from ELB to the instance run over HTTP?

What's the best way to point the websites to the elb? CNAME record to the amazon ELB instance name?

Should I be using a loadbalancer for this, am I on the right track here?

I am completely open to any other suggestions/help on this issue.

Thank you for your help.

We replaced an old SSL certificate with a new wildcard SSL certificate from GoDaddy. We switched out this certificate last week and have been receiving calls from customers trying to register ever since about the following error.

We cannot figure out what on earth is going on as we have tested this cert in IE 6,7,8, Chrome, & Firefox without receiving any errors, but we know there is a problem as we continue to get calls. For the record, we do have multiple SSL certificates installed on this box, but are using separate IP addresses to serve them up.

Any help or ideas would be greatly appreciated.

Thank you,

We recently switched our SSL certificates on our web hosting environment and the old certificates are still showing up on certain computers with IE installed. It works perfectly fine in both Firefox and Chrome.

On the computers that are having errors, IE is looking at the old SSL cert at *.website1.org instead of the new SSL cert at *.website2.org, thus causing security errors. We've cleared the SSL state in the internet options, removed all cookies/temp files/history/etc.., made sure the time on the computer is correct, and done just about everything we can think of to try and get these computers to view the new certificate.

That all being said, SSL Checker is looking at the old certificate as well, so that's not good obviously.

http://www.sslshopper.com/ssl-checker.html

Forgive me if this has already been answered, but I have looked everywhere.

Basically, we have a store setup on a windows server. However, we want to setup a second area within the website for content and articles, etc.. We want to setup the content area to be a wordpress site on a linux server. How can we configure IIS on the windows server and apache/wordpress on the other server to accomplish this task while using the same domain name?

We want the URLs to look like the following.

http://www.store.com/ http://www.store.com/articles/..

I have setup a SQL Server 2008 Express instance on a dedicated Windows 2008 Server hosted by 1and1.com. I cannot connect remotely to the server through management studio. I have taken the following steps below and am beyond any further ideas. I have researched the site and cannot figure anything else out so please forgive me if I missed something obvious, but I'm going crazy. Here's the lowdown.

The SQL Server instance is running and works perfectly when working locally.

In SQL Server Management Studio, I have checked the box "Allow Remote Connections to this Server"

I have removed any external hardware firewall settings from the 1and1 admin panel

Windows firewall on the server has been disabled, but just for kicks I added an inbound rule that allows for all connections on port 1433.

In SQL Native Client configuration, TCP/IP is enabled. I also made sure the "IP1" with the server's IP address had a 0 for dynamic port, but I deleted it and added 1433 in the regular TCP Port field. I also set the "IPALL" TCP Port to 1433.

In SQL Native Client configuration, SQL Server Browser is also running and

I also tried adding an ALIAS in the

I restarted SQL server after I set this value.

Doing a "netstat -ano" on the server machine returns a

TCP 0.0.0.0:1433 LISTENING UDP 0.0.0.0:1434 LISTENING

I do a port scan from my local computer and it says that the port is FILTERED instead of LISTENING. I also tried to connect from Management studio on my local machine and it is throwing a connection error. Tried the following server names with SQL Server and Windows Authentication marked in the database security.

ipaddress\SQLEXPRESS,1433

ipaddress\SQLEXPRESS

ipaddress

ipaddress,1433

tcp:ipaddress\SQLEXPRESS

tcp:ipaddress\SQLEXPRESS,1433