[iaoa-infrastructure] Getting a certificate for secure.iaoa.iorg

[Valter Cavecchia]

Dear all,

After a *very long* (and somewhat boring) conversation with the godaddy 
hotline they told me that we have to wait at least 72 hours after the 
old certificate (the one issued by CIM3) was declared as 'expired' or 
'no more valid' before issuing a request for a new one. They also 
suggested me to stay with the self-signed one for the time being (which 
actually is the only option available if we want to have the site up and 
running). To be honest I didn't know at all about this 'timing' problems.

Regards
    valter

On 8/26/2014 3:56 PM, Peter Yim wrote:
>
> Dear Valter,
>
> Since your self-signed certificate is still on the <secure.iaoa.org 
> <http://secure.iaoa.org>> host and it expires on 2024/07/01 (which is 
> about 3600 days away,) the GoDaddy support is probably referring to that.
>
> I suppose their system would do a check to see if the <secure.iaoa.org 
> <http://secure.iaoa.org>> is certified (which it still is, with your 
> certificate.) Therefore, if you just remove that self-signed 
> certificate, then this conflict will be gone, and the system will be 
> able to respond properly to your certificate signing request (CSR).
>
> Good luck! =ppy
> --
>
> On Aug 26, 2014 4:40 AM, "Valter Cavecchia" <valter at science.unitn.it 
> <mailto:valter at science.unitn.it>> wrote:
>
>     Dear Peter
>     I just tried again to request a certificate and got the same
>     result as yesterday. Then I called the godaddy hotline and they
>     told me that a certificate is already active for the iaoa.org
>     <http://iaoa.org> domain and it is due to expire in something like
>     3000 days. In order to proceed we should, in some way, "cancel"
>     the old certificate (maybe this will take some time).  I do not
>     know if something is in conflict with MY self-signed certificate
>     (I have to check this, I thought the new one will simply replace
>     the old...)
>
>       valter
>
>
>     On 8/25/2014 9:04 PM, Peter Yim wrote:
>>     Dear Valter,
>>
>>     Thank you for providing the prompt on this issue.
>>
>>     As it turns out, when we transfer the iaoa.org <http://iaoa.org>
>>     domain from CIM3 to IAOA earlier (at GoDaddy), I did not realize
>>     we needed to "drop" the association of our SSL certificate to the
>>     secure.iaoa.org <http://secure.iaoa.org> host manually ... I have
>>     just done that now.
>>
>>     Please try again. Please let me know if that works ok.
>>
>>     Thanks & regards. =ppy
>>     -- 
>>
>>
>>
>>     On Mon, Aug 25, 2014 at 10:45 AM, Valter Cavecchia
>>     <valter at science.unitn.it <mailto:valter at science.unitn.it>> wrote:
>>
>>         Dear all,
>>         I just tried to get a valid SSL certificate for
>>         secure.iaoa.org <http://secure.iaoa.org>. Following the
>>         godaddy instructions I produced a certificate request on the
>>         server and inserted it on the supplied form. I made the csr with:
>>>         openssl req -new -newkey rsa:2048 -nodes -keyout
>>>         iaoa.org.key -out iaoa.org.csr
>>         However I got an error (This domain already uses an SSL
>>         certificate) as you may see in the picture below.
>>         I will try again tomorrow (at a time when the support hotline
>>         will be active)
>>           valter
>>
>>
>>
>>
>>         _________________________________________________________________________
>>         Msg Archives:
>>         https://listserv.ovgu.de/pipermail/iaoa-infrastructure/
>>         Committee Wiki:
>>         http://ontolog-02.cim3.net/wiki/IaoaInfrastructure
>>         To join:        please email committee chairs or to: info @
>>         iaoa.org <http://iaoa.org>
>>         IAOA website: http://iaoa.org
>>
>>
>>
>>
>>     _________________________________________________________________________
>>     Msg Archives:https://listserv.ovgu.de/pipermail/iaoa-infrastructure/
>>     Committee Wiki:http://ontolog-02.cim3.net/wiki/IaoaInfrastructure
>>     To join:        please email committee chairs or to: info @iaoa.org  <http://iaoa.org>
>>     IAOA website:http://iaoa.org  
>
>
>
>     _________________________________________________________________________
>     Msg Archives: https://listserv.ovgu.de/pipermail/iaoa-infrastructure/
>     Committee Wiki: http://ontolog-02.cim3.net/wiki/IaoaInfrastructure
>     To join:        please email committee chairs or to: info @
>     iaoa.org <http://iaoa.org>
>     IAOA website: http://iaoa.org
>
>
>
> _________________________________________________________________________
> Msg Archives:   https://listserv.ovgu.de/pipermail/iaoa-infrastructure/
> Committee Wiki: http://ontolog-02.cim3.net/wiki/IaoaInfrastructure
> To join:        please email committee chairs or to: info @ iaoa.org
> IAOA website:   http://iaoa.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.ovgu.de/pipermail/iaoa-infrastructure/attachments/20140826/e60042cc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 15855 bytes
Desc: not available
URL: <http://listserv.ovgu.de/pipermail/iaoa-infrastructure/attachments/20140826/e60042cc/attachment-0001.png>