Hi guys, need your help again.
I'm having problem on our page which I shared over on the network. The site works fine on the pc in which the php and html files is being stored. But if access through other pc on the network the page doesn't load it shows HTTP 500 Internal Server Error / Page Cannot be displayed.

Any ideas? please help. Thanks.

Attached is the screen shot of the error. :)

Dani AI

Generated

This thread ended with a working fix reported by and a short diagnostic hint from . The symptom — the site serves correctly on the host machine but errors when requested from other networked PCs — is usually caused by differences in how the webserver process accesses files and resources compared with an interactive user. The checklist below turns that general idea into concrete checks.

  • Confirm file access from the webserver account. Web services often run as a system/service account and do not inherit mapped drive letters. Replace drive-letter paths with UNC paths or move required files into the webroot.
  • Verify PHP include/open settings. include_path, open_basedir, or custom include/require using absolute local paths can break when the request context changes. Use __DIR__ or realpath() to build robust paths.
  • Check webserver configuration and .htaccess differences between local testing and hosted setup (document root, virtual host aliases, rewrite base). Small path mismatches in rewrites commonly trigger server errors only for remote requests.
  • Ensure file and share permissions grant the webserver user read (and write, if needed) rights. On Windows, consider running the service under a domain account when it must access network shares.
  • Temporarily capture errors in a safe way: enable verbose reporting only for debugging and log rather than display in production.

A minimal PHP snippet to enable short-term debugging:

<?php
ini_set('display_errors', 1);
error_reporting(E_ALL);
?>

Do not leave display enabled on a production intranet; prefer logging with error_log() and consult the server error log for the full trace. Other remote-only causes include incorrect host headers, proxy/firewall rules, or antivirus/SMB access restrictions.

Recommended Answers

All 2 Replies

Member Avatar for Member #119018

You will need to check the server's error log to see what the problem is.

thanks for the reply.. able to figure out.. path problem

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.