If you are hosting a Java application on a shared hosting account with Plesk, the safest approach is to create a separate FTP account for deployment files, configuration packages, and application uploads. A dedicated FTP user gives you better control over who can access your Java project files, and it also makes it easier to separate development, staging, and production content when you are deploying WAR, JSP, servlet, or static assets through My App Server.
In a typical Java hosting setup, FTP access is used to upload application files, review deploy paths, place Tomcat-related packages, or transfer build artifacts into the correct directory before deployment. With Plesk, you can create an FTP account for a specific folder, set the login credentials, and restrict access to only the file path that your Java project needs.
When you should create a separate FTP account
A dedicated FTP account is useful when more than one person works on the same Java project, or when you want to keep application deployment files isolated from the rest of the hosting account. It is also a practical choice if your Java application is managed through Plesk and uses a private JVM or Tomcat instance through My App Server.
- Deploying a Java web application to a specific folder
- Uploading WAR files, JSP files, or static resources
- Allowing a developer or contractor access only to one project directory
- Separating the application files from logs, backups, and mail content
- Keeping Tomcat and deploy paths organized in a managed hosting environment
If your account already uses the main subscription login, you can still create an additional FTP user for day-to-day deployment tasks. That is often safer than sharing the main control panel password with a developer.
What you need before you start
Before you create the FTP account, make sure you know the exact folder where the Java project should be uploaded. In Plesk, this may be a web root, a deployment directory, or a custom application path used by My App Server.
- Access to the Plesk control panel
- The domain or subscription where the Java project is hosted
- The correct target directory for uploads
- A strong password for the new FTP user
- Optional: the name of the Tomcat webapp folder or WAR deploy path
If you are using My App Server, confirm whether the project should be uploaded to a standard web directory or to a specific Tomcat deployment path. This depends on how the Java app is configured in your hosting account.
How to create an FTP account in Plesk
The exact screen labels can vary slightly by Plesk version, but the general process is the same. You create an FTP account from the domain’s hosting settings and assign it to a specific folder.
Step 1: Log in to Plesk
Sign in to your Plesk control panel using your hosting credentials. If your hosting provider has enabled My App Server, you will usually see the Java management tools together with your domain settings and file management options.
Step 2: Open the domain or subscription
Go to the domain where your Java application is hosted. In a shared hosting environment, FTP accounts are usually created at the domain or subscription level rather than globally.
Step 3: Find the FTP Accounts section
Look for FTP Access, FTP Accounts, or a similar option under the domain’s file management tools. This section is used to create and manage additional FTP users.
Step 4: Click to add a new FTP account
Select the option to create a new account. You will usually be asked to define a username, a password, and a home directory.
Step 5: Set the username
Choose a clear username that identifies the purpose of the account. For example:
- projectname-ftp
- deploy-user
- tomcat-upload
Use a name that is easy to recognize, especially if multiple people manage the same Java hosting account.
Step 6: Set a strong password
Create a strong, unique password. For hosting environments, avoid simple combinations or reused credentials. If your team uses a password manager, store the FTP password there so it can be shared securely when needed.
Step 7: Choose the access directory
This is the most important part for a Java project. Set the FTP account to a folder that matches the deployment structure you actually need. Common examples include:
- A web root folder for application files
- A custom deploy directory for WAR uploads
- A project folder that contains JSP and static resources
- A staging directory used before moving files into Tomcat
Do not give FTP access to a broader folder than necessary. If the account only needs to upload a Java web application, restrict it to that application path only.
Step 8: Save the account
After you confirm the username, password, and folder path, save the new FTP account. Plesk should then list it among the available FTP users for that domain.
How to choose the right folder for a Java project
For Java hosting, the folder you assign to the FTP account matters as much as the account itself. A Tomcat or private JVM deployment often has a different structure than a standard PHP or static website.
Common folder scenarios
- WAR deployment folder: Use this when you upload build artifacts that are later deployed by Tomcat.
- Web application root: Use this if your files are served directly from a project directory.
- Staging folder: Use this if you upload files first and deploy them manually after validation.
- Custom application directory: Use this if My App Server or your Plesk setup uses a custom path for the Java app.
If you are not sure which directory is correct, check the Java hosting instructions for your service or review the application path configured in My App Server. The correct deploy path is the one that matches the way the application is served by Tomcat.
Recommended permissions and access rules
In managed hosting, the best practice is to keep FTP permissions as limited as possible while still allowing deployment. The account should be able to upload and edit files inside the assigned folder, but not browse the entire hosting subscription.
- Assign access only to the application folder
- Use a unique account for each developer or purpose
- Remove old FTP users when they are no longer needed
- Avoid using the main control panel account for file transfers
- Keep credentials separate from database and application secrets
This approach is especially helpful when your Java project includes config files, private keys, or environment-specific build assets.
Using FTP with My App Server and Tomcat
If your hosting account includes My App Server, FTP can be used as part of the deployment workflow for Java applications. You may upload a WAR file, copy JSP pages, place static assets, or transfer custom configuration files to the appropriate Tomcat path. The key is to match the FTP folder with the application layout used by your Tomcat instance.
My App Server is designed to make Java hosting easier in Plesk by giving you practical control over your Java application stack. That can include selecting a Java version, managing a private JVM, working with a Tomcat-based service, and deploying application files without needing a separate enterprise application platform.
In this setup, FTP is not the application server itself. It is simply the file transfer method that helps you place files where Tomcat or your Java runtime can use them.
Typical deployment examples
- Upload a WAR file to the deployment folder, then trigger redeploy in Plesk
- Upload JSP files to the webapp directory used by your Tomcat instance
- Transfer static assets such as images, CSS, or JavaScript to the application folder
- Place updated configuration files in a staging path before restart or redeploy
If your setup uses a custom app server definition, make sure the FTP path points to the correct location used by that server. A mismatch between the upload folder and the runtime folder is a common reason why changes do not appear after deployment.
How to connect with an FTP client
After the account is created, you can connect with any standard FTP or FTPS client supported by your hosting provider. If available, prefer encrypted file transfer over plain FTP.
- Host: your domain name or hosting server hostname
- Username: the FTP account you created
- Password: the password you set during account creation
- Port: typically 21 for FTP, or the FTPS port provided by your host
Once connected, navigate only to the assigned folder. For Java projects, verify that uploaded files appear in the deploy path expected by Tomcat or My App Server.
Troubleshooting common FTP issues
Even in a well-managed hosting environment, FTP problems can happen if the folder path, username, or permissions are not set correctly. The following checks solve most issues.
Cannot log in
Check that the username and password are correct, and confirm that the account is active. If the hosting provider requires FTPS, make sure your client is configured for secure connection.
Can connect, but cannot upload files
This usually means the FTP account does not have write access to the target directory. Review the folder assigned to the account and make sure it matches the intended deployment path.
Files upload, but the Java app does not change
In a Tomcat-based setup, this often means files were uploaded to the wrong directory. Check whether the application uses a web root, a WAR deployment folder, or a separate private JVM path through My App Server.
Permission denied on certain directories
This can happen if the FTP account is restricted to a narrower folder than expected, or if the target directory belongs to a different deployment path. Adjust the folder assignment in Plesk if needed.
Old files remain after deployment
Tomcat may keep cached resources or the application may need a redeploy or restart after file changes. If your hosting plan includes service controls in Plesk, use the available application or service control tools to refresh the deployment where appropriate.
Best practices for Java hosting file access
For Java hosting, clean file management helps avoid deployment mistakes and makes support easier if you need assistance from your hosting provider.
- Use one FTP account per project when possible
- Keep deployment files in a clearly named folder
- Document the deploy path used by your Java application
- Separate source archives from runtime files
- Review FTP users regularly and delete unused accounts
- Use secure passwords and encrypted transfer when supported
These practices are especially useful when the same hosting subscription contains multiple sites, application versions, or test environments.
Example workflow for a Tomcat-based Java project
A practical workflow on a Plesk Java hosting account might look like this:
- Create a dedicated FTP account for the project.
- Assign it to the application folder used by Tomcat or My App Server.
- Upload the WAR file or updated JSP resources.
- Check the application path in Plesk.
- Redeploy or restart the service if required.
- Test the site in a browser to confirm the new version is active.
This approach keeps file transfers simple and reduces the chance of uploading to the wrong directory.
Frequently asked questions
Can I create more than one FTP account for the same Java project?
Yes. In Plesk, you can usually create multiple FTP accounts and assign them to different folders. This is useful if one developer manages source uploads while another handles deployment files.
Should I give FTP access to the whole hosting account?
No, not unless it is absolutely necessary. For a Java project, it is better to restrict access to the application directory only. That keeps logs, backups, and other site files separate.
Do I need FTP if I use My App Server?
Not always, but FTP is often useful for file deployment, especially when you need to upload WAR files, JSP pages, or supporting assets. My App Server manages the Java runtime and Tomcat-related service side; FTP handles file transfer.
What is the difference between FTP and the Tomcat deploy path?
FTP is the method you use to upload files. The deploy path is the actual directory where the Java application files must be placed so Tomcat or the private JVM can use them.
Can I use the same account for multiple domains?
Usually an FTP account is tied to one domain or one directory scope. If you manage several Java projects, create separate accounts for each one to avoid confusion and accidental uploads.
Is FTPS better than plain FTP?
Yes. If your hosting platform supports it, encrypted file transfer is the safer choice because it protects login credentials and uploaded files during transfer.
Summary
Creating a separate FTP account for a Java project in Plesk is a straightforward way to improve file management, limit access, and keep deployment paths organized. In a Java hosting environment that uses My App Server, this is especially helpful for uploading WAR files, JSP resources, and application assets to the correct Tomcat directory.
The main rule is simple: create the FTP user, restrict it to the proper folder, and make sure that folder matches the actual Java deploy path. When FTP access is aligned with your Plesk hosting structure, deploying and maintaining Java applications becomes much easier and less error-prone.