The word “localhost”, or an internal network ip address ( 192.168.x.x -or- 10.x.x.x ) in your General Settings > addresses, means your blog will only be accessible to the machine on which it is installed, or other clients within your LAN, respectively.
If you want your site to be available from the web, the addresses need to contain your domain name, and your router needs to forward port 80 to your server.
Thank you ClaytonJames, I have a look at those settings. Yes my router is already set up to forward, thank you.
Do you by chance know what file contains the information form the General Settings if something goes wrong.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
If something goes wrong with the URL settings at Settings/General, you’ll have to access your WordPress database via phpMyAdmin (most hosting providers offer this in their control panel) and manually change the siteurl and home values.
Thank you, just did that but I have a question, should both be the same? What if you created a folder called “blog” and placed the entire WordPress files in there does that affect these setting? Would you then change the settings site and home URL to http://www.example.com/blog ?
Because I basically left the default OSX site as is , created a new folder for the WordPress blog and set that up as the default.
Webserver/Library/Documents/WordPress -> is the location of the files
Moderator
James Huff
(@macmanx)
Volunteer Moderator
If the blog exists in a /blog/ directory at example.com then both should be http://www.example.com/blog
It seems I messed it up, kinda of half working now. I’m only testing right now so I will have to figure out what changed. But now it’s not possible to even get into the dashboard and with not have reference to localhost you can’t even modify it. The only thing I can do is manually change the Site and Home URL through PhpMyAdmin.
I may need to select the Override All setting as well to get it completely working.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
You can’t use example.com/blog if example.com isn’t setup and pointing to your server with enough time to propagate to your ISP’s DNS cache.
No no I messed up, I mistakenly added the “Sites” folder in the path in the database, because I installed WordPress under my accounts Site folder. It’s all working again locally for now.
See the problem is this is a development server, and I’m using DynDNS to track my dynamic IP, so when someone types in the domain name its resolved through DynDNS so again if the registered name is http://www.mytestserver .com, its then resolved through DynDNS as mytestserver.dyndns.org and that translates to the server.
We are developing a real estate site utilizing WordPress so we want the client to have the ability to view the site.
DynDNS so again if the registered name is http://www.mytestserver .com, its then resolved through DynDNS as mytestserver.dyndns.org and that translates to the server.
Not necessarily true.
DynDns no longer allows wild-carding with free accounts. Unless you have a paid account, take that into consideration.
Step 1) enter your exact DynDns domain name in the General Settings page of your dashboard. www, or non-www, makes all the difference in the world with free DynDns service. Remember, no wild-carding with the free service.
step 2) assign your “server” a static internal network ip address.
step 3) install a DynDns Dynamic Update client on one of the machines on your internal network, or activate the DynDns update features that may already be present in your router.
step4) port forward ports 80/8080 to static server ip address (which you have done)
step5) if you need more than one site, it will mean understanding and configuring virtual host containers in apache/httpd.conf.
Ah wait I never forwarded port 8080,,I’ll do that and adjust my firewall accordingly. Yes I had the DynDNS address correct then.
I don’t think forwarding 8080 is a major issue. Can you describe the problem you are still having?
Well what I had done was I copied all the WordPress files into the default web server folder and then changed site and home url to DynDNS address. I had to connect through another service to check it and the default page was missing the header graphic and it looked like other graphics were missing but the template was centered.
Sounds like you are on track.
Thank you. Got it all working, cleared all the caches. Now working remotely but now how do you work on it locally, do most make all their modifications then once they are ready , publish it. I may have to create 2 databases, one for production and one for testing. Maybe opening port 8080 was holding something back as well.
The site obviously does not resolve locally because the webserver and development server are the same so I get my router administration page popping up at the localhost prompt. But that is minor at this point.
Thanks for your quick responses, they really helped, I almost called it a night but since you were putting in a good effort to help me out, I felt it only fair to put in the same effort.
You should be able to resolve it locally ( from the browser located on the server ) in most cases by adding a couple of entries to the hosts file on the server:
127.0.0.1 yoursite.dyndns.com
127.0.0.1 ww.yoursite.dyndns.com
( Use “www” prefix when you make the entry in the hosts file )
Be sure to leave spaces between 127.0.0.1 and your domain. That should let you resolve the domain name to localhost ( 127.0.0.1 ) in the browser on the server.
If in doubt about hosts file usage, consult references for OS X ( any ‘nix OS ) on Google, or man pages if applicable.
