The FTP Problem is back with Hostinger. Its the same scenario. I’m modifying a file and letting my build server deploy it every few minutes as I keep making changes. Suddenly the build fails on FTP, which is confirmed at home using FTP Rush as well. FTP Rush reports the same error about the data channel when trying to get directory contents. Since I changed to a new FTP action on my builds, the process doesn’t hang, but it doesn’t detect the initial problem either. It things my server doesn’t have any files so it hashes every file locally and attempts to create a folder on the FTP server, which then proceeds to fail.

I decided to try my luck with Hostinger help again to see if there is a scheduled maintenance issue. This time I was able to make it past the chatbot.

In a nut shell, their isn’t any scheduled maintenance on my server, and by time someone is able to verify, the problem resolves itself. It seems to happen between 1:30 to 2:00 AM Eastern. I wake up late and work throughout the night. Although the new FTP Action is able to eventually detect a problem, it wastes time hashing all files as if my FTP server doesn’t have anything. I found bug report, posted my findings with various FTP clients when it happens, and a suggestion to fail if the ftp state file isn’t found.

Date	May 30	June 8
Day	Thursday	Saturday
Time Started	1:41 AM	1:51 AM
Time Ended	~2:00 AM	~2:00 AM

FTP is down again. It says “The specified data channel type is not implemented.” when trying to get directory contents. My build server says that Client is closed because Server sent FIN packet unexpectedly, closing connection. Does FTP stop working around the same time every day?

No … this happens from multiple locations at the same time. Its the same error. The last time it happened the FTP server wasn’t working for about 30 minutes, and then came back online for all locations without any configuration changes.

It sounds like the intermittent downtime of the FTP server might be related to server-side issues since it resolves without any changes on your end. Unfortunately, it’s not possible to disable FTP on Web and Cloud hosting plans as it would affect all accounts on the same server. This option is only available on VPS plans.

Since the downtime resolves itself and affects multiple locations simultaneously, it might be a temporary server issue. If this problem continues to occur frequently, it could be worth monitoring the times it happens to identify any patterns or recurring issues.

The pattern seems to be around 2am, or close to it for 30 minutes.

eastern time

It appears there might be scheduled maintenance or server updates occurring around that time, which could explain the consistent downtime around 2 AM Eastern Time. These activities are typically scheduled during off-peak hours to minimize disruption.

Since the downtime is regular and short, it’s likely part of routine server management. If the timing of these downtimes is critical for your operations, you might consider adjusting any automated tasks or workflows to accommodate this window.

That’s pretty much what I’m asking – is there a scheduled maintenance, or is this a problem? Your status page shows that all services are online, so its a bit confusing if I’m tracking down a bug or not.

It seems there isn’t specific information available in our knowledge base about scheduled FTP downtime or maintenance at 2 AM Eastern Time. If the status page indicates that all services are operational, this might suggest that the issue isn’t officially recognized as a service disruption or scheduled maintenance.

Given the regularity and timing of the downtime, it could still be tied to some routine server activity or an unnoticed issue. Since the downtime is brief and occurs regularly at the same time, monitoring the situation while considering any potential server-side activities could be your best approach right now. If this pattern changes or the downtime extends, it might indicate a different issue.

Could you open a ticket to have someone look into it?

I’m now redirecting you to our Customer Success Team for further assistance. A specialist will join our conversation shortly. They’ll have access to our chat history, so there’s no need for you to repeat anything previously mentioned, unless you’d like to provide additional details.

---

Hello! It’s Jeah here, I’m ready to assist you.

Hello. The FTP server problem is back.

It seems to be a regular occurance.

ok. The last time was May 30 at 1:30 am

2:03 am

FTP Data Channel Type

The first screenshot is from my home using FTP Rush. The second screenshot is from the build server on GitHub. The link details the same problem last time when I used a different client that was hanging and burning my minutes.

The problem has just resolved itself when I tried again. It’s great – but, this keeps happening around the same time.

It’s like I upload a file every few minutes, and then for 30 minutes the FTP server doesn’t respond to me manually uploading or the build server. In fact – my build server should have only uploaded 1 file, but because of the directory issue, it wasn’t able to get the .ftp-deploy-sync-state.json file to tell it that only one file had changed.

I really don’t want to transfer to another host.

I just got this plan a few days ago

ftp.periplux.io – it works now. It seems to happen between 1:30 AM to 2:00 AM eastern time. Yes. I just came from bluehost. I don’t want to hunt for another host to move everything.

---

Well, hopefully they’ll figure out whats going on sooner or later. It’s such an odd issue that I haven’t experienced anywhere else before. If I switch hosted locations with Hostinger, I would have to wait 20 days before doing so since you can only change every 30 days. My server is in Massachusetts. The next closest server is in Arizona. The data center in Brazil is between 2,500 to 5,000 miles away and the UK is about 3,500 miles away. I’d have to pinpoint exactly where the servers are, and then play a guessing game with internet routes since it’s not a strait line. I wonder if I could simply ping a server in each location for latency and look at all of the hops involved. The question is – will moving servers really fix the issue, or is this something that goes on with all servers managed by Hostinger? What are the legal ramifications if my server is hosted in another country? It feels like they were just making a suggestion to get me out of their hair. I’ve only been with Hostinger for 10 days and the problem has occurred twice. If the problem persists to the point that it becomes disruptive in work or burning unnecessary minutes on the build server, I may need to change to another host.