Website URL for subpages not showing up after domain forwarding - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Website URL for subpages not showing up after domain forwarding error on your web browser.
Problem : I have a wordpress site setup on an amazon ec2 server. I created an elastic ip, forwarded my domain name (registered with namecheap) to that ip, and setup everything to properly work through aws's route 53.
The domain name, say www.example.com redirects correctly to the home page of my WordPress site, but when I navigate to a specific page on the site the URL does not change correctly to say example.com/page.html, but remains the same (example.com). This does not happen if I directly go to the ec2 elastic ip address, only when using the domain name redirect.
Am I doing something wrong here? How can I get the correct URL to appear through the domain name?
Solution :You don't want to "forward" your domain name. That's what's causing this behavior.
You need to create a DNS A record for the hostname that you want to point to the elastic IP.
https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-do-i-set-up-host-records-for-a-domain
We hope that this article has helped you resolve the domains, redirects, wordpress error in your web browsers. Enjoy browsing the internet uninterrupted!
Comments
Post a Comment