Title: Localhost Chrome Remote Debugging Not Working
Last modified: August 5, 2022

---

# Localhost Chrome Remote Debugging Not Working

 *  [Bill Vallance](https://wordpress.org/support/users/bvallance/)
 * (@bvallance)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/chrome-remote-debugging-not-working/)
 * I have a WordPress localhost development website with the following WordPress
   Address and Site Address values:
 * WordPress Address: [https://localhost/IST01](https://localhost/IST01)
    Site Address:
   [https://localhost/IST01](https://localhost/IST01)
 * As you can see, both values match. I am trying to debug this website using Chrome’s
   remote debugging tool on a Samsung Galaxy S9+ (Android 10) smartphone. I can 
   get access to the phpinfo.php file that is located in [https://localhost/IST01/phpinfo.php](https://localhost/IST01/phpinfo.php)
   via Chrome’s Inspect browser tab with no problem. However, when I try to access
   the website using the following access URL, the URL is redirected:
 * Access URL: [https://localhost:5000/IST01/](https://localhost:5000/IST01/)
    Redirected
   URL: [https://localhost/IST01/](https://localhost/IST01/)
 * The port number of “5000” is being stripped from the access URL, which results
   in a “This site can’t be reached” error message.” I suspect that the reason for
   the error is that the Chrome remote debugging port forwarding port number (which
   I have set to “5000”) is being stripped from the access URL because it is not
   present in the Site Address URL.
 * I have the following questions:
 * 1. Is the port number being stripped because of the WordPress Site Address value(
   which doesn’t contain a port number)?
 * 2. How can I fix this problem?
 * Thanks In Advance For Your Help!
    -  This topic was modified 3 years, 9 months ago by [Bill Vallance](https://wordpress.org/support/users/bvallance/).
    -  This topic was modified 3 years, 9 months ago by [Bill Vallance](https://wordpress.org/support/users/bvallance/).
    -  This topic was modified 3 years, 9 months ago by [Jan Dembowski](https://wordpress.org/support/users/jdembowski/).
      Reason: Moved to Fixing WordPress, this is not an Developing with WordPress
      topic

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [George Appiah](https://wordpress.org/support/users/gappiah/)
 * (@gappiah)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/chrome-remote-debugging-not-working/#post-15890238)
 * > 1. Is the port number being stripped because of the WordPress Site Address 
   > value (which doesn’t contain a port number)?
 * Yes.
 * > 2. How can I fix this problem?
 * I would just set up a dummy domain/hostname and resolve it over my network (by
   adding an entry in my devices’ `hosts` file, router, or some other means)… and
   use this as my WordPress site address… instead of using `localhost`.
 *  Thread Starter [Bill Vallance](https://wordpress.org/support/users/bvallance/)
 * (@bvallance)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/chrome-remote-debugging-not-working/#post-15891463)
 * Thanks for the response [@gappiah](https://wordpress.org/support/users/gappiah/).
   I have a few questions about your suggestion:
 * 1. Does the use of localhost differ from using a dummy domain name?
 * 2. Would adding the port number to the WordPress Site Address work? I realize
   I would have to type the port number each time I wanted to reach the development
   website.
 * I REALLY appreciate your help with this problem!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Localhost Chrome Remote Debugging Not Working’ is closed to new replies.

## Tags

 * [chrome](https://wordpress.org/support/topic-tag/chrome/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 2 replies
 * 2 participants
 * Last reply from: [Bill Vallance](https://wordpress.org/support/users/bvallance/)
 * Last activity: [3 years, 9 months ago](https://wordpress.org/support/topic/chrome-remote-debugging-not-working/#post-15891463)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics