DWShells:Website Hosting
Publish your personal website
Upload a first page, use File Manager and keep private material out of public_html.
Last verified: 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.
← Documentation hub · Visual website guide
From a file to a public page
| Step | What it means |
|---|---|
| 01 · Your computer | Prepare index.html and a backup copy. |
| 02 · public_html | Upload using File Manager or SFTP. |
| 03 · Personal HTTPS URL | Open the website address from your dashboard. |
What becomes public
Before you continue: Files in public_html are website content. Never place passwords, private keys, application configs, database dumps or backup archives there. Hosting must fit your approved use and plan.
Publish a first page
- Select the website location. Open File Manager for the correct shell. Set File location to Website · public_html. The Eggdrop location is for bot files, not public web content.
- Upload index.html. Use Upload file for a file from your computer. For folders or larger transfers, use SFTP. Copy your existing site before overwriting files.
- Visit the right URL. Open the personal HTTPS website link in your dashboard. Do not add an SSH or ZNC port. The hostname alone is not a substitute for the exact dashboard link.
- Edit and check. Use the file editor for a text change and Save file. Reload the website and check that links, images and filenames match, including letter case.
A minimal page to try
Save this as index.html on your computer. Replace the sample heading before uploading:
<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,initial-scale=1"> <title>My shell website</title> </head> <body> <h1>Hello from my DWShells website</h1> <p>This is my personal page.</p> </body> </html>
Files and scripts
New folder creates a directory in the current location. Upload file transfers one file. The editor saves text files; it does not build a framework or enable unsupported runtimes. Static HTML is a good first check. PHP or other dynamic hosting depends on your effective permissions. Deletion is permanent in the file manager; keep your own copies.
Troubleshooting
| What you see | What to do |
|---|---|
| Old page still appears | Check you edited the selected shell’s public_html, saved the file and refreshed the browser. |
| An image is missing | Match the filename and relative path exactly; Linux paths are case-sensitive. |
| Upload is too large or a folder will not upload | Use SFTP and check the disk allocation. |
| Page is unavailable | Check shell status and the exact HTTPS link, then report the URL and error to staff. |
Example directory layout
| Location | Purpose |
|---|---|
public_html/index.html
|
Your entry page |
public_html/style.css
|
Public stylesheet |
public_html/images/logo.png
|
Public image referenced by your HTML |
Outside public_html
|
Private account files; keep credentials and backups out of the website |
Use relative links such as images/logo.png when the page is in public_html. A file named Logo.png is different from logo.png.
Safe updates
Download a copy of the existing page, upload your replacement, then test the live HTTPS link. Do not use world-writable permissions or publish configuration secrets to fix a hosting error. Ask staff about unsupported runtimes and commercial hosting before deploying them.
Rules and support
This guide describes how to use the service; it does not replace Signup and Rules. Join #DWShells on irc.darkworld.chat using TLS port 6697 for help. Use the customer portal for your actual status and connection details. Never share credentials or recovery links.