HTTPD Mod User DIR
Enable or disable Apache UserDir per domain in Eenos and verify temporary user-directory access.
Open Web Servers → Apache HTTPD → HTTPD Mod User DIR.
This page controls per-domain access through URLs such as http://example.com/~username/. It does not create a hosting account or change normal domain DNS.
Read the table
| Column | Meaning |
|---|---|
| Website | Domain link for normal website access. |
| UserDir URL | Generated HTTP user-directory link for the domain and account. |
| Owner | Account associated with the domain. |
| UserDir Status | Enabled when the stored UserDir setting is on; otherwise Disabled. |
| Action | Enable/disable control, or Suspended for a suspended account. |
Use search, sorting and pagination. The initial page size is 25, with 10, 50, 100 and All available.
A displayed link or Enabled status is not a connectivity test. The link still depends on the domain reaching the intended server and on the generated web configuration and application behavior.
Enable temporary access
- Find the correct domain and owner.
- Click Enable UserDir.
- Review the domain and access warning in the dialog.
- Click Enable, or Cancel.
- Read the result and test the displayed UserDir URL.
Content becomes accessible through another URL
The panel warns that UserDir can expose account content before normal domain routing is available. Enable it only when required and disable it after temporary access ends. The displayed link uses HTTP; do not treat it as a secure channel for credentials.
Disable access
Click Disable UserDir on the row, verify the domain and click Disable. Check both the UserDir URL and normal website afterward. Disabling this path is separate from suspending an account or removing its website.
What is saved
The request carries the row's domain, user and on/off status. The server requires the corresponding domain configuration to exist. It updates the domain's UserDir setting and its Nginx UserDir setting when that configuration is present, then invokes the domain virtual-host builder.
The reported success follows the metadata write; it does not prove every build/reload step or HTTP request succeeded. Check generated configuration and logs if the observed behavior differs from the saved status.
Suspended accounts have no toggle action in the table. Demo sessions cannot change the setting. Missing domain data or I/O errors require administrator investigation; do not recreate unrelated account files to bypass the error.