Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bitnami Wordpress Image] www vs non www domain - different content displayed #1747

Closed
ae4021ff opened this issue Jan 5, 2025 · 3 comments
Closed
Assignees
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@ae4021ff
Copy link

ae4021ff commented Jan 5, 2025

Platform

Google Cloud Platform

bndiagnostic ID know more about bndiagnostic ID

n/a

bndiagnostic output

No response

bndiagnostic was not useful. Could you please tell us why?

The server itself is running fine, I think this issue might be a network configuration error

Describe your issue as much as you can

This may not be the right place for this, but i'm running out of options. When I access my wordpress site using www. before the domain, I get an entirely different version of the site, an older version, without the most recent blog posts, and a different home page. When I just access the plain domain (without www.), it's totally normal. I've never seen this behavior before and I know i'm just missing something. I've checked DNS at my domain registrar (GoDaddy) and that all looks fine. I tried editing .htaccess to force a redirect, but the same behavior persists. If anyone could point me in the right direction, i'd be eternally grateful :)

@ae4021ff ae4021ff added the tech-issues The user has a technical issue about an application label Jan 5, 2025
@github-actions github-actions bot added the triage Triage is needed label Jan 5, 2025
@jotamartos
Copy link
Collaborator

I've checked DNS at my domain registrar (GoDaddy) and that all looks fine.

Did you confirm both domains (www and non-www) point to the instance's IP address?

https://www.whatsmydns.net/

If that's correct, please confirm you do not have any specific virtual host for the domains under /opt/bitnami/apache/conf/vhosts.

@ae4021ff
Copy link
Author

ae4021ff commented Jan 8, 2025

Thank you for the response! Yes, both www and non-www point to the same public IP (our VPS in GCP). I looked through .htaccess, httpd.conf, and bitnami.conf, the only virtual hosts I see setup are the ones that redirect http to https. I tried adding (separately, in each of these files, then removing after) redirects, following other posts in the community for syntax. So far no luck at all. If I copy a URL path to a document or page or something from the 'non-www' version of the site, and use that path with the www. version of the site, I can still access the content, so I'm confident we're still pointing to the correct site, but I cannot figure out why I get 2 different versions of our homepage and no recent blog posts with the www. version.

Let me ask you this, we have a staging site, but it's not done conventionally (at least I don't think). When we're ready to move staging to production, we clone the staging site, change the public IP assigned to it to make it prod, and assign the public IP from prod back to staging, which essentially flips them. Poking around in the current prod site, i'm seeing references to the staging site (which makes sense), other than the fact that this might not be the best way to accomplish this, are there other areas where redirection might occur that i'm just missing?

Thank you SO much for your support.

@ae4021ff
Copy link
Author

This can be closed. It was an SSL issue. Renewed it and recreated the www to non www redirect, which fixed it. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants