Deploying your Website

Deploying your Website

Last updated: May 25, 2026

Outline

Website Deployment & FTP

This guide details how to securely provision your access credentials, connect to your Vooju hosting space, and deploy your website files using File Transfer Protocol (FTP).

⚡ Activating & Retrieving Your FTP Credentials

To protect your hosting environment, FTP access is disabled by default. Your specific login credentials are not static and must be securely generated from your Vooju Account Admin Panel.

Activating your FTP credentials

  1. Log into your Vooju Account Admin Panel.
  2. Navigate to Account Settings from the primary menu navigation.
  3. Locate the FTP Access status indicator and click the “Disabled” button. This action signals the system to dynamically provision your FTP access credentials.
  4. The system will immediately display your newly generated Username, and Password.

⚠️ Critical Action: Make an immediate, secure copy of these credentials. For your protection, the password will only be visible once and cannot be recovered later. You may reset the password by going through the process again.

  1. Click the “I’ve made a copy” button. This finalizes the workflow and changes your FTP access status to Enabled.

Connecting to the Webserver

Once activated, your configuration fields will map to these values:

  • FTP Hostname: ftp.vooju.com
  • Username: The username copied during step 5
  • Password: The secure password copied during step 5
  • Port: 21
  • Protocol/Encryption: FTP or Explicit FTP over TLS (FTPS) (Recommended for security)

📂 The Directory Structure Matrix

When you successfully connect via FTP, you will see several system folders. Uploading files to the wrong folder will cause your website to display a “404 Not Found” or default landing page error.

Root Directory Breakdown

/yourdomainname.com : This is your live web folder. All public-facing files—such as index.html, index.php, CSS stylesheets, and images—must be uploaded inside this folder.

/private: Used for storing backups, or logs that should never be accessible via a web browser.

⚠️ Critical Deployment Rule: Your website’s homepage file must be named exactly index.html or index.php (all lowercase). If you name it Index.html or home.html, the server will fail to recognize it as the default page.

💻 Recommended FTP Clients & Setup

FileZilla (Windows / Mac / Linux)

FileZilla is the industry standard for cross-platform file transfers.

  1. Download and open FileZilla.
  2. Open the Site Manager from bar at the top of the interface.
  3. Click “New site” button
  4. In the “General” tab, enter your Host (ftp.vooju.com), Port (21), Username and Password.
  5. In the “Transfer Settings” tab, select “Passive” as your Transfer Mode.
  6. Click “Connect”
  7. In the right-hand panel (Remote Site), double-click the folder named with your domain name.
  8. Drag your website files from the left-hand panel (Local Site) and drop them into the right-hand panel.

Cyberduck (Mac / Windows)

A streamlined interface popular among macOS users.

  1. Open Cyberduck and click Open Connection in the top left.
  2. Select FTP with SSL wrap (Implicit FTPS) from the connection protocol dropdown menu.
  3. Input your server address in the Server field.
  4. The system will automatically adjust the port to 990 (the standard port for implicit SSL wrap).
  5. Enter your hosting credentials and click Connect.
  6. Navigate into the public_html directory and use the Upload action to transfer your files.

🛠️ Common FTP Troubleshooting

Scenario 1: Connection times out or fails to retrieve the directory listing.

The Cause: Strict local firewalls or routers blocking the secondary data ports used by FTP.

The Fix: Open your FTP client’s connection settings and switch the Transfer Mode from Active to Passive. Passive mode forces the server to choose the data port, which easily bypasses local firewall restrictions.

Scenario 2: Changes are uploaded, but the old website still shows up.

The Cause: Aggressive web browser caching or a failure to overwrite the default placeholder page.

The Fix: 1. Perform a hard refresh in your browser (Ctrl + F5 on Windows or Cmd + Shift + R on Mac). 2. Check your public_html folder via FTP and delete any default placeholder file (like default.html or placeholder.png) that might be taking priority over your new index.html.

[back to support]