> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/guides/troubleshooting/dashboard/refreshing-dashboard-sub-page-leads-to-404-error.md).

# Refreshing dashboard sub-page leads to 404 error

Current UXWizz dashboards use hash routing: the dashboard page is selected after `#` in the URL. The browser does not send that fragment to the server, so refreshing a dashboard view should load the same application entry page.

1. Open the normal UXWizz dashboard URL and navigate to the affected view again. Replace an old bookmark that uses a path from an older version.
2. If refresh still returns 404, try the installation's `index.html` directly. Check that the file exists and the web server serves the correct application directory.
3. If a reverse proxy is used, ask the administrator to check its base path and forwarding rules. Include the exact failing URL and response status.
4. Reload the dashboard and repeat the refresh check.

Opening the correct URL is possible in your browser. Missing files, directory-index settings, and proxy rules require server access.

Do not enable `AllowOverride All` across Apache to fix current dashboard routing. Keep the application's supplied file-protection rules. NGINX and other supported web servers can serve the dashboard without Apache URL rewrites.

## Older dashboards that use path-based routing

UXWizz versions before 5.0.0 used URL rewrites. For those installations, the original Apache checks still apply:

1. Confirm that the supplied `.htaccess` files exist in the application root and its `server` folder. Enable your file manager's hidden-file view if needed.
2. Check that Apache's rewrite module is enabled. On Ubuntu, use `sudo a2enmod rewrite`.
3. In the site's Apache configuration, allow the supplied rules **for this installation directory only**:

   ```apache
   <Directory "/var/www/uxwizz">
       AllowOverride All
   </Directory>
   ```
4. Replace the path with the real installation directory. Run `sudo apache2ctl configtest`, then `sudo systemctl reload apache2` only if the test succeeds.
5. Open a dashboard sub-page and refresh it. Also check that the `server` directory does not expose a file listing.

This requires server access. On shared hosting, ask the host to enable the supplied `.htaccess` rules for your installation. Do not change every `AllowOverride None` entry on the server. See [Apache's AllowOverride reference](https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride).