If you are hosting a JSP application on a shared hosting account with Plesk, creating a separate FTP account is one of the simplest ways to manage files safely. A dedicated FTP user lets you upload WAR files, JSP pages, static assets, configuration files, and deployment folders without sharing the main panel login. In a typical Java hosting setup with My App Server, this is especially useful when you want to keep application deployment separate from domain administration.
For UK-based hosting accounts, the process is the same in Plesk regardless of location: you create an FTP account, assign it to the correct domain or folder, and then use those credentials from an FTP client such as FileZilla. If your JSP project uses a Tomcat deploy path or a custom application directory, the most important part is choosing the correct home folder so the account can access only the files it needs.
Why create a separate FTP account for a JSP project
A separate FTP account improves day-to-day file management for JSP hosting. It also helps reduce mistakes when multiple people work on the same project. Instead of using the main hosting login, you can create a restricted account for a specific application path, such as the web root, a deployment folder, or a workspace for static content.
- Better access control: limit the FTP user to one domain, one project, or one folder.
- Safer deployments: developers can upload files without access to billing or full control panel features.
- Cleaner project structure: separate source files, deploy files, and logs.
- Useful for Tomcat and JSP workflows: easier upload of JSP pages, WAR archives, and related assets.
- Practical for teams: each developer or agency can have its own credentials.
If your JSP application runs through My App Server, the FTP account usually works alongside the application’s deploy path. You can use FTP to place files in the right folder, while Plesk handles the service, Java version, and Tomcat-related configuration.
Before you start
To create an FTP account, you usually need access to Plesk for the hosting subscription or domain. If the account is managed by a hosting provider, the domain must already be added and active in the panel. For a JSP project, make sure you know which folder is being used for deployment before you create the account.
Check these details first
- The domain or subdomain used by your JSP application.
- The deploy path configured for Tomcat or My App Server.
- The folder you want the FTP account to access.
- Your preferred FTP client, such as FileZilla, WinSCP, or another SFTP/FTP tool if supported.
- Whether you need full write access or read-only access to a specific directory.
If you are not sure which directory is correct, check the app server settings in Plesk first. A JSP application often uses a deployment folder that is different from the general website root. Uploading files to the wrong path can prevent the application from starting correctly or make updates appear missing.
How to create an FTP account in Plesk
The exact interface may vary slightly depending on the hosting setup, but the steps are usually the same. The goal is to create a user, set a password, and point that user to the correct folder for your JSP project.
Step 1: Log in to Plesk
Sign in to the Plesk control panel for the hosting subscription that contains your JSP project. If you manage multiple domains, open the correct subscription first. This matters because FTP accounts are usually created within the context of a specific domain or hosting space.
Step 2: Open the FTP access section
In Plesk, look for the section labeled FTP Access, Web Hosting Access, or a similar file access menu. Some Plesk layouts place this under the domain management screen. If your hosting provider uses a custom theme or extension, the label may differ slightly, but the purpose is the same.
Step 3: Add a new FTP account
Select the option to create a new FTP user. Enter a username that is easy to identify, especially if you manage several environments. Good examples are project-based names such as jspdeploy, clientname, or site-update. Avoid generic names that might be reused across multiple sites.
Step 4: Set a secure password
Choose a strong password for the FTP account. It should be long enough to resist guessing and unique to this project. If your team uses password management tools, store the credentials there instead of sending them by email or chat.
For security reasons, avoid using the same password as the Plesk admin login or your main hosting account.
Step 5: Assign the correct directory
This is the most important step for JSP hosting. Set the FTP account’s home directory to the folder where the project files should be uploaded. In many cases, that will be one of the following:
- The domain’s document root for static assets or front-end files.
- A specific deploy folder used by My App Server.
- A staging directory for WAR files and build artifacts.
- A subfolder used for shared images, scripts, or configuration files.
If your JSP application is deployed through Apache Tomcat or a private JVM setup, check the exact deploy path before confirming the account. Uploading a WAR file to the wrong folder may not trigger deployment. Likewise, editing JSP files in the wrong directory can lead to 404 errors or stale content.
Step 6: Confirm permissions and save
Review the account settings and save the new FTP user. Depending on the hosting plan and Plesk configuration, the user may inherit the permissions of the target folder. In most managed hosting environments, the default file permissions are sufficient for normal web deployment, but you should still verify that the account can write only where needed.
How to use the FTP account for a JSP deployment
After the FTP account is created, you can connect with an FTP client and upload project files into the correct folder. For JSP hosting, the deployment workflow often depends on whether your application is a simple JSP site, a servlet application, or a packaged WAR file running in Tomcat.
Typical upload scenarios
- Uploading JSP pages: place updated .jsp files in the application directory expected by the server.
- Uploading static assets: upload CSS, JS, images, and fonts to the web-accessible folder.
- Deploying a WAR file: place the archive in the Tomcat deploy path if your setup uses auto-deploy.
- Updating configuration files: upload properties or XML files only to the folder that your application reads from.
In a My App Server environment, the FTP account helps with file transfer, while the app server extension manages the Java runtime and service. This separation is useful because you can change files without needing to reconfigure the entire hosting account.
Recommended client settings
When connecting from an FTP client, enter the hostname, username, password, and the correct port. If the server supports encrypted file transfer, prefer FTPS or SFTP where available. Many hosting platforms allow secure file transfer for better protection of credentials and content.
- Host: your domain or the server host name provided by the hosting company.
- Username: the FTP account you created in Plesk.
- Password: the password set during account creation.
- Port: usually 21 for FTP or a secure alternative if configured.
- Encryption: use explicit FTPS or SFTP if available.
Choosing the right folder for a JSP project
One of the most common mistakes in JSP hosting is placing files in the wrong location. A folder that works for a standard website may not be the correct deploy path for a Java application. In a Tomcat-based setup, the structure can include application directories, class files, WEB-INF, and static resources that should remain inside a specific tree.
Common folder types
- Web root: public files that should be accessible from the browser.
- Application root: the main directory for the JSP project.
- WEB-INF: protected application files that should not be accessed directly.
- Deployment folder: where WAR files or unpacked app content is stored.
- Staging folder: a temporary location used before final deployment.
If your hosting account uses My App Server, the deploy path may already be configured to work with the chosen Java/Tomcat instance. In that case, create the FTP account so it points to the same directory used by the application. This keeps deployment simple and reduces the risk of mixing unrelated files with the running app.
Best practices for FTP access on JSP hosting
Good file-management habits matter even more on Java hosting because a small change in the wrong folder can affect the running application. The following practices help keep a JSP project stable and easier to support.
Use one FTP account per project or role
If several people need access, create separate FTP accounts instead of sharing one login. A developer may need access to the application folder, while a designer only needs the asset directory. This makes auditing easier and limits accidental changes.
Keep deployments structured
Separate source files, build output, and runtime assets wherever possible. For example, you can keep:
- application source in a local development environment,
- WAR archives in a deployment folder,
- static assets in the public web directory,
- logs and diagnostics outside the public path.
Avoid uploading directly to the wrong live path
Some JSP applications use a temporary or staging directory before the final Tomcat deployment path. If your setup allows that, upload to staging first, test the files, then move them into the live location. This is especially helpful when updating production pages on a managed hosting account.
Keep credentials secure
Do not store FTP passwords in plain text documents. Use a password manager and remove access when a contractor or temporary developer no longer needs it. If an account is no longer required, delete or disable it in Plesk.
Use secure transfer where possible
When your hosting environment supports it, prefer encrypted file transfer. That helps protect login details and file contents during upload and download.
Common issues when creating or using an FTP account
Even a correctly created FTP account can fail to work if the directory, password, or service settings are wrong. These are the issues most often seen on JSP and Tomcat hosting accounts.
Login fails after account creation
Check that the username and password are correct and that you are connecting to the right host. Also confirm whether the account requires FTP, FTPS, or SFTP. Some clients try the wrong protocol by default.
Files upload successfully but do not appear in the application
This usually means the files were uploaded to the wrong directory. For JSP hosting, verify the exact deploy path in Plesk or in the My App Server configuration. The browser may also cache old content, so clear cache after deployment if needed.
Permission denied errors
If the FTP account can connect but cannot write files, the folder permissions may be too restrictive. In a managed hosting setup, permissions are usually set to a secure default, but the target directory still needs write access for deployments.
The application does not pick up a WAR upload
If your Tomcat setup uses auto-deployment, confirm that the WAR file is placed in the correct app server folder. If the service is not running or the version is mismatched, deployment may not occur as expected. In My App Server, check the service control and Java version before trying again.
JSP changes do not show immediately
Depending on the application structure, Tomcat may cache compiled JSP output or keep old sessions active. Redeploy the application, restart the service if needed, and refresh the browser. If your hosting plan includes multiple Java versions, make sure the app is running under the intended version.
How FTP access fits into My App Server workflows
My App Server is designed to make Java hosting more practical in a shared hosting environment. It allows you to manage your own Tomcat or private JVM setup through Plesk, with a clear service structure and deploy path. FTP is one part of that workflow: it gives you a simple way to move application files into place while the control panel handles the app server side.
In a typical JSP hosting project, the workflow may look like this:
- Create or configure the application server in My App Server.
- Select the Java version or Tomcat version required by the app.
- Note the deployment directory used by the service.
- Create an FTP account that points to that directory.
- Upload the JSP, WAR, or static files.
- Test the application in the browser and check logs if needed.
This setup is well suited to small and medium Java applications that need practical control without a full enterprise application server environment. It gives you enough flexibility to host JSP, servlets, and Tomcat-based sites while keeping file management straightforward.
Example use case
Imagine you have a JSP application for a customer portal. The application runs on a Tomcat instance managed through Plesk and My App Server. You need to update a few JSP pages and replace some image assets. Instead of logging in with the main panel account, you create an FTP user called portal-update and assign it to the application directory.
You then connect with FileZilla, upload the updated files, verify that the new JSP pages are in the correct path, and test the site in the browser. If the app uses a WAR-based deployment, you upload the new archive to the deploy folder and allow Tomcat to redeploy it. This is a simple and controlled way to handle file changes in a managed hosting environment.
FAQ
Can I create more than one FTP account for the same JSP site?
Yes. In Plesk, you can usually create multiple FTP users for the same domain or hosting subscription. This is useful when different people need access to different parts of the project.
Should I use FTP or SFTP for JSP file uploads?
If secure options are available, use SFTP or FTPS. They protect credentials and file transfers better than plain FTP. The exact option depends on the hosting configuration.
Where should I upload a JSP file?
Upload it to the application directory or web root used by your JSP or Tomcat setup. Do not assume the standard website folder is correct. Check the deploy path in Plesk or My App Server first.
Can an FTP account restart Tomcat or manage the Java service?
No. FTP access is for file transfer only. Service control, Java version selection, and Tomcat management are done in Plesk through My App Server or the hosting control tools.
What if my JSP project uses a custom app server path?
Use the custom deploy directory configured for that application. If you are not sure where it is, review the service settings or the app server documentation in your hosting panel before creating the FTP account.
Is FTP suitable for large enterprise Java deployments?
It can be useful for small and medium hosting workflows, but it is not a replacement for enterprise deployment pipelines, clustering, or complex release automation. For this hosting context, FTP is best used as a practical file-transfer method.
Summary
Creating an FTP account for a JSP project in Plesk is a straightforward way to manage files securely and efficiently. The key steps are to create a dedicated user, choose a strong password, and assign the account to the correct deploy path for your Java application. In a My App Server environment, this works well alongside Tomcat or a private JVM because you can keep file uploads separate from service management.
For the best results, always confirm the project folder before uploading, use secure transfer if available, and keep credentials limited to the access level required. That approach makes JSP deployment cleaner, safer, and easier to maintain within a managed hosting platform.