I called back to the Tier 4 advanced support Monday morning. The "advanced" support person I spoke with did NOT understand what ftp is. I had to explain it to him. He then reported that speed was OK and explained to me about the number of device limitations with their service. When I asked where that was documented for customers, he could not give me any specifics other than to check the HN legal web pages. He did say that he was seeing a large number of packet errors (which do not show up in the modem web page on my end). He decided that it would be best to send a technician out to physically check the system. That tech should come on Wednesday, 9 January. I hope that technician understands about ftp...
HughesNet technician came today. He was awesome (even though he didn't know what ftp was). He saw errors on both the modem AND the dish. He replaced both and now my ftp access is working again. (Hope I'm not speaking too soon again.) For what it is worth, this is my 4th Gen5 modem. The previous ones were each replaced for different problems.
Again, I spoke too soon about ftp working. It worked all day every time I tried after the tech left. Then worked once at night. Then 3 hours later it stopped working. Will see what happens on Wednesday. Looks like I may have to consider Viasat (formerly Exede).
Just out of curiosity, do you know which Gateway you're using? I'm just wondering if it's San Diego, which seems to be having some issues.
You can see in the "IP Gateway Association State" on this page. It will be the three letters after the J1 or J2, as in like mine, which is J2ROS051HNSIGW0104, with the ROS corresponding to Roseburg, OR. You can see the full instructions on how to determine your Gateway on Corrosive's personal site, which is here. The site can take a bit of time to load.
ftp is still hit-and-miss via HughesNet. Had a lot of problems Monday morning. Would get a connection to the ftp server and a directory listing. Uploaded some small files (HTML and JPEG) successfully. Then a few seconds later upload aborted mid-upload. Had a lot of problems getting reconnected. Had to give up.
This morning connected to the ftp server and uploaded several small files. No issues.
Since my modem and dish electronics have been replaced (and my local devices rebooted many times since 15 December 2018), maybe the Gateway needs to be rebooted.
They can't really "reboot" a gateway without knocking everyone on it off air. Doubt they are going to do that.
I'm wondering if they could put you on a different Outroute ID just to see if it makes a difference. I know from experience it can greatly affect an individul's system performance.
What ftp client are you using (if any), and are you using secure (sftp) or regular?
If you're using Filezilla, there's an issue with reconnecting after a curtailed send. Killing FileZilla and restarting it usually fixes the reconnect problem.
I use several ftp apps. On the Macs I use CaptainFTP and Cyberduck. On the iPhone and iPad I use EasyFTP Pro. On one of the Macs I also use a CURL ftp terminal command at times to upload a single char file. Sometimes these all work fine. Other times they all fail. Sometimes one will work when the others fail. But there is no consistency as to what works when. There seems to be no pattern with the failures. Time of day doesn't matter. Happens with multiple computers and handheld devices. BUT doesn't happen when I use the AT&T LTE cell network from the handheld devices.