|This is the last time your account was accessed.|
06-28-2016 04:01 AM
Again, not really true, as I have been FTP'ing every day this week, to GoDaddy servers and other servers from Verizon Fios.
The problem was just with FTP'ing from Verizon to a particular GoDaddy server. It's the combination that didn't work. FTP'ing from any other ISP to that GoDaddy server worked fine. FTP'ing from Verizon to OTHER GoDaddy servers worked. It's the combination, WITH a particular "older" (as GoDaddy puts it) server of theirs, that didn't work.
06-29-2016 07:52 PM
Let me clarify what Verizon techs are trying to say. FTP as a fundamental protocol on the Intermet is supported by Verizon, from an ISP perspective. Their network has to be able to pass such traffic properly, as well as cooperate with whatever firmware Verizon or their vendors write for the FiOS routers.
Verizon has not supported FTP to the Verizon Personal Web Space in years. This was an old perk Verizon offered, which also does not exist anymore.
06-30-2016 11:33 AM
I hope this helps someone. I had exactly the same problem, but it is now fixed.
I have two GoDaddy hosting accounts on two different servers. On one, FTP/Filezilla worked fine, on the other, it only worked when the Verizon firewall was disabled.
Verizon said the problem was with goDaddy- if I can FTP into one site I should be able to FTP into any site. GoDaddy insisted that FTP was too basic a protocol to work differently on different servers.
Verizon was right. The problem is at GoDaddy.
On another issue, I needed SSH, but the server I was on at GoDaddy did not support user SSH. Enabling SSH meant moving my site files to another server at GoDaddy. And, now, my FTP/Filezilla problem is gone.
The transfer was not without pain, however, because I had to manually move my databases - GoDaddy couldn't or wouldn't do it. That meant back up every database, copy the backup to my local drive, then delete the databases. when the migration was finished, I had to create new databases, restore the data, and change the programs' config files to point to the new database. The whole process took me three days. (I have six subdomains and eight databases).
07-05-2016 12:10 PM
It was WAS fixable on GoDaddy's end. You were right!
The answer was having GoDaddy move me to a diffferent server. I had a "classic" linux server account and apparently those older servers have been blacklisted or blocked or whatever by Verizon. It took about 5 minutes for them to fix it (after two months of hair pulling). I went into my account panel on GoDaddy - clicked on "web hosting" (NOT "manage"). Then clicked on the "Options" button. I selected a paraliel account (no charge) and it was up in less than half an hour (I had no databases to move).
I am FINALLY able to FTP into my site. Thank you for the help!
07-05-2016 12:38 PM
Glad I could help. Now, let the truth be known! No more mystery. Take care and happy "FTP'ing"! :-)
08-20-2016 11:47 AM