What You’ll Need Before Starting
- A StackCP hosting account
- At least one domain already added to your hosting package
- The domain’s DNS managed through StackCP (most users have this by default)
Step 1: Log In to StackCP
- Go to your StackCP login page.
- Enter your username and password.
Step 2: Navigate to the Subdomains Section
- In the left sidebar (or main dashboard), click Manage Hosting.
- Click Manage next to your hosting package.
- Look for and click the Subdomains icon (it’s often grouped under Domains or in the main tools area).
Step 3: Create the Subdomain
- In the Subdomain field, type the prefix you want (e.g., blog, shop, app).
- Select the parent domain from the dropdown if it’s not already selected.
- (Optional but recommended) Set the Document Root.
- This is the folder where the subdomain’s files will live.
- Example: Type public_html/blog to keep files in a blog folder inside your main public_html directory.
- You can leave it blank for the default location.
- Click Create Subdomain.
That’s it! StackCP will automatically:
- Create the subdomain
- Add the necessary DNS records
- Create the folder (if specified)
Note: Changes to the Document Root can take up to 15 minutes to fully apply.
After creation:
- Go back to Manage Hosting → Manage.
- Click the File Manager icon (under Web Files).
- Navigate to the folder you set as the Document Root (e.g., public_html/blog).
- Upload your website files here (HTML, WordPress files, images, etc.).
You can also connect via FTP using the credentials shown in your StackCP dashboard.
Step 5: Test Your Subdomain
- Wait a few minutes for everything to propagate.
- Visit your-subdomain.yourdomain.com in your browser.
- You should see your uploaded content.
If it doesn’t load immediately, clear your browser cache or check DNS propagation using a tool like whatsmydns.net.
From the same Subdomains section you can:
- View all your subdomains
- Edit the Document Root
- Delete a subdomain (this removes the DNS record but keeps the files — delete files manually if needed)
Advanced: Wildcard Subdomains (*.yourdomain.com)
This usually requires:
- Adding a wildcard DNS record (* A record pointing to your server IP) in Manage Domains → Manage DNS.
- Proper server configuration (often handled automatically in StackCP, but check with your host if needed).
For most users, creating individual subdomains is simpler and more reliable.
Common Troubleshooting
|
Issue
|
Possible Cause
|
Solution
|
|---|---|---|
|
Subdomain shows error/404
|
Wrong Document Root
|
Edit the subdomain and correct the folder path
|
|
Subdomain not resolving
|
DNS propagation
|
Wait 5–60 minutes or check with DNS checker
|
|
Files not showing
|
Uploaded to wrong folder
|
Use File Manager to verify location
|
|
SSL not working
|
SSL not issued for subdomain
|
StackCP usually auto-issues Let’s Encrypt SSL
|
Pro Tips
- Use clear, descriptive names (blog, store, docs, staging).
- Keep subdomains organized in separate folders for easier management and backups.
- Subdomains are great for staging sites, client portals, or separating different projects.
- Always back up before making changes (StackCP has easy backup tools).
Need Help?
