Upload the static files to the server directory and bind the domain through Nginx.
Help Center
Quick answers for deployment, access, and page management
This page keeps the most common operational guidance in one place so team members can find the next step quickly.
Use a valid certificate and private key pair, then point Nginx to the correct file paths.
Update HTML and CSS files, reload Nginx, and refresh the browser to check the latest version.
Common Questions
Frequently used help topics
Where should the static files be placed?
A common Windows Nginx path is C:/nginx/html/starriver/. Place index.html, styles.css, help.html, and any assets in that folder.
How do I update the live page?
Replace the old static files on the server, then run nginx.exe -s reload if the Nginx configuration also changed.
Why would HTTPS fail?
The most common causes are a wrong certificate path, a wrong private key path, a domain mismatch, or an incomplete certificate chain.
Can this site be extended later?
Yes. You can continue adding static pages such as service details, case studies, contact forms, or documentation sections.
Support Flow
A simple operational checklist
Check files
Confirm that index.html, styles.css, help.html, and certificate files are all in the expected directories.
Check Nginx
Run nginx.exe -t first, then reload Nginx only after the configuration test passes.
Check access
Verify the domain, HTTPS certificate status, and browser cache when checking the final result.