If you are hosting a Java application on a managed hosting platform and need to upload WAR files, JSP pages, configuration files, or static assets, creating a dedicated FTP account is usually the safest and most practical way to manage deployment. In a Plesk-based environment, this lets you separate file access for a Java project from the main hosting login, control exactly which directory can be reached, and keep deploy paths tidy for Tomcat or a private JVM setup.
In an ITA Java hosting environment with My App Server, an FTP account is especially useful when you want to upload files into your application root, a shared deploy folder, or a specific Tomcat webapp directory without giving broader access to the whole hosting subscription. This is a common setup for WAR deployments, JSP hosting, servlet projects, and manual file uploads that support a Java application lifecycle.
Why create a separate FTP account for a Java project
A dedicated FTP user is more than just a convenience. For Java hosting, it helps keep application files organized and reduces the risk of accidental changes elsewhere in the account. If you deploy through Plesk and My App Server, a separate FTP account can be assigned to the exact folder where your project lives, so your team can upload builds without touching logs, mail, or unrelated websites.
- Safer access control: limit a user to one project directory or deploy path.
- Cleaner deployment workflow: upload WAR, JSP, class resources, or static files directly to the right location.
- Better separation: developers, testers, and content editors can have different access levels.
- Useful for Tomcat deployments: place application files where your Tomcat instance expects them.
- Easier maintenance: manage file transfers without using the full control panel login.
For small and medium Java applications, this is usually the simplest way to handle file management in a shared hosting account with a private JVM or Tomcat service.
Before you create the FTP account
Before setting up the account, it helps to confirm where your Java application files should live. In a Plesk hosting environment, this may be one of the following:
- a project folder under the subscription root;
- the application directory used by My App Server;
- a Tomcat web application folder;
- a deploy directory for WAR uploads and unpacking;
- a folder for static assets, configs, or generated files.
If you are not sure which path to use, check the service details in Plesk or the My App Server setup for your Java application. For example, some projects are deployed as WAR files and then expanded by Tomcat, while others keep configuration files in a separate folder to make updates easier.
You will also need:
- access to the hosting control panel;
- the domain or subscription that contains the Java project;
- the target folder path for the FTP account;
- a username and strong password for the new FTP user.
How to create an FTP account in Plesk
The exact menu labels may vary slightly depending on the hosting setup, but the process is generally the same in Plesk.
1. Open the hosting subscription
Log in to Plesk and select the subscription or domain that hosts your Java project. If you manage multiple applications, make sure you are working inside the correct one. This is important in a Java hosting environment where one subscription may contain several deploy paths or service folders.
2. Go to FTP Access
Find the section for FTP Access or FTP Accounts. In many Plesk installations, this is located under the domain or subscription tools. This area lets you create, edit, disable, or remove FTP users.
3. Add a new FTP user
Choose the option to add a new FTP account. Enter a username that clearly identifies the project or role, for example:
- projectname-deploy
- appname-ftp
- tomcat-release
- javasvc-upload
Use a naming pattern that your team can understand later. Clear account names are especially helpful if you manage multiple Java apps in one hosting subscription.
4. Set a strong password
Choose a password that is long and difficult to guess. For hosted Java applications, FTP access can lead directly to important deploy files, so password hygiene matters. If your team uses a password manager, store the credentials there rather than in email or chat history.
5. Select the directory for access
This is the most important step. Assign the FTP account to the exact folder that should be reachable by that user. For a Java project, this might be:
- the application source or upload folder;
- the deploy directory for WAR uploads;
- the webroot used by Tomcat for unpacked content;
- a dedicated folder for configuration or assets.
Do not give access to a broader folder unless the user really needs it. If the account is only for uploading release files, point it to the deploy path and nothing else.
6. Save the account
After confirming the username, password, and folder path, save the FTP account. Plesk will create the user and attach it to the selected directory. The account should now be ready for file transfers.
How to choose the right folder for a Java application
The right folder depends on how your Java project is deployed. In a My App Server setup, common use cases include WAR deployment, JSP-based sites, servlet applications, or a private JVM running a specific service. The goal is to make file deployment predictable and simple.
For WAR deployments
If your application is deployed as a WAR file, the FTP account should usually point to the directory where release artifacts are uploaded. In some setups, Tomcat or the application service watches that folder and deploys the app automatically, while in others you manually copy the WAR to the correct location and restart the service if needed.
For JSP and servlet projects
When you are working with JSP hosting or servlet hosting, the FTP user should have access to the web application folder where JSP files, view templates, static resources, and related assets are stored. Keep the structure consistent so that developers know where to upload changes.
For configuration files
Some Java applications keep config files outside the main app package. This can be useful for environment-specific settings, connection details, or integration values that change more often than the application code. In that case, create a separate FTP account for the config folder if your workflow requires it.
For static assets
If your Java app serves images, stylesheets, or downloadable documents, you may want one FTP account for static files and another for deploy files. This can reduce confusion and make content updates easier for non-developers.
Recommended FTP account setup for managed Java hosting
For a hosting company environment, a good setup is usually simple and restrictive. That means the FTP account can do the job without having access to unnecessary areas of the subscription.
- One project, one account: create a separate account for each application or major deploy path.
- Least privilege: limit the folder to the smallest practical directory.
- Clear naming: use names that show the purpose of the account.
- Strong passwords: treat FTP access as sensitive because it can affect live files.
- Document the path: note which folder the account is linked to, especially in shared team environments.
In a My App Server context, this is often the best balance between flexibility and control. You can manage your own Apache Tomcat or private JVM inside the hosting account while keeping file transfers separated from day-to-day panel access.
How FTP fits into My App Server and Tomcat workflows
My App Server is designed to make Java hosting more practical inside a shared hosting account. That includes working with different Java versions, managing service control, and handling deployment paths for application files. FTP is the file-transfer part of that workflow.
Here is how the pieces commonly fit together:
- My App Server: provides the Java/Tomcat runtime and service management.
- Plesk: gives you control over domains, files, and access accounts.
- FTP account: lets you upload application files to the correct directory.
- Tomcat or private JVM: runs the Java application once files are in place.
This setup is useful when you need a practical hosting platform for a smaller Java application, internal tool, or JSP site. It is not intended to replace large enterprise application server architectures, but it does provide a straightforward way to deploy and maintain Java projects with direct file access.
Common mistakes to avoid
When creating an FTP account for a Java project, a few simple mistakes can cause deployment problems or security issues.
Giving access to the wrong directory
If the FTP account points to the wrong folder, uploads may not appear in your application, or the user may see files they should not access. Always verify the target path before saving the account.
Using the main panel login for file transfers
It may be tempting to use the main hosting login for everything, but this is not a good practice. Separate FTP access is easier to control and safer for team workflows.
Mixing deploy files with unrelated content
Keep Java deploy files away from unrelated documents, backups, or temporary uploads. A tidy structure reduces the chance of accidental overwrites.
Using weak or shared passwords
FTP credentials should be unique per user or purpose. Avoid reused passwords, especially when the account can change live application files.
Not checking permissions after upload
After uploading WAR files, JSPs, or configs, make sure the application can read them correctly. If your deployment fails, the issue may be the folder path, ownership, or file permissions rather than the Java application itself.
How to connect with an FTP client
Once the account is created, you can connect with a standard FTP client or a secure transfer tool supported by your hosting setup. Enter the FTP host, username, password, and port values provided by your hosting platform.
Typical connection details include:
- Host: the domain name or FTP server name;
- Username: the new FTP account name;
- Password: the password you set in Plesk;
- Port: the standard FTP or secure FTP port used by your service;
- Remote directory: the folder assigned to the account.
After login, upload your Java application files to the expected location. If your Tomcat service is configured to deploy automatically, the application may become available shortly after the upload. If deployment is manual, you may need to trigger it through Plesk or service control.
Troubleshooting FTP access for Java project files
If the account does not work as expected, the problem is often related to the folder path, login details, or service configuration. Use the following checks.
Cannot log in
Verify the username and password. Check whether the account is active and whether the hosting subscription is still available. If the password was copied from a manager, confirm that no extra spaces were included.
Uploads go to the wrong place
Review the root folder assigned to the FTP user in Plesk. If the account points to a home directory instead of the Java deploy folder, files will not reach your application.
Files upload but the app does not change
Your Tomcat or private JVM may need a restart, or the files may need to be placed in a different deploy path. Also confirm that the project uses the uploaded file type, such as WAR, JSP, or static content.
Permission denied errors
Check file ownership and permissions. In some cases, the application service can read files but the FTP user cannot overwrite them, or the reverse. Make sure the folder is writable by the FTP account and readable by the application runtime.
Directory appears empty after login
This often means the FTP account was assigned to a folder that has no files yet, or the account is restricted to a path above or below the project root. Recheck the directory mapping in the control panel.
Security tips for FTP accounts in hosting environments
FTP access is useful, but it should be managed carefully. For Java hosting, the files you transfer can directly affect live application behavior, so basic security practices matter.
- create one account per person or per function where possible;
- remove accounts that are no longer needed;
- change passwords when staff or developers leave a project;
- avoid storing credentials in plain text;
- review the assigned folder path periodically;
- use secure transfer options if supported by your hosting setup.
These steps help keep your application deployment process stable while reducing unnecessary access.
FAQ
Can I create an FTP account only for one Java application?
Yes. In Plesk, you can usually assign the FTP account to a specific folder, which makes it suitable for one Java project, one deploy path, or one Tomcat web application directory.
Should I use one FTP account for all my Java projects?
That is possible, but not ideal. Separate accounts are easier to manage and reduce the risk of uploading files to the wrong application.
Can an FTP account be used to upload WAR files?
Yes. This is one of the most common uses in Java hosting. You can upload WAR files to the deploy location used by My App Server or Tomcat.
Do I need FTP access if I deploy through Plesk?
Not always, but FTP is useful when you need direct file uploads, quick changes, or access from a local development machine or build process.
Can I restrict FTP access to a subfolder?
Yes, in most Plesk setups you can limit the FTP account to a specific directory. This is recommended for Java project deployments.
What if my Java app uses a private JVM?
You can still use FTP to manage the application files. The FTP account should point to the folder used by that private JVM or the related deploy path.
Is FTP enough for Tomcat hosting?
For many small and medium projects, yes. FTP is often enough for uploading application files, JSPs, configs, and static content. Service control and runtime management can be handled separately in Plesk.
Summary
Creating a dedicated FTP account for a Java project in a Plesk hosting environment is a simple but important part of clean deployment management. It helps you keep file uploads separate from panel access, limits each user to the right folder, and supports practical workflows for Tomcat hosting, JSP hosting, servlet hosting, WAR deployments, and private JVM setups.
In an ITA My App Server environment, this approach fits well with the way Java applications are managed through Plesk: the control panel handles access and service management, while FTP gives you direct and precise file transfer to the correct deploy path. If you configure the account carefully and keep folder access narrow, you get a more reliable and safer deployment process for your Java project.