Using 4.4, it was yum-updated roughly one month ago. On Fri, Mar 16, 2012 at 12:41 PM, Douglas Hubler <dhub...@ezuce.com> wrote:
> Are you update 4.4 and have you updated to the latest build. There > were fixes here according to Mircea > > On Fri, Mar 16, 2012 at 11:42 AM, Clayton Gooding > <clayton.good...@gmail.com> wrote: > > Hello > > > > We have a deployment of SipX where we require an SSL certificate to > prevent > > IE users from getting the "There is a problem with this website's > security > > certificate." page/message when they try to log into the user web portal. > > > > I have followed the steps to modify the base files to have SipX generate > a > > 2048 bit CSR and obtained a single site SSL certificate through our > provider > > GoDaddy. I downloaded the files as "apache" which I think is the > > appropriate option? However, when I try to use the GUI to perform the > > upload I have some problems (I also have this problem utilizing other > > download types for GD). > > > > GoDaddy provides a certificate file and a bundle file which apparently > > includes the intermidiate certificate. > > > > These files take the format of: > > > > gd_bundle.crt > > xxxx.xxxx.xxxx.xxxx.crt (where X is the domain/instance we are working > with) > > > > I have been able to upload the "gd_bundle.crt" file successfully through > the > > GUI at SYSTEM>CERTIFICATE>IMPORT WEB CERTIFICATE>KEY FILE>BROWSE/UPLOAD. > > > > But when I try to upload the xxxx.xxxx.xxxx.xxxx.crt file it says > something > > to the affect of "invalid file". Note, this is not a wildcard SSL, it's > a > > unique single site SSL with four sections to the web site name seperated > by > > the period. > > > > Is there some step that I am missing in the GUI in order to get this to > > work, or possibly a different format I should be using when I download > from > > GD? I have reviewed many of the forum posts regarding SSL certs and have > > seen some reference to using command line to modify and replace some > > additional files to bypass the GUI process. But I am very hesitant to > do so > > as the same threads also mention systems suffering some issues due to the > > changes and this is a production system. > > > > Thank you for your time in review. > > > > R > > > > > > _______________________________________________ > > sipx-users mailing list > > sipx-users@list.sipfoundry.org > > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
