NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: lanmicro on August 06, 2008, 10:11:28 AM

Title: Server Connection Failed
Post by: lanmicro on August 06, 2008, 10:11:28 AM
Hi Guys,

Sometimes I get a
"Server Connection Failed

An error occurred during a connection to www.mx247.net.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)"

This message occurs on FireFox (latest version).  Just minutes before attempted same form from IE with no problems.  Using NETTalk v4.24.

Any clues?
Title: Re: Server Connection Failed
Post by: Mike Grigsby on August 07, 2008, 10:27:47 AM
Could it be the same problem Bruce describes having fixed in the next release of NTW? It's discussed in this thread: http://www.nettalkcentral.com/index.php?option=com_smf&Itemid=36&topic=439.0.

Also, if you do a search for FF3 it comes up.
Title: Re: Server Connection Failed
Post by: Bruce on August 07, 2008, 10:43:53 PM
Hi Greg,

The FireFox tip is here:
http://www.nettalkcentral.com/index.php?option=com_smf&Itemid=36&topic=467.0

There's also a thread somewhere (alas I can't find the link at the moment) which recommends not putting 2 web servers on the same window. (As is typically done when one server is SSL, and the other is not). There were some machines (browsers) which got an SSL error when you did this. I'm not sure if this is applicable in your case (the error doesn't look the same).

Lastly - you're still on version 4.24, which was a good build, but beware of getting too far behind. 4.30 is the current "official" build, and 4.31 is nearing release as well. The further behind you get the more likely there are to be "difficulties" upgrading. All these version-to-version issues (and to be fair there aren't many) are documented in the Version History.

Cheers
Bruce
Title: Re: Server Connection Failed
Post by: Alan Telford on August 10, 2008, 12:45:20 PM
Bruce,
It was my issue that had the one app with two servers - 1 HTTPS and 1 HTTP- on the same window. This created error -12263 in the clients browser whenever the request took too long.
The workaround you gave me was to remove the HTTP server, and just use the HTTPS.
And I must say, I haven't seen the error again since then.

So the thread was via email around 14-Mar-08.

Cheers,
Alan