Ever since I had to change to a Speedstream router instead of my old 2wire (constant and still somewhat present connectivity difficulties), I had been unable to login in to my WordPress install locally. This was because the Speedstream redirected traffic calling the external URL or IP from inside to itself rather than forwarding the request to the server, and because WordPress requires a single fixed URL reference in its database that it automatically redirects to.
I worked hard trying to get the router itself to not do this, but instead the problem was fixable on my computer itself: the hosts file, as I found on this post. You simply edit the hosts file:
$ sudo vi /etc/hosts
and then place an entry like “accessURL externalURL” for another machine, ie:
or modify a localhost line for a local machine (haven’t tried this yet):
127.0.0.1 localhost cosmicosmo.ath.cx
Or possibly you could just do as for another machine and access by the LAN address rather than localhost (haven’t tried this either, just speculation).
This was very quick and easy to do and works like a charm. I haven’t seen what happens if my WAN network access goes down with this method: I imagine it would cause problems accessing any part of the site.
One problem I’ve already found with WordPress and this method is that many links don’t work because they contain the full URL. Examples include the Preview button and the all post links. You must copy the link and past it, replacing the hostname bit. But all the admin links work, at least the ones I’ve tried. Tag autocompletion doesn’t seem to be working either, but I’m not sure if that is a browser compatibility problem with this new 2.7 version or a plugin (simple tags) conflict.