Upload a website with FileZilla
Connect FileZilla to your assigned UKC hosting server, then upload the website into the domain’s httpdocs folder
Use the FTP username and password shown under Plesk Web Hosting Access, not your Client Area password. Prefer explicit FTP over TLS when offered, keep passive mode enabled and confirm you are working inside the correct domain before replacing files.
What do you need before uploading?
Hosting server
Use the assigned server shown in the hosting welcome email or Client Area, such as ukc10.uk, ukc11.uk, ukc12.uk or ukc13.uk.
FTP system user
In Plesk open Websites & Domains, Hosting & DNS, then Hosting or Web Hosting Access to view or reset it.
A local website copy
Know which folder on your computer contains the home page and all required images, stylesheets and scripts.
A backup
Back up the current remote files before overwriting a working site. Keep the copy outside httpdocs.
How do you connect and upload with FileZilla?
- 1Install the official FileZilla Client
Download the client from the FileZilla Project. Do not install an unrelated copy from an advert or download portal.
- 2Create a Site Manager entry
Enter the assigned server as Host, choose FTP with explicit TLS when available, and use Normal logon.
- 3Enter the Plesk FTP login
Use the system user and its password. Port 21 is the usual FTP and explicit-TLS port.
- 4Open httpdocs
After connecting, use the remote pane to open the correct domain’s httpdocs folder.
- 5Upload the complete site
Drag the website files from the local pane to the remote pane. Keep folders and file names intact.
- 6Check failed transfers
Open FileZilla’s failed and queued transfer tabs and retry only after correcting the cause.
What should you test after uploading?
Home page file
Make sure httpdocs contains the intended index file and no unwanted default index page takes priority.
HTTPS and links
Open the site securely, follow important links and check that images and styles load.
Case-sensitive names
Linux treats Image.jpg and image.jpg as different files. Correct the HTML or file name when an asset is missing.
Application requirements
A PHP or database-driven site can need a database import, configuration file and suitable PHP settings in addition to files.
Common FileZilla problems
Why do I see 530 Login incorrect?
The FTP username or password is wrong. Re-enter the Plesk system user, remove copied spaces and reset only the FTP password if needed.
Why can FileZilla not find the server?
Check the assigned hostname and local internet connection. Use the exact UKC server name rather than an old example from another account.
Why is the old website still visible?
Confirm you uploaded into the correct httpdocs folder, replaced the active index file and are viewing the correct domain over HTTPS. Browser or CDN caching can also delay what you see.
Can I upload without FileZilla?
Yes. Plesk File Manager can upload files or directories through the browser and is often simpler for a small update.
Ready to publish?
Open Plesk and confirm the credentials for the correct website
If the connection fails, send support the domain, server and exact FileZilla error, but never the password.