XAMPP - Access to the requested object is only available from the local network

XAMPP - Access to the requested object is only available from the local network

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Deciphering XAMPP's "Local Network Only" Restriction for phpMyAdmin

When attempting to access a remote instance of Apache running on XAMPP, specifically targeting phpMyAdmin via IP address, you will likely encounter an immediate Access forbidden warning. The error message explicitly states that the requested object is only available from the local network. While this restriction acts as a security layer intended to prevent unauthorized external access to sensitive administrative tools, it can be frustrating when trying to debug a development environment or expose a service for testing within a private subnet.

This behavior is not a bug but a deliberate configuration enforced by XAMPP's default httpd-xampp.conf file. Unlike standard Apache installations where permissions are often managed through .htaccess or global httpd.conf directives alone, XAMPP bundles these restrictions directly into its modular configuration to ensure that sensitive paths like server-status, phpmyadmin, and xampp are not exposed to the public internet by default.

The most common troubleshooting step involves modifying the <LocationMatch> block within httpd-xampp.conf. The typical solution suggests adding or altering the following directive:

<LocationMatch "^/(?i(?:xampp|security|licenses|phpmyadmin|webalizer|server-status|server-info))">
    Order deny,allow
    Allow from all
    ErrorDocument 403 /error/XAMPP_FORBIDDEN.html.var
</LocationMatch>

However, simply appending this block to the end of the file often fails to resolve the issue. This discrepancy usually points to one of two underlying problems: the version-specific configuration logic or the presence of overriding directives elsewhere in the Apache stack. In modern Apache versions (2.4 and above), the Order and Allow/Deny syntax is deprecated in favor of Require. If your XAMPP installation is running a newer Apache core, the legacy Order deny,allow combined with Allow from all might be ignored or evaluated differently depending on where this block sits relative to other Location directives.

A more robust approach involves targeting the specific directory path directly using <Directory> blocks. If your XAMPP installation resides in C:/xampp, you can attempt to override the restriction by defining permissions for the phpMyAdmin root:

<Directory "C:/xampp/phpMyAdmin">
    AllowOverride AuthConfig Limit
    Require all granted
    ErrorDocument 403 /error/XAMPP_FORBIDDEN.html.var
</Directory>

It is crucial to note that Require all granted is the modern equivalent of Order allow,deny followed by Allow from all. Mixing old and new syntax without verifying your Apache version can lead to confusing results. Furthermore, ensure that you are not inadvertently creating a conflict with a global <Directory> block defined earlier in httpd.conf or httpd-xampp.conf that might be setting a broader restriction.

When these configuration changes yield no results, the issue often stems from how Apache handles virtual hosts or the specific order of processing directives. In some configurations, the XAMPP security module checks for network connectivity at a higher level than the standard directory permission checks. If you are attempting to access the service from a different subnet (e.g., 192.168.x.x vs 10.0.x.x), Apache may interpret the connection as originating from an external, untrusted network if the firewall or router does not explicitly route these IPs as local.

In scenarios where configuration edits persist in failing, consider whether you need to expose phpMyAdmin at all from a remote machine. For production environments, this tool should never be accessible over the public internet without strict IP whitelisting. However, for development workstations within a LAN, disabling the restriction is acceptable. If editing httpd-xampp.conf proves elusive due to versioning issues or hidden overrides, reinstalling Apache with a clean XAMPP configuration can sometimes reset these security flags to their intended defaults, which you can then tailor precisely using modern Require directives.

Ultimately, the error is a feature designed to protect your database credentials and server status logs from prying eyes. Understanding that this is a configurable firewall rule rather than an immutable system limit allows you to tailor the environment to your specific testing needs without compromising the integrity of the underlying software stack.

Our network