jlorensen Absent Member.
Absent Member.
2302 views

Yet another SSL certificate question

We are trying to get our comodo certificate installed and running for our mobility installation. Here is what I have (and by no means am I certificate/mobility/Linux expert)

I have 3 .crt files... one for the server, one for comodo, and one for an external ca root. Reading the other threads on SSL certs, it looks like you just combine the 3 of them and place them in /var/lib/datasync/device/ and then rename it to mobility.pem. When I do that and restart the datasync services it seems to just shut down. It shows the engines are running, but from the outside I can no longer telnet on port 443. Like I said, total nube, but would like to get this working... any help would be much appreciated... thanks!
Labels (1)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Yet another SSL certificate question

You also need the private key file in the mobility.pem file. Please make
sure to copy the contents of the Private Key at the very top of mobility.pem
file

Before copying remove the password from the private key file using the
following command
openssl rsa -in private.key -out nopassword.key

Regards
MJ

>>> On Wednesday, September 01, 2010 at 12:05 PM, in message

<jlorensen.4gmgnv@no-mx.forums.novell.com>,
jlorensen<jlorensen@no-mx.forums.novell.com> wrote:

> We are trying to get our comodo certificate installed and running for
> our mobility installation. Here is what I have (and by no means am I
> certificate/mobility/Linux expert)
>
> I have 3 .crt files... one for the server, one for comodo, and one for
> an external ca root. Reading the other threads on SSL certs, it looks
> like you just combine the 3 of them and place them in
> /var/lib/datasync/device/ and then rename it to mobility.pem. When I do
> that and restart the datasync services it seems to just shut down. It
> shows the engines are running, but from the outside I can no longer
> telnet on port 443. Like I said, total nube, but would like to get this
> working... any help would be much appreciated... thanks!

0 Likes
jlorensen Absent Member.
Absent Member.

Re: Yet another SSL certificate question

Is the private key something that would have come with the certificate files, or is it something that I need to generate?
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Yet another SSL certificate question

jlorensen wrote:

> Is the private key something that would have come with the certificate
> files, or is it something that I need to generate?


It's something that was generated when you generated the CSR to obtain
the certificate.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Yet another SSL certificate question

When you generated the CSR, it would have created the Private Key for you.

Regards
MJ

>>> On Thursday, September 02, 2010 at 08:36 AM, in message

<jlorensen.4go1mb@no-mx.forums.novell.com>,
jlorensen<jlorensen@no-mx.forums.novell.com> wrote:

> Is the private key something that would have come with the certificate
> files, or is it something that I need to generate?

0 Likes
jlorensen Absent Member.
Absent Member.

Re: Yet another SSL certificate question

OK... so the certificate is up and running (thanks for the help) and mobility was working for most of the day yesterday, but now no one can send email from their device. Everyone can receive, but no send... All of the engines are running and the server has been rebooted... any thoughts?
0 Likes
jlorensen Absent Member.
Absent Member.

Re: Yet another SSL certificate question

jlorensen;2018623 wrote:
OK... so the certificate is up and running (thanks for the help) and mobility was working for most of the day yesterday, but now no one can send email from their device. Everyone can receive, but no send... All of the engines are running and the server has been rebooted... any thoughts?


Installed latest build and that fixed our problems... so far so good.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.