Prepare the finished site and a rollback copy
Upload the finished build to the domain's served directory, then check the entry page and its referenced assets over HTTPS.
A deployable static build is the output bundle, not the source project. Obtain the finished static build on your computer, including its entry page, stylesheets, scripts, images and any directories they reference. A source project or build configuration is not necessarily the deployable output. Open the local index.html and inspect whether its links use absolute paths or paths relative to the page. Record the current public site and keep a restorable copy before replacing anything.
Confirm the intended domain and its effective document root first. DirectAdmin documents a typical per-domain public_html directory, but an administrator can customise the document root. Use the directory shown for your own domain or ask support; do not assume that the first public_html you see serves the hostname you are changing.
Upload the deployable files
Use the file manager or a transfer account that your service actually provides. Select the correct domain directory and upload the contents of the built site so the intended entry page sits at the effective web root. If the build creates a top-level folder, check whether you need its contents rather than the folder itself: otherwise the homepage may be one directory too deep. Keep the asset directory structure and filename case intact, because a link to Images/logo.svg may not resolve to images/logo.svg on the server.
Avoid placing source archives, configuration secrets, database dumps or private keys under the served directory. If an existing site is live, upload to a safe staging location where available and arrange a controlled swap; replacing a live index file first can leave visitors with a half-uploaded page.
Test the exact host and representative assets
Open the intended hostname over HTTPS in a fresh browser session. Confirm that the expected homepage appears, then open a second page and several assets directly. Use the browser network panel to identify 404 responses and paths containing an unexpected extra folder. Test the root and www forms if both are meant to work; they may be separate host mappings. If DNS has not yet moved, use an authorised preview method that sends the real hostname to the new hosting target rather than treating a bare server IP as proof.
A successful homepage alone does not prove that navigation, CSS, JavaScript and image paths work. Check a mobile viewport and a deep link as well. Record the exact failing URL, status and browser time if something differs.
For example, an unstyled entry page may mean its CSS path is wrong, the asset failed to upload or a cache holds old HTML. Inspect one failed asset URL and response before rebuilding.
Recover a failed upload without widening access
If the previous site worked, restore the retained files or a tested backup for that same domain. For missing assets, compare the uploaded tree with the build output and correct only the mismatched paths. A hosting placeholder after a complete upload may mean the request reached another document root or server; follow the related default-page guide before deleting more files. If the panel lacks file access, an upload is refused or the path is unclear, stop and ask support to confirm the account entitlement and served root.
Frequently asked questions
Should I upload the project source folder? Usually upload the generated public build, but follow your site generator’s own deployment instructions. A build may reference assets outside a single HTML file.
Does changing the index page publish the site immediately? It affects requests that reach that served directory. DNS, caching and any separate hostname configuration determine which visitors see it. Verify the real host before calling the launch complete.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.