Search results

I can buy that. So, that being said, in the future, I will generate the CSR prior to setting up additional domain aliases. Maybe that will do the trick.

Stephen, I'm very impressed with your dedication. I don't know what caused the problem, but you stuck with it and for that I thank you tremendously. Are there any takeaway points for this; lessons I should have learned, a better way to do the SSL?

What if you manually generated the CSR and installed a newly created SSL manually (not from hsphere)? If you can send me the CSR I will "rekey" (GoDaddy terms) a new SSL and send it back.

Should I try to regenerate the CSR and start all over, for the third time?

Server move and a total do-over? What I'm trying to do here is not uncommon, right (secure a domain with multiple "aliases" pointed to it)? Are the aliases even a consideration?

It fails for me in the latest Safari, Chrome, FireFox, and IE. Yesterday it worked in Safari, but no longer.

Just their basic (cheapest) SSL.

Yeah, that could be a big problem. They publish email addresses on one of the other domains, so I can't disable all of them to test. Any ideas?

Would it make sense to just move this application to another server (win29) and remove the static IP to start all over again? I didn't have any problems on win29 with another account and a GoDaddy cert.

I didn't receive any errors. It went in fine, a little quicker than I would expect, but fine nonetheless.

To eliminate code loop possibilities, I pushed out a plane HTML page: https://[domain name].com/test.htm It works fine when https is not used: http://[domain name].com/test.htm Here is what ExpertsExchange.com says about this error: You cannot use shared host headers with SSL on the same port...

Thanks for the reply, Stephen and please forgive my bluntness here, but you're telling me things we both already know. The process we went through should have worked. It actually should have worked three days ago when I did it the first time, but it didn't. Now my client is uncomfortable with...

Thanks for your help. Unfortunately, it did not solve the problem. We're going in circles. I did as you suggested and disabled the SSL support. I then re-enabled it and generated a new "self signed CSR". I used that CSR to "rekey" the SSL at GoDaddy. I then went back in to the SSL settings in...

I called back to talk to GoDaddy's support department. She dug further into the issue and determined that you guys are using a certificate issues on 3/12 which was definitely revoked since you asked me to reissue a new one. She said the most simple thing to do is completely remove everything to...

I'm at my wit's end here. Godaddy says it's not their fault and Jodo says it's not their fault. What am I to do?

This information is also in the ticket, but I wanted to post it here as well in case anyone else has the same issue. I just got off of the phone with GoDaddy support. They said the certificate is not fully installed on the server and that it is definitely NOT revoked. The most likely cause is...

Thanks.

I've been trying to work with the support department on setting up a GoDaddy SSL for two days now. The first issue is that the GoDaddy intermediate certificate was not installed on Win27. Then, as soon as that was installed it worked for a few hours and then I was told that the client...

As of today, localhost is no longer working for outgoing mail for this project. I have a support ticket entered (#CNV-16028-717).

For anyone interested in the "solution", here goes. Port change through web.config for mail settings only works in full trust. Jodo doesn't allow full trust on shared environments. To get around this, I used the "localhost" mail server to send the outgoing mail. This website is only sending...