>An error occurred during a connection to 192.168.1.252. > >SSL received a record that exceeded the maximum permissible length. > >(Error code: ssl_error_rx_record_too_long)
Are you sure you did not connect via HTTPS? I always see this error when connecting the IP via https if I do not enter the right port and subfolders in the address. (https:192.168.1.252 instead of https://192.168.1.252:8443/sipxconfig) Rene 2010/4/20 Todd Hodgen <[email protected]> > I have an issue where I can no longer get access to sipxconfig via a > browser, either with the domain name or with the IP address. I can access > with Putty and WinSCP. Here is the scenario, which I repeated to ensure I > didn’t so something wrong. > > > > 2nd time this failed – > > Fresh 4.0.4 install from Iso. > > Restored backup from working system. > > Restoral was flawless with exception of aa recordings not restored – known > issue in 4.0.4 > > Updated etc/yum.repos.d/sipXecs.repo to remove all 5.2 and replace with 5 > in Centos lines > > Ran yum update –y > > Updated with no error. > > System was working fine for today. > > I configured instant message items, can’t recall anything else I played > with. > > Later, when I tried to access sipxconfig via Internet Explorer 8 (latest), > I error out. “Internet Explorer cannot display the page”. I tried with > Chrome 4.1.219 (latest), and had an error “Invalid Server Certificate” > > > > Firefox 3.6.2 returned the following – > > Secure Connection Failed > > > > An error occurred during a connection to 192.168.1.252. > > > > SSL received a record that exceeded the maximum permissible length. > > > > (Error code: ssl_error_rx_record_too_long) > > > > * The page you are trying to view can not be shown because the > authenticity of the received data could not be verified. > > > > * Please contact the web site owners to inform them of this problem. > Alternatively, use the command found in the help menu to report this broken > site. > > > > > > > > SO, AFTER ALL OF THIS, it started working again with Firefox only. I tried > to clear the errors from firefox so I could forward the exact errors, and it > magically started working again. However, it comes up only in Firefox, and > not IE8 or Google Chrome. > > > > > > I’ve had this same problem twice now, so I suspect it’s not a fluke. I > have a few things I want to try to fix the problem but wanted to provide the > correct files to demonstrate what has gone wrong for the developers to have > for troubleshooting. I was going to start with rebuilding the certificate. > > > > Any files of value on the system to provide for testing and reproducing > this issue? Any suggestions as to what it might be besides the security > certificate? > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
