Re: Configure new Navigator for TLS but doesn't come up on TLS port -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Configure new Navigator for TLS but doesn't come up on TLS port
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 17 Jan 2024 08:15:43 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Wed, Jan 17, 2024 at 6:49 AM Pete Helgren <pete@xxxxxxxxxx> wrote:

Interesting. I just did the same over the weekend. I am on 7.5 and
followed the "Select an existing certificate from the *SYSTEM keystore"
since I already use LetsEncrypt for pretty much everything. However,
the server instance came right up. I kept both the secure and insecure
instances running, just in case the secure option didn't work.

What approach did you take?

Pete, that's what I did.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Configure new Navigator for TLS but doesn't come up on TLS port , stefan

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.