Too long? - Basically: if you are using the correct password and username and you still get FTP client errors, it is likely there are FTP node issues - simply wait it out. You can confirm this by using the files.000webhost.com file manager if you get “Log in details not correct” and you are 100% sure you’ve got the correct username and password - this indicates there are FTP node issues - there is nothing to do apart from waiting sadly be it hours or days. Thank you.
While you shouldn’t have to unfortunately there are a lot of users on the free network which impacts File Manager / FTP accessibility sometimes and you can troubleshoot it easily.
If you join our Discord server you can use the #uptime-monitor to get live information on FTP issues, if any nodes are facing high traffic you’ll know why you can’t get connected.
Head to 000webhost.com > Website Settings > General and you’ll see the page that displays your correct username and the option to toggle it off/on - it won’t hurt to try this.
If you browse down a bit more you’ll see the Repair button, give this a hit and wait a few minutes before connecting to File Manager / FTP again.
If you manually visit files.000webhost.com you get “Log in details are not correct” then login to 000webhost.com and use the link login automatically to File Manager, if you get the error again then it is likely there are FTP issues.
You can change your password via General Settings and wait five minutes then try to log in again, if you again get the message it is likely there are FTP issues.
Using an FTP client to test the details you’ll likely get other errors but if you get a 530 then it generally means the password is BAD.
Your main FTP login details are listed in your Settings > General while logged into 000webhost.com
Your username for FTP is always the part before 000webhostapp.com in your URL for visiting your website.
The hostname is always files.000webhost.com, the password can be reset via General Settings page on 000webhost.com
This can be a number of things but we can troubleshoot it first by making sure we are using the correct hostname of files.000webhost.com, failing that we can try using a VPN network, if we can get access via that then something is blocking your access locally on your computer, network or further up the line at your ISP.
We can try using alternative DNS to see if this resolves anything and failing that you can revert to a proxy or VPN until you figure out what local issue is affecting you (sometimes it resolves by itself if a routing issue is fixed along the way for example)
Can be a number of things again but by making sure the hostname is 100% correct, then we can check the port number of 21 to see if it works by using that, if not then try using a proxy or VPN, if that succeeds there may be something blocking you locally or the server is busy - try again later.
"FTP connection timed out"
This is normally a local connection issue be it a firewall on your computer, router or further up the network if you are on one or your ISP may be affecting your connection via FTP. Try using a proxy or VPN, if this solves the issue contact your ISP to see if there is any issues with using port 21 or FTP to remote connect to your files.
FileZilla options to test if you are failing to connect to files.000webhost.com
"421 Too many connections, 421 Service Not Available, 421 Home Directory Unavailable"
This error can be shown for a number of reasons if too many connections make sure no one else on your network is also using FTP for 000webhost, i.e. students in a classroom might encounter this error, if you are alone on your network then it may be the 000webhost network is busy, other errors like Home Directory Unavailable, Service Not Available point to a local blockage caused by firewall software or network routing issues. You can try to resolve this yourself by using alternative DNS, the use of a proxy server or a VPN.
FREE WINDSCRIBE VPN
ALTERNATIVE DNS TUTORIALS
After all of the above, if you feel there is something actually wrong with your 000webhost account severely enough that you would like us to check or a developer to investigate then open a thread on the forum and we will do our best to check, if we are able to connect ourselves or using FTP test scripts then the issue will be on your side / your ISP / routing issues that we cannot control.