×
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.
Excellent! Thanks, everyone. I really wouldn't mind using the newer
tool, and maybe it's as simple as a configuration issue. A cursory
check with the FQDN shows no improvement, but I also note that I'm going
through http:. not https: and maybe that's part of the problem as well.
Now I just have to deal with the SSL stuff. When I tried https:, I got
a secure socket error:
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
So now I have to fight through that.
On 2/24/2021 10:58 AM, Rob Berendt wrote:
Joe Pluta,
I think that Jacob is on the right track. I seem to remember the FQDN from
CFGTCP
12. Change TCP/IP domain information
Being a big thing. Make sure your URL combines Host and Domain name.
And run the suggested QSH script.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.