"No valid WordPress.com Connection" error, site reverted to older version

Your site is loading at SiteGround for me. I’m assuming from the description, you were seeing the old site at BlueHost for a bit?

After a while, the DNS change should have propagated to your ISP, so you should be seeing the site at SiteGround (and therefore all of the “lost” content too).

If you run a DNS query again, are the nameservers showing as pointed to SiteGround for you?

No, the version I was seeing (and still am) is a much older one.

I run a DNS query and all the nameservers point to Siteground now. Still I am seeing the older version.

I don’t see how changing domain NS would affect Jetpack and the whole website, even the favicon is from a previous version, I had updated long time ago.

I have changed the NS 3 days ago, if it was that the problem, shouldn’t it be ok by now?

What can I do?

The latest post I’m seeing there is https://www.swiftbranding.com/plume-font/ from November 12, 2015.

I’m guessing there’s more recent content?

Are you using any sort of caching plugin, or do you see a “Clear/Purge Cache” button in your Dashboard or admin bar? If so, would you please try clearing the cache?

Note: You do not need to install a caching plugin at this point just to clear a cache you don’t have. If you don’t have a caching plugin or a way to clear a server-level cache, just say so. ??

Additionally, Siteground has a cache you can clear in cPanel, so make sure you do that too.

Yes there’s more recent content.

I have the W3 Total Cache plugin, just performed an “Empty All Caches” through the Plugin and also a master flush cache trough Siteground Admin panel. Nothing fixed ??

Still is beyond me how changing the NS on GoDaddy from Bluehost to Siteground can cause all this, if that’s the reason, but apart from that I haven’t done anything else in the last few days when this happened.

Is it possible that the new content was actually hosted on Bluehost?

No, I am pretty sure that all this content was created after I had transferred to Siteground from Bluehost.

I don’t know, should I change the NS back to Bluehost(I have 3 more months active subscription there)in case the content becomes visible again, make a backup, and then change to Siteground again? I am not even making sense, I am kinda over my head here with all this.

If you saw the content, it’s somewhere, it’s pretty much impossible for only a portion of it to automatically vanish.

At this point, I have to assume the new site was actually at DreamHost, and when you switch to SiteGround, you began viewing the old site at SiteGround.

Currently, that’s the most likely possibility.

you mean Bluehost and assuming that’s the issue, what can I do re remedy it?

Should I do what I suggested? Revert NS to Bluehost, wait to see if the content pops back up and then re-revert to Siteground?

Is this thing even viable?

That’s what I’d try. Change the nameservers back to BlueHost, wait for them to propagate, then see if your site has more recent content on Bluehost, or less.

Assuming Bluehost has the site with the most recent content, export the recent months from Tools -> Export, swap the nameservers back to Siteground and wait for them to propagate again. Then, just import the new content into the Siteground-hosted site at Tools -> Import -> WordPress.

Thank you James, I guess it’s my last shot, I can’t think of anything else.

Thank you so much for trying to give me a hand out of this mess. The whole NS back and forth changing will take a couple of days I assume, so we’ll have to wait and see if eventually I’ll manage.

Thank you again for your help, it is much appreciated.

When a domain is registered or altered, there is a process called propagation, where information about the domain name is passed to internet service providers all over the world. This process can take up to 72 hours (though usually much less). During that time, your domain may go to its old location, and you may also receive a warning message in your browser about “redirect errors.”

If you still have trouble viewing the site after 48 hours have passed, please try clearing your browser’s cache.

If that doesn’t work, try clearing your local DNS cache: https://support.opendns.com/entries/26336865-Clearing-the-DNS-Cache-on-Computers-Servers-and-Web-Browsers