VaporLock
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Can't access blog over internetIs this a new install of WordPress?
Yes and no. I did a clean install, dropped all the tables from the new DB, and imported tables from my old site (after using myphpadmin to replace all instances of blog.old-example.com with blog.example.com).
And have you tried disabling all plugins as well as switching back to the default Twenty Fifteen theme? And have you tried going to Settings > Permalinks and clicking Save Changes?
yes, yes, and yes
Oh, and what happens if you remove the need for port forwarding and just have things set to port 80???
Haven’t tried that, but I don’t want 80 exposed externally. And if my photo site on my synology server is working fine w/ port forwarding, I don’t see why WP won’t function. Not to mention that http://www.example.com:12345/wordpress/wp-login.php works…
Forum: Fixing WordPress
In reply to: Moved (physically) and now can't access siteYou’re running it off of a home server? Is your home router natting to the interal address of the server? Is your webserver running?
Yes, yes, and yes.
I think I fixed it though. I checked my zonefile and my domain was not directed to my new IP (maybe I didn’t hit save last time??). Correcting that seems to have fixed everything.
So I have some followup questions:
1) On my LAN, typing in the IP (ie, 192.x.x.x/blog) redirects to my domain name (saved in siteurl in wp_options) before loading the blog. Why?
2) When accessing remotely, why can’t you use the IP address, instead of the domain name saved in wp_options? In other words, until my zonefile updated, I couldn’t even access my blog using 74.x.x.x/blog.
3) Is #2, why I can’t access my blog remotely using blog.domainname.com versus http://www.domainname.com/blog? My siteurl in wp_options is listed as “www.domainname.com/blog”, but I have subdomain forwarding set up so blog.domainname.com forwards to http://www.domainname.com/blog.