Using Cloudways Hosting and FileZilla Upload Settings

“Cloudways is definitely not just for WordPress. I tried it myself, and non‑WordPress sites work too!”

Published: 2025/12/10

This article records my journey from learning through courses to actually building a site. I eventually chose Cloudways hosting and share how to solve upload issues for non‑WordPress websites. Topics include Cloudways architecture, FileZilla setup, the link between Application and public_html, and cache clearing tips. It’s not a textbook, but my own hands‑on experience to help you avoid detours. Contents include:

  • Why choose Cloudways:
    • Multiple sites, fast speed, responsive support
    • More flexible than Godaddy basic plan
  • Cloudways architecture:
    • Server: hosting under your account
    • Application: space for each website
  • WordPress vs non‑WordPress:
    • WordPress: one‑click install, beginner‑friendly
    • Non‑WordPress: need to create a Custom App to find upload location
  • FileZilla setup and upload:
    • Find info in Master Credentials
    • Go to applications → Application folder → public_html
    • Place index.html and folders inside
  • Cache issues and solutions:
    • Clear Varnish cache in Cloudways dashboard
    • Also clear browser cache

Background and Choosing Cloudways

I discovered Cloudways hosting when my site was nearly complete.

After exploring different fields, I wanted to build a blog to organize my learning journey.

By chance, I met teacher Wu Zhe‑Yu on Hahow and joined his course “Interactive Web Programming (HTML/CSS/JS).” Since I was building a personal blog, I decided to challenge myself using traditional HTML, CSS, and JS with Codepen knowledge.

This also trained my front‑end and basic back‑end skills, giving me a chance to step into programming. Thanks to the solid course, I managed to build my own site.

I highly recommend Wu’s online course. He helps you move beyond old web concepts, introduces waterfall layouts, and tools like Bootstrap to make building easier.

He is both an engineer and a designer, guiding you to create not just functional but beautiful websites.

Almost anyone can build their own site after the course. Even with AI tools, you’ll have the skills to edit AI‑generated code. Truly valuable.

Links to the course are below for those interested.

Near the end of the course, we needed hosting. The teacher recommended several options, but I only noted them casually at the time.

Years ago, I had built a personal site using Yahoo’s free space. It was simple, with a UI for easy uploads. But such spaces no longer exist.

Now hosts only provide IP addresses without UI, so you need software to upload. Luckily, Wu’s course covered this.

When I finally chose hosting, I realized the course was recorded years ago. Technology had changed, so I only learned upload basics and decided to compare hosts myself.

Later, I wanted a WordPress site for team management and joined another course. It recommended Cloudways and Gandi domains.

Since that course was recent, it compared Cloudways with other hosts and included step‑by‑step setup. Cloudways allows multiple sites, unlike Godaddy’s basic plan.

So I chose Cloudways without hesitation. Though pricier than Godaddy basic, it fit my needs.

Many online articles compare Cloudways hosting. I valued its ability to host multiple sites, fast speed, and responsive support.

Problems Encountered

After purchasing Cloudways, you can log in and start setup.

For WordPress sites, Cloudways shines with one‑click environment installation. No need to worry about setup. Very beginner‑friendly.

I recommend Cloudways to WordPress beginners.

Cloudways later updated its interface. I took some time to adapt.

Before setting up WordPress, you need to understand Cloudways architecture and terms.

Each account can have multiple servers. Each server can host multiple Applications, one per site.

To create a WordPress space, you add a new Application. Same for non‑WordPress sites.

The new interface has “Flexible” for quick access to Servers and Applications. It shows how many you have.

Flexible location in the new interface

Inside Flexible, you’ll see Servers and Applications. My server already had sites, so it wasn’t empty.

New servers will be empty.

View after entering Flexible

To add a new site, click “+ Add Application” and choose the server.

Add Application server selection

Then choose WordPress version, name the Application, and click “+Add Application.”

Application setup page

Setup takes time. The UI shows progress.

Environment setup progress UI

Cloudways also emails you when the Application is ready.

