• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Scheduled Pinned Locked Moved General pfSense Questions
7 Posts 4 Posters 4.6k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    TAC57
    last edited by Jan 19, 2019, 10:21 PM

    I was trying to change my cable modem and was having trouble so I went back to the original. Now after re-powering all my devices I get the following when trying to log into my pfSense box. I am running 2.4.4-RELEASE-p2.

    An error occurred during a connection to 192.168.30.1:441. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    I can get out to the internet just find on my computer(s) but not into my pfSense box.

    Anyone have any ideas?

    Thanks,
    -TAC

    G 1 Reply Last reply Jan 21, 2019, 8:37 AM Reply Quote 0
    • T
      TAC57
      last edited by Jan 20, 2019, 9:23 AM

      This fixed it:

      The web server is sending non-secure (HTTP) data where secure (HTTPS) data is expected by Firefox. This can be confirmed by going to http://server-name:443 instead of https://server-name.

      1 Reply Last reply Reply Quote 0
      • G
        Gertjan @TAC57
        last edited by Jan 21, 2019, 8:37 AM

        @tac57 said in Error code: SSL_ERROR_RX_RECORD_TOO_LONG:

        An error occurred during a connection to 192.168.30.1:441. SSL

        Check your port number : 441 seems very non-default to me.

        @tac57 said in Error code: SSL_ERROR_RX_RECORD_TOO_LONG:

        This can be confirmed by going to http://server-name:443 instead of https://server-name.

        How is this server related to pfSense firewall/router ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • T
          TAC57
          last edited by Jan 21, 2019, 12:03 PM

          I was getting this error when logging into my pfSense box, IP 192.168.30.1:441. When I changed from https:// to http:// I could get in.

          1 Reply Last reply Reply Quote 0
          • G
            Gertjan
            last edited by Jan 21, 2019, 12:51 PM

            So you set the port number to "441" instead of the default "443".
            Ok, why not. But, btw : why ?
            In that case you can not use "https://your.pfsense.tld" which default to "https://your.pfsense.tld:443" (your browser will use port 443 if you didn't gave supplied one in the URL like "https://your.pfsense.tld:443").

            This means the "error" you saw is normal. If you set another non default port number, you should use it in every URL without exceptions.

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            1 Reply Last reply Reply Quote 0
            • C
              comparecheapssl Banned
              last edited by Aug 30, 2019, 6:14 PM

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • S
                stratcat
                last edited by Nov 13, 2023, 12:54 AM

                2e3017cc-7fd4-4fca-8014-f09df9ddbf2a-image.png

                I had this happen to me recently after a power outage.
                For some reason it changed the webConfigurator protocol to http/
                I logged in using http and my custom port and changed it back to https/

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received