Http 425 error

HTTP response status code 425 Too Early is a client error that is returned by the server to indicate that it has received the request but is not going to process it because there is a risk of it being replayed.

This status code is not cacheable by default, as its message body is not the representation of any identified resource.

Usage

When the 425 Too Early error message is received, it may be related to the time required to secure an HTTPS connection. In particular, when there is a great deal of latency, the time required for TLS to create a secure connection can be lengthy. One of the ways for a client to optimize this is by sending data early in the process, in advance of the secure connection being set up.

If there is an intermediary involved in the chain then it must include the Early-Data: 1 request header. Similarly, an intermediary must not remove it. This not only notifies the server that the request has been sent in early data, but also that the client understands the meaning of the 425 Too Early response.

Request

GET /tech-news HTTP/1.1
Host: www.example.ai
Early-Data: 1

It is not necessary for the original initiator of a request to send this header. Simply by sending data early, it implies that the client understands the consequences of doing so, and can deal with the 425 Too Early response appropriately.

Sending early data may be unfavorable in certain situations, and in response, the server will return this error message. The risk is that the client request may be replayed, which can lead to side effects that compromise security.

When a client receives this status code, it can automatically retry the request, although it must wait until after the handshake is complete and the secure connection is in place.

Example

In the example, the client requests a resource and the server responds with the 425 Too Early response, instructing the client to wait until after the connection is fully set up before retrying the request.

Request

GET /tech-news HTTP/1.1
Host: www.example.ai
Content-Type: application/xml
Content-length: 225

<Message includes early data>

Response

HTTP/1.1 425 Too Early

Code references

Go

http.StatusTooEarly

Symfony

Response::HTTP_TOO_EARLY

Python3.5+

http.HTTPStatus.TOO_EARLY

Apache HttpComponents Core

org.apache.hc.core5.http.HttpStatus.SC_TOO_EARLY

Angular

@angular/common/http/HttpStatusCode.TooEarly

Takeaway

The 425 Too Early status code is a client error that is sent by the server in response to the client sending a request in advance of a secure connection being established. If the server does not support early data, then this error will be returned.

See also

• RFC 8470

Introduction[edit]

This is a How-to guide on how to set up your router with FileZilla Server (FZS) in order to fix the error code 425.
There is a Wiki on Network Configuration that covers this information, however, it is written in such a way that the “layman” may have difficulty understanding what’s going on—and it doesn’t show exactly how to fix the 425 error code—so this Wiki will give instructions on how to set up your specific router.

”Abstract”[edit]

This Wiki will go over the common technical reason(s) for error 425 being given after the FZS sends the 227 Passive command to the FTP client—regardless of what client is being used. This Wiki is written for the common user in a narrative tone—if a more in-depth technical Wiki is desired refer to the Network Configuration article.

Narrative[edit]

So, you’ve set up your FZS and it works for a local connection in your home, BUT you want to make your Local FTP Server accessible when you’re away—and you want to use encryption (FTP over TLS) to do so. You set up a Dynamic DNS (DynDNS) service to point to your FZS via your external IP address (don’t worry I’ll explain later in the Wiki). You’ve followed a how-to on setting up FZS to use TLS, but you’ve run into an issue—and after looking at the FZS Log you see the problem—right after the «227 Passive command» is given and acknowledged you see a 425 error. But even after summoning a Warlock, a Witch, and a Unicorn—you can’t fix it and wind up here reading this Wiki.

The Problem[edit]

More than likely the problem is that your FZS is requesting the FTP Client to use the Passive Ports defined in the FZS settings. And even though you’ve changed the settings in your Windows 7 or 8 Firewall you still can’t get your FTP Client to connect.
Why? Well it’s complicated; the type of encryption that FZS uses doesn’t allow the router to “see” that you’d like to allow this communication, and thus the router blocks the data from being transferred. There are other programs you can use that would allow the router to see that a computer requested the information to come in, but you’ve configured FZS thus far, and in many ways it’s better that no one knows what this data is at all—it is your private information after all.

Why the Router?[edit]

OK, so I know that this Wiki isn’t supposed to get too technical, but some of you might be curious as to how the router works, and why it’s doing what it is.

The Router is an important part in your Network security. Some say it’s the first line of defence against hacking and the last line of defence against Trojans/Viruses leaving with your private data—others say it’s a magic box connecting you to the world using sorcery—all of these are true.

The router takes one IP address and allows many devices to connect to the Internet using a complex protocol called Network Address Translation (NAT). Each time a computer requests information, such as going to “Google,” it puts it in a “packet” (think of an envelope) that the router opens, looks for an address, and then sends it to the Google web page, and in turn the Google web page sends a packet back with the information that opens up in your browser—only first the Router again opens the return packet to make sure that someone inside your private network requested it, and then sends it to the appropriate computer.

What if a packet comes in that no one requested? The Router puts it in the “trash”—in technical terms, the Router “drops” the packet. This keeps bad stuff out, and allows only what you’ve asked for to come in.

So what does this mean for this application? As stated above FZS uses an encrypted protocol to receive data. The Router can’t see that the encrypted data “packets” are “OK” to let in on the ports they are coming in on, and thus thinks that a hacker is trying to break in because those ports are closed.

At this point you can think whatever you want, like «well when I shut off the TLS portion of the service it works, so why don’t we change the type of encryption?» or whatever else you might come up with—but after all the work you’ve done so far, why give up now when there’s an easy fix? And there’s the pesky fact that you can’t change the type of encryption that FZS uses (what a drag…).

