id edits not working (committing)

[Jaxo]

I have a few blockstack ids and edits work on only 1 of them.

One of my id's is latone.id. It's the first one I created. It's verified. Edits to latone.id work fine, i.e., when I make & save a change on my local blockstack client, it soon is committed and appears on the blockchain.

Edits on my other id's don't work, e.g., square.id. I make local edits, save, and the changes never commit & appear on the blockchain, and disappear locally when I refresh.

The only differences between latone.id and all my other id's is latone.id was created first and it's fully verified (of course, I can't verify the others since I can save edits).

Any ideas before I try to dig into the logs/wire to see what's happening?

--joe (latone.id)

[kantai]

Hi @Jaxo --

If you open your browser's javascript console when you edit the profile, do you see any errors when you try to save the changes?

[Jaxo]

Here's the error when I try to save:

 Failed to load resource: the server responded with a status of 401 (Unauthorized)

Looking further, when I switch to the id's page (More), I get a couple 404's. Then, if I select one of the id's on the page and go Back, I see the following, which likely leads tot he 401 above:

 VM45:1 GET http://localhost:6270/v1/names/vacationrentals.id net::ERR_INVALID_HTTP_RESPONSE

I occasionally see one of these, too:

 GET http://localhost:6270/v1/names/hotel.id 500 (Internal Server Error)

Seems like my (local?) id profiles are messed up.

--joe

[kantai]

Ah -- yes, it looks like these errors are stemming from the local background daemon going down. If you stop and restart the blockstack application, that should restore that background process.

[Jaxo]

I had tried (and again just now) but it didn't fix it. In fact, this problem has existed for months, I just never got around to looking into it. --joe

…

On Fri, Mar 9, 2018 at 11:47 AM, Aaron Blankstein ***@***.***> wrote: Ah -- yes, it looks like these errors are stemming from the local background daemon going down. If you stop and restart the blockstack application, that *should* restore that background process. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#432 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABg-3jBbK5q815NX4AysPaRRJxZp2dhSks5tctxAgaJpZM4Sksvx> .

[Jaxo]

Can I get some further help on this? The id's I purchased are rather useless if I cannot update them.

[kantai]

@Jaxo --

It seems like there might be a persistent problem with the background daemon on your machine. Using the webapp version (browser.blockstack.org) should fix that problem -- you can use your keychain phrase to restore the account there (the keys are still stored only on your local machine-- the webapp version is identical to the local version, except it communicates with a hosted daemon rather than a local one). When you restore an account, if you have multiple owned names, you do need to manually add back in those accounts by going to the profiles page (https://browser.blockstack.org/profiles/i/all) and clicking "Create New ID" (this just tells the browser to look for more identity addresses on the blockchain that you own-- you won't have to add a username again, and it should find the content previously uploaded for that name).

[Jaxo]

Thanks for the quick reply, I'll give it a try today. --joe

…

On Thu, Mar 15, 2018 at 7:59 AM, Aaron Blankstein ***@***.***> wrote: @Jaxo <https://github.com/jaxo> -- It seems like there might be a persistent problem with the background daemon on your machine. Using the webapp version (browser.blockstack.org) should fix that problem -- you can use your keychain phrase to restore the account there (the keys are still stored only on your local machine-- the webapp version is identical to the local version, except it communicates with a hosted daemon rather than a local one). When you restore an account, if you have multiple owned names, you do need to manually add back in those accounts by going to the profiles page (https://browser.blockstack. org/profiles/i/all) and clicking "Create New ID" (this just tells the browser to look for more identity addresses on the blockchain that you own-- you won't have to add a username again, and it should find the content previously uploaded for that name). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#432 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABg-3mlOIVylZKFVe9p12Y37XQAcPIc4ks5teoHPgaJpZM4Sksvx> .

[Jaxo]

This mostly worked, Aaron, thank you! I suspect my problem is/was due to what I'm about to complain about now: Here are the id's (names) I purchased that were properly restored in my id list after following your instructions, and that I can now successfully edit: *latone* *tesla (+ weather on the same id) * *square* *hotel* *maps* *lottery* *realestate* However, several id's that I had problems with in the past--and were listed on my local blockcstack id list--were not restored in my id list after following your instructions. Are you able to look into these names to see what the problem is? vote dating energy vacationrentals As an example, you can see from the Blockstack explorer *lottery.id <http://lottery.id>* and *vacationrentals.id <http://vacationrentals.id> *were established in close (time) proximity to one another (since I was purchasing a set of names all at once). I don't know enough about the Blockstack structure to try to find out where the problem is from there (though I'm sure this article will likely help, https://medium.com/@ dougvk/end-to-end-blockstack-identity-and-profile-management-9faaed2a4a06).

…

--joe - latone.id - ID-1Nzcxb9gx9pfBLhgovckWE5ZcztmJqJts3 - - tesla.id - ID-1CBQmqrAFCd1Kseg6EgXJNKHropUehraaF - - *Add username* - ID-1122QB9rG6L6jAb3kfsmqKAE5ZP94DgPUu - … Transfer username from Onename to this ID - square.id - ID-12k1u1kAdmMT9kXgJ9funjeMWyrkKkQd4K - Default ID - *Add username* - ID-1DFQxFJehzm72FFkeQWm7MNsYhR1hZhV9y - … Transfer username from Onename to this ID - hotel.id - ID-1Aharc92Wf1ofofVjT3uxyKezG1eJ1PgSB - - *Add username* - ID-17XHh5YwveXRB98ZW5iB9ZudkRddhuqmb8 - … Transfer username from Onename to this ID - maps.id - ID-1NmjCoSRBXbykMN8NmTwfMWchSZnTQqqKx - - *Add username* - ID-1JPfc5oKCwrHP3bH3Ud31f6VjvnWYuosGP - … Transfer username from Onename to this ID - lottery.id - ID-1JxTR3vEMhifLCWdmb3DG9p2gchNFuSyvu - - *Add username* - ID-1JRjgNnPxyvHSYyTFK6GGY46mqgw7pF3rv - … Transfer username from Onename to this ID - *Add username* - ID-14GnFiphrMEJaNfqRVhEUaw5h3nNrrn5A6 - … Transfer username from Onename to this ID - *Add username* - ID-1H5JUcUHwHBtnos2Lk3zoQ4yDqYBt8QmPu - … Transfer username from Onename to this ID - realestate.id - ID-192LLF2K94orvmAHhoV17wTm8QouVGotqJ - - *Add username* - ID-14QjAa9QTVv9Tfmom356v82Ddcpxf5CHdy - … Transfer username from Onename to this ID - *Add username* - ID-121CHBsyi44vGg33Lk7kYTBB9DXBcHLHSF

On Thu, Mar 15, 2018 at 8:00 AM, Joe Latone ***@***.***> wrote: Thanks for the quick reply, I'll give it a try today. --joe On Thu, Mar 15, 2018 at 7:59 AM, Aaron Blankstein < ***@***.***> wrote: > @Jaxo <https://github.com/jaxo> -- > > It seems like there might be a persistent problem with the background > daemon on your machine. Using the webapp version (browser.blockstack.org) > should fix that problem -- you can use your keychain phrase to restore the > account there (the keys are still stored only on your local machine-- the > webapp version is identical to the local version, except it communicates > with a hosted daemon rather than a local one). When you restore an account, > if you have multiple owned names, you do need to manually add back in those > accounts by going to the profiles page (https://browser.blockstack.or > g/profiles/i/all) and clicking "Create New ID" (this just tells the > browser to look for more identity addresses on the blockchain that you > own-- you won't have to add a username again, and it should find the > content previously uploaded for that name). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#432 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABg-3mlOIVylZKFVe9p12Y37XQAcPIc4ks5teoHPgaJpZM4Sksvx> > . >

[kantai]

However, several id's that I had problems with in the past--and were listed on my local blockcstack id list--were not restored in my id list after following your instructions. Are you able to look into these names to see what the problem is? vote dating energy vacationrentals

It looks like vote.id expired -- if you tried to register it at some point, that registration probably failed.
(https://core.blockstack.org/v1/names/vote.id)

The other names all appear to be correctly registered -- though it looks like they are at pretty high indexes in your keychain (see the /12/ in the profile URL of https://core.blockstack.org/v1/names/dating.id) -- you may need to add a lot of IDs before you'll see it (there was a bug at one point which hid half of the ids in a keychain, so while that index may have been 12 at the time you registered that name, that's probably actually your 24th or 25th identity address).

[Jaxo]

*>you may need to add a lot of IDs * ok, thanks, this is what i suspected but i didn't know they were quite that high. i confess i was playing around a lot with id's that day and may have created/deleted many of them. btw, can we now delete id's, e.g., unnamed id's? i'd like to get rid of all these unnamed ones.

…

--joe

On Thu, Mar 15, 2018 at 10:57 AM, Aaron Blankstein ***@***.*** > wrote: However, several id's that I had problems with in the past--and were listed on my local blockcstack id list--were not restored in my id list after following your instructions. Are you able to look into these names to see what the problem is? vote dating energy vacationrentals It looks like vote.id expired -- if you tried to register it at some point, that registration probably failed. (https://core.blockstack.org/v1/names/vote.id) The other names all appear to be correctly registered -- though it looks like they are at pretty high indexes in your keychain (see the /12/ in the profile URL of https://core.blockstack.org/v1/names/dating.id) -- you may need to add a lot of IDs before you'll see it (there was a bug at one point which hid half of the ids in a keychain, so while that index may have been 12 at the time you registered that name, that's probably actually your 24th or 25th identity address). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#432 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABg-3kVGINj2VZEDM2muBVlx4GQR6T8zks5teqtwgaJpZM4Sksvx> .

[ghost]

@kantai @Jaxo , assuming this one can be closed?