@rawkode Sorry for the delay. What this means is that you need to update your profile data and re-sign it with the new keys.
We're working on an improved profile update command that makes it easy to do this. We'll have a step-by-step command-line wizard that helps to generate a new valid profile.
With that said, here are the manual steps:
Take a look at https://resolver.onename.com/v2/users/rawkode, current output there is:
"zone_file": "$ORIGIN rawkode.id\n$TTL 3600\n_http._tcp URI 10 1 \"https://blockstack.s3.amazonaws.com/rawkode.id\"\n",
This means that your owner address is 1JNQFBEBQDLMTwaTVGFcNfADceBehfK2a4 and your zonefile is:
_http._tcp URI 10 1 "https://blockstack.s3.amazonaws.com/rawkode.id"
If you go to https://blockstack.s3.amazonaws.com/rawkode.id you'll see that there is data there but it's signed by your old owner keypair. You need to generate your new profile data. This is where a step-by-step wizard can be really helpful. There are two packages blockstack-profiles-js and blockstack-profiles-py that can be used to create and sign a valid profile.
You can upload your data to your storage backend like S3. Let's assume you got the bucket "rawcode" then your URL would look something like https://rawcode.s3.amazonaws.com/rawkode.id.
You can then create a new zonefile like:
_http._tcp URI 10 1 "https://rawcode.s3.amazonaws.com/rawkode.id"
And use the step in this update tutorial to update your zonefile.
We realize that the manual steps are not user-friendly at all and we're working on automating this process for the users. I've started a Github issue and you can track it to see when the new automated way of doing this gets merged. Once again thanks for your patience while we iron out the UX.