“So how do we know it’s the router?” You might ask. Take a look at the following Log, and the explanation below it.

Sample 425 error Log[edit]

According to your logs (Logs WILL vary so keep reading) you see:

1. (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> Connected, sending welcome message…
   • (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> TLS connection established
   • (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> HOST **********.mooo.com
   • (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> 500 Syntax error, command unrecognized.
2. (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> USER RCSTEST
   • (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> 331 Password required for rcstest
   • (000015)12/28/2013 20:43:55 PM — (not logged in) (72.174.118.74)> PASS *********
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> 230 Logged on
   • *Output Omitted*
3. (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> AUTH TLS
   • *Output Omitted*
4. (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> MKD Cobian Backup 11 test directory-2013-12-28 20;43;42
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> 257 «/Cobian Backup 11 test directory-2013-12-28 20;43;42» created successfully
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> CWD Cobian Backup 11 test directory-2013-12-28 20;43;42
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> 250 CWD successful. «/Cobian Backup 11 test directory-2013-12-28 20;43;42» is current directory.
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> PWD
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> 257 «/Cobian Backup 11 test directory-2013-12-28 20;43;42» is current directory.
   • *Output Omitted*
5. (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> PROT P
   • (000015)12/28/2013 20:43:55 PM — rcstest (72.174.118.74)> 200 Protection level set to P
   • (000015)12/28/2013 20:43:56 PM — rcstest (72.174.118.74)> PASV
   • (000015)12/28/2013 20:43:56 PM — rcstest (72.174.118.74)> 227 Entering Passive Mode (84,25,240,74,206,88)
   • (000015)12/28/2013 20:43:56 PM — rcstest (72.174.118.74)> STOR Test file.txt
6. (000015)12/28/2013 20:44:06 PM — rcstest (72.174.118.74)> 425 Can’t open data connection for transfer of «»
7. (000015)12/28/2013 20:44:17 PM — rcstest (72.174.118.74)> QUIT
   • (000015)12/28/2013 20:44:17 PM — rcstest (72.174.118.74)> 221 Goodbye
   • (000015)12/28/2013 20:44:17 PM — rcstest (72.174.118.74)> disconnected.

So here’s what’s going on:

1. The FTP Client (Cobian Backup 11 in this case) is establishing a connection with the FZS using standard ports 21 (non-encrypted) or 990 (encrypted) depending on your setup.
2. The FTP Client is now providing the FZS with a username and password.
3. The Server and client now establish that TLS must be used for further communication.
4. The FTP Client is requesting that a folder be created. FZS creates the folder, etc. (boring stuff).
5. Now FZS and the FTP Client enter Passive Mode (code 227)
   • The FZS tells the FTP Client that the passive ports are located at «(84,25,240,74,206,88).»
   • Decoded this translates to IP address 84.25.240.74 (the first four set of numbers) port number 52824 (the last two sets of numbers equated as: 206*256=52736, and 52736+88=52824 #Mathisfun).
6. Here’s where the 425 «error» is given
7. This last bit is what’s frustrating you, the connection is ending without any data being transferred…

Again, your output will vary in all aspects.

We Found the Problem, Now What?[edit]

The Fix: In the router you’ll need to open these ports for the encrypted traffic.
Now on to the exciting part if you have no idea how to do this! Look for your brand of router below, if it’s not listed ask me to list it, and I’ll do my best!

DynDNS Explained[edit]

• Note: You’ll want to pay close attention here.

So what about this whole “DYNDNS” thing? For those of you who don’t know what this is, it’s a service that you can set up to point internet traffic to your computer when your external IP address is “Dynamic” or changes from time to time—as is the case with most public IP Addresses given by your Internet Service Provider (ISP). The set-up of such service “can” be free with a little work, but this falls outside the scope of this article at this time, another article will explain this in the future.

External IP Address[edit]

Your external IP address is the address given to you by your ISP. It should not in any way resemble your server’s IP address, or the IP address of any computer on your network.
For the purpose of this Wiki we will not address the Subnet Masks, as it’s not relevant to this topic.

Internal vs. External IP Address[edit]

The internal “Private” IP address of a Network “usually” starts with 192.168.X.X (where “X” can vary), and is assigned to your computer(s) so they can talk to the Internet via the external “Public” IP address. The external address can be anything in all reality, for this Wiki we’ll pretend the outside address is 84.25.240.74.

Device Specific Instructions[edit]

Please send a request for your device to be added if you don’t see it, and we’ll do our best to add it.

Apple Airport Extreme[edit]

1. Under the Network tab of the Airport Utility there’s a section titled «port settings.»
2. Click the «+» button to add a setting, either select «FTP access» from the dropdown, or add it.
3. Under both «Private TCP ports» and «Public TCP Ports» put in 21 (standard FTP Port).
   • Note: You do NOT need to allow UDP ports as they are not used for FTP.
4. Under Private IP address type the IP address of the destination computer (FTP server).
   • Note: setting a static IP address on the FTP server is strongly suggested.
5. Repeat step 3 and allow port 990 (standard TLS port).
6. Repeat step 3 one last time and
   • Under the TCP ports fill in the range of the FZS passive ports: i.e. «60000-65000» just like that.
   • Use your FZS ports. No spaces, no other characters.
7. Apply the settings to the router, and allow it to reset.
8. Test the connection.