Back in Applications, you’ll see the new WordPress environment with your chosen name.

New Application name

Inside, you’ll find the WordPress site, temporary domain, and related settings.

Application info view

You can now enter WordPress backend to design and build content.

But here’s the problem.

My site wasn’t built with WordPress. I used Codepen, downloaded files, edited with Sublime Text, and had HTML, CSS, and JS ready. I needed to upload them.

So where should I put my files?

When in doubt, search Google or ask AI. But most Cloudways guides focus on WordPress. Few cover non‑WordPress uploads.

Looks like I had to figure it out myself.

Solutions and Related Settings

Cloudways is a hosting management interface, but at its core it’s still a server. So the upload process follows standard hosting methods, which is no problem.

I personally use FileZilla, so I’ll explain using its interface.

First, select your purchased server in Cloudways and go to Master Credentials. You’ll find the Public IP, Username, and Password. These are the details you’ll enter in FileZilla to connect.

You can find the info in the red box. Record it for later. Username and password can be changed.

Back in FileZilla, go to “File” → “Site Manager.” I prefer creating a site profile instead of quick connect.

FileZilla is user‑friendly, with drag‑and‑drop features. Highly recommended.

In Site Manager, fill in the details from Cloudways. Once connected, you’ll see remote folders on the right.

Enter IP, username, and password here.

After connecting, the right side shows Cloudways folders. The left side shows local folders.

The red box shows Cloudways server folders.

So where do we upload files?

Back in Cloudways, go to Applications. Each site is separated by its own Application.

For WordPress, you just add another Application. But for non‑WordPress, you need a blank space to upload files.

Create a new Application, but choose PHP → Custom App instead of WordPress.

After installation, you’ll see a new Application with a different icon. That’s your upload space.

Choose the red box option for non‑WordPress environment.
Top and bottom are WordPress, middle is non‑WordPress. Upload here.

In Access Details, find Database. The DB name is the folder name you’ll see in FileZilla.

Here the folder name is “hbbbkjbrka.” That’s the target folder in FileZilla.

Reconnect FileZilla, go to applications, then the folder “hbbbkjbrka.” Inside is public_html.

public_html is the root folder for your site. Place your files here.

public_html is the main site folder. Arrange files here with relative links.

Inside public_html, you’ll see index.php. That’s the default homepage. You can check it via Application URL.

Example of index.php location.

Replace it with your index.html. Upload by dragging from left (local) to right (server). Simple and intuitive.

Final look of public_html. Index file must be at root.

Handling Non‑Instant Updates After Upload

At first, I struggled because even after deleting index.php, the temporary domain still worked. Strange.

After testing and searching, I realized it was due to Cloudways cache.

Solution: In Server → Manage Services, find Varnish and click “Purge.” This clears cache.

Varnish purge location

Cache speeds up sites but can be troublesome here.

If you still see old pages, clear your browser cache too. Then you’ll see updates.

WordPress also faces cache issues, but plugins can help. That’s beyond this article.

Conclusion

Cloudways hosting is user‑friendly for both WordPress and non‑WordPress sites.

Domain integration is straightforward. Settings are clear.

Though the English interface may feel overwhelming at first, good courses and practice help. I faced upload issues but solved them with Google and trial‑and‑error.

Since I spent time solving this, I wrote this article to help others.

I’m Wakame. If my article helps, follow my IG or fan page.

Thank you for reading! Your support keeps me creating. If my article inspired or helped you, please consider supporting me via the link above. Any amount is appreciated. Thank you for being here, and I look forward to sharing more useful stories and experiences :)

Recommended Resources

FAQ

No, just create a Custom App to host non‑WordPress sites.

Inside the Application folder’s public_html, which is the root directory.

Because cache wasn’t cleared. Go to Server → Varnish and click “Purge.”

Use the IP, username, and password from Master Credentials to set up the site.

Yes. WordPress installs in one click, and non‑WordPress works via Custom App.

You may also be interested in these articles

🌐 CN