If you host a Tomcat application in Plesk, the safest way to transfer files is to create a separate FTP account for the project instead of using the main subscription login. This gives you cleaner access control, makes deployment easier for developers, and reduces the risk of changing files outside the application directory. In a typical UK hosting setup, this is especially useful when one team manages the website, another handles the Java app, and you want each person to access only the relevant deploy path.
For Tomcat hosting with My App Server, an FTP account is commonly used to upload WAR files, JSP resources, configuration files, static assets, and supporting application packages into the correct deploy folder. If your hosting account includes Plesk, you can usually create an FTP user in a few minutes and point it directly to the project directory.
When you should create a separate FTP account
A dedicated FTP account is recommended when you need one or more of the following:
- Developer access without sharing the main hosting password.
- Access limited to one Tomcat project or one deploy path.
- Safer file management for WAR, JSP, and servlet resources.
- Simple handover between developers or agencies.
- Clear separation between application files and other website content.
For managed Java hosting, this is a practical way to keep your Tomcat deployment tidy. It also helps when you are using a private JVM or a Tomcat instance managed through a control panel, because the FTP account can be aligned with the exact directory used by the app server.
Before you start
Check the following first:
- You have access to Plesk for the hosting subscription.
- The Tomcat project or My App Server instance already exists, or you know the folder where it will be deployed.
- You know which directory should be writable by FTP, for example a deploy folder, upload folder, or application root.
- You have a username and a strong password ready for the new FTP account.
If you are not sure which path to use, ask your hosting provider or check the My App Server service details in Plesk. For Tomcat hosting, the folder you choose should match the deployment workflow for your application, especially if you upload WAR files or external resources regularly.
How to create an FTP account in Plesk
Step 1: Sign in to Plesk
Log in to your Plesk control panel using your hosting subscription details. If you manage multiple domains, make sure you select the correct subscription or domain before adding the FTP user.
Step 2: Open the FTP Access section
In the domain or subscription panel, find the section for FTP access or FTP users. The exact label may differ slightly depending on the Plesk version, but it is usually found under website and domain management.
Step 3: Add a new FTP account
Click the option to create a new FTP account. You will normally need to enter:
- A username for the FTP account.
- A strong password.
- The home directory or root directory for access.
Choose a username that makes the purpose clear, such as one related to the project or application. For example, a name like tomcat-app or deploy-app1 is easier to recognise later than a generic username.
Step 4: Set the directory for the account
This is the most important part for Tomcat hosting. Select the folder that should be accessible through FTP. In many cases, that folder will be one of the following:
- The application deploy directory.
- A folder used for WAR uploads.
- A web resources directory for static files.
- A project-specific folder under your hosting account.
For My App Server or custom Tomcat setups, make sure the FTP path matches the application workflow. If your app expects files in a specific deploy path, do not point the FTP user to a broader account directory unless that is intentionally required.
Step 5: Save the account
Confirm the settings and save the new FTP account. Once saved, the account should appear in the FTP users list, along with the assigned path.
Step 6: Test the login
Use an FTP client such as FileZilla, or your preferred deployment tool, to test the new credentials. Connect using:
- The FTP hostname provided by your hosting panel.
- The new username and password.
- The correct protocol required by your hosting service, such as FTP or FTPS if enabled.
After logging in, verify that you can see only the intended directory and that you can upload, rename, and delete files within the allowed path.
Recommended folder structure for Tomcat projects
For a Tomcat project, a clear file structure makes deployment easier. The exact structure depends on the application and the way My App Server is configured, but a practical approach is to keep separate folders for each purpose.
- deploy/ for WAR uploads or deployment packages.
- app/ for extracted application files, if your workflow uses them.
- assets/ for static resources such as images, CSS, or JavaScript.
- config/ for application-specific configuration files, if allowed.
If your Tomcat application is served from a private JVM or a controlled deploy path, keeping these directories separate helps reduce confusion and lowers the chance of accidental overwrites. It also makes it easier for support teams to identify where files should go during updates.
Best practices for FTP access on hosting accounts
Use a separate account per project or developer
When possible, create one FTP user per application or per team member. This improves accountability and reduces the chance that one user changes another project’s files.
Grant access only to the needed directory
Do not give FTP access to the whole hosting account unless it is necessary. For Tomcat and Java hosting, a narrow path is usually enough and is better from a security and maintenance point of view.
Prefer secure file transfer if available
If your hosting plan supports FTPS or SFTP, use the secure option rather than plain FTP. This protects login details and file transfers during deployment.
Use strong passwords
FTP passwords should be unique and strong. Avoid reusing the same password for Plesk, email, and FTP. If multiple people need access, create separate accounts instead of sharing one password.
Review permissions before uploading application files
Tomcat deployments often include WAR files, configuration files, and resource directories. Make sure the FTP account has enough permission to upload what you need, but not more than necessary. If a file upload works but the app still cannot read the files, the issue may be related to directory permissions or ownership, not the FTP login itself.
How this works with My App Server and Tomcat hosting
In a hosting platform that uses My App Server, the Tomcat instance is managed from Plesk and can run with its own Java version and service settings. An FTP account does not manage the server process itself, but it is useful for moving files into the correct location for deployment.
Typical use cases include:
- Uploading a WAR file to trigger a Tomcat deployment.
- Updating JSP pages or servlet resources.
- Replacing static files used by the Java application.
- Moving packaged releases into a staging or deploy folder.
This workflow is practical for small and medium Java applications that need a private JVM, a managed Tomcat service, and an easy file transfer method. It is not meant to replace advanced enterprise application-server administration, but it is very effective for everyday Tomcat hosting tasks in Plesk.
Common problems and how to fix them
The FTP account cannot connect
Check the username, password, and host name. Also confirm whether the account should use FTP, FTPS, or another protocol supported by your provider. In some cases, passive mode must be enabled in the FTP client.
The account connects but cannot see the expected files
This usually means the home directory is set incorrectly. Go back to Plesk and verify the directory assigned to the FTP account. For Tomcat projects, make sure it points to the correct deploy path or project folder.
Files upload successfully but the application does not update
Tomcat may need a redeploy, service refresh, or the correct file location for the changes to take effect. Check whether the files were uploaded into the runtime directory, a web resources directory, or a staging folder that still needs to be copied into the live path.
The account has too much access
If the FTP user can browse beyond the project directory, restrict the home folder in Plesk. A narrower scope is usually better for hosting accounts, especially when multiple websites or applications share the same subscription.
The Tomcat app uses a different deploy path than expected
Some Java hosting setups use a custom app server path or a different internal structure. If your Tomcat instance is managed by My App Server, review the service settings and the deploy path described in your hosting panel before creating the FTP account.
Example setup for a Tomcat project
Here is a practical flow for a small Java application:
- The main hosting account is managed in Plesk.
- My App Server provides the Tomcat instance and Java runtime.
- A project folder is created for the application files.
- An FTP account is created with access only to that folder.
- Developers upload WAR or JSP updates through the FTP account.
- The app is redeployed or refreshed from the Tomcat service panel.
This approach keeps the deployment process simple and controlled. It is especially useful when several people support the application and you need a predictable way to move files without exposing the whole hosting subscription.
FAQ
Can I use the main Plesk login instead of creating an FTP account?
You can, but it is not ideal for day-to-day deployment. A dedicated FTP account is safer because it can be limited to one project directory and shared only with the people who need access.
Should the FTP folder be the same as the Tomcat web root?
Not always. The correct folder depends on your deployment method. Some setups upload directly into the deploy path, while others use a staging or upload directory first. Follow the structure used by your Tomcat hosting configuration.
Can I upload a WAR file through FTP?
Yes, if your hosting configuration uses WAR-based deployment and the folder is set up for it. In many Plesk Tomcat setups, uploading the WAR file to the proper deploy folder is a common deployment method.
Do I need special permissions for JSP or servlet files?
Usually you only need write access to the relevant project directory. If the application reads files at runtime, make sure the file ownership and permissions are compatible with the Tomcat service on the hosting platform.
What is the benefit of using a separate FTP account on managed hosting?
It gives you cleaner access control, better security, and easier troubleshooting. It also makes it simpler to manage multiple applications inside one hosting account.
Is this suitable for large enterprise Java deployments?
This guide is focused on practical Tomcat hosting and managed Java hosting for small to medium applications. For complex clustering, high-availability architectures, or enterprise application-server management, the deployment model is usually different.
Summary
Creating a separate FTP account for a Tomcat project in Plesk is one of the simplest ways to manage files safely and efficiently. It lets you assign access to the exact deploy path needed for your Java application, supports cleaner collaboration, and fits well with My App Server-based hosting workflows. For UK hosting customers who manage JSP, servlet, WAR, or static resources through Plesk, this is a practical and reliable approach to file management.
After creating the account, always test the login, confirm the folder scope, and verify that uploads land in the correct Tomcat directory. That small amount of setup time usually saves a lot of time later during deployment and support.