COCKPIT PANEL
A large number of installation mistakes come from path confusion rather than missing PHP features. If the upload folder, public URL, and web server document root do not line up, Cockpit can look broken even when the files themselves are correct.
When to Use This
- You are deciding where Cockpit should live on the server.
- You uploaded the files but the URL does not behave as expected.
- You want to avoid common folder and subfolder mistakes.
- You are moving Cockpit between servers or domains.
What to Understand
- the server folder you uploaded into
- the public URL that points to that folder
- the document root your web server actually serves from
Steps
- Identify the actual folder being served by your host or Apache virtual host.
- Upload Cockpit to the folder or subfolder you intend to expose publicly.
- Open the matching URL in a browser and verify it reaches that location.
- If the page is missing assets or opens at the wrong level, re-check your folder mapping before changing Cockpit itself.
Expected Result
You should be able to explain exactly which public URL maps to which Cockpit folder on disk.
Common Mistakes
- Uploading into one folder and testing another: This is one of the fastest ways to create false install problems.
- Assuming the hosting panel label equals the live document root: Always verify the actual served path.
- Changing app files before confirming the path: Fix routing and document-root mistakes first.
Example Use Cases
- Subfolder install: A reseller uploads Cockpit to a dedicated panel path and confirms the exact URL before proceeding.
- Root-path install: The owner places Cockpit in the main served directory and verifies the browser path lines up correctly.
- Migration cleanup: After moving hosts, the operator confirms the new virtual host serves the intended Cockpit directory.
Related Articles
- How to Verify Cockpit After Upload
- How to Check SQLite Support Before Installing
- How to Confirm HTTPS and Endpoint Access