WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Unable to access in local network (7 posts)

  1. Eck
    Member
    Posted 5 years ago #

    My site is http://3ck.us - it should load fine for anyone viewing this post. However, it will not load for me since it is hosted here at my house in my local network (it's on the same external IP as me).

    Though I could access wordpress just fine until today (and absolutely nothing has changed), now I cannot access it from within my network in any of the following ways:
    1. By typing 192.168.1.100 (the IP of the server)
    2. By typing http://3ck.us
    3. By typing localhost while on the server
    4. By typing 127.0.0.1 while on the server

    BUT, all of those work for everything else except wordpress. For example, http://3ck.us/quad and all variations work.

    Again, I used to be able to access wordpress both internally and externally in regard to my home network. I even found the last time I could in the server logs: 3:04 PM. After that, no go.

    In summary, I believe this to be a wordpress issue because I can access everything BUT wordpress from within my network, and can access everything including wordpress from outside.

  2. Eck
    Member
    Posted 5 years ago #

    And now, again without changing _ANYTHING_, it works.

    I'm glad it works, but I'm wondering what caused it to not work and how to prevent this issue from happening again.

  3. Eck
    Member
    Posted 5 years ago #

    Update: It started doing it again. And here are more specifics:

    When trying to access http://3ck.us (both from inside and outside my network), I get "Network Error (dns_unresolved_hostname)" aka "Internet Explorer cannot display the webpage." It's not get a 404 error or anything.

    However, if I rename index.php to something else and add an index.html for testing purposes, it loads http://3ck.us both inside and outside my network.

    Also, here is my apache log showing what happens when trying to access it (and it gets the DNS error):
    IP Address - - [24/Nov/2008:15:53:05 -0600] "GET / HTTP/1.1" 301 -
    IP Address - - [24/Nov/2008:15:55:18 -0600] "GET / HTTP/1.1" 301 -
    IP Address - - [24/Nov/2008:15:56:45 -0600] "GET / HTTP/1.1" 301 -
    IP Address - - [24/Nov/2008:15:57:14 -0600] "GET / HTTP/1.1" 301 -
    IP Address - - [24/Nov/2008:15:57:49 -0600] "GET / HTTP/1.1" 301 -

    And then my log when I use index.html (which is the readme file, renamed):
    IP Address - - [24/Nov/2008:16:00:49 -0600] "GET / HTTP/1.1" 301 -
    IP Address - - [24/Nov/2008:16:00:53 -0600] "GET /quad HTTP/1.1" 301 230
    IP Address - - [24/Nov/2008:16:00:53 -0600] "GET /quad/ HTTP/1.1" 200 3438
    IP Address - - [24/Nov/2008:16:00:53 -0600] "GET /icons/blank.gif HTTP/1.1" 304 -
    IP Address - - [24/Nov/2008:16:00:53 -0600] "GET /icons/back.gif HTTP/1.1" 304 -
    IP Address - - [24/Nov/2008:16:00:53 -0600] "GET /icons/image2.gif HTTP/1.1" 304 -

    Does that clear anything up? Why is this randomly happening?

  4. peiqinglong
    Member
    Posted 5 years ago #

    What you might consider doing is modifying the HOSTS files on your computer (and ever other computer you wish to access the local site from).

    Do a search on your computer for Hosts or Host and edit it in notepad. Put in the IP address of you web server and then hit tab and put in 3ck.us. All done.

  5. Eck
    Member
    Posted 5 years ago #

    That still doesn't solve the issue. It's not a problem with the DNS, it's a problem with wordpress. Even if I type in the IP address (127.0.0.1 from the server, or the actual IP address from another computer inside or outside of the network), it still won't resolve with index.php being the go-to file.

    It will load index.htm fine every single time if I rename wordpress's index.php to anything else. It will not display when attempting to load the wordpress index.php file.

  6. Eck
    Member
    Posted 5 years ago #

    And now it started working again. There has to be some explanation behind this.

  7. Eck
    Member
    Posted 5 years ago #

    I'm going to make a new post with a more accurate title since the problem happens both inside and outside of the network and call this resolved, even though it's not.

Topic Closed

This topic has been closed to new replies.

About this Topic