Getting error while creating WebID, but it is actually created and listed after page refresh
See original GitHub issueWhen I try to create a WebID using latest webid manager, it is showing an error saying Error creating webid on the network
and If I switch to list tab from create tab it lists the id which was just throwing the error.
Note: I used my old account which was created before rc2, for creating webid. Tested on Windows and Ubuntu cc: @bochaco
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
React Error Message Persists even after Refreshing the page
In the Register Page, I add all errors in a Message component. During development, whenever a React error occurs (like Cannot read properties...
Read more >web app does not work after page refresh #272 - GitHub
To replicate the issue: Create a new React application by using create-react-app; Follow the 'Quick Start' documentation for React up to 'Read ...
Read more >Solved: Something went wrong Try refreshing the page. Refr...
Solved: Something went wrong Try refreshing the page. Refresh If the problem persists, contact Atlassian Support or your space admin with ...
Read more >SharePoint Online: Get Site Collection ID (or Web ID) using ...
This gets you the ID of the site, which is a GUID. The other way to get the site ID is to use...
Read more >Query by date or current iteration in Azure Boards
To list work items based on when they were created, closed, ... If you're new to creating queries, see Use the query editor...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After further research I’m quite sure this has to do with the revocation of an app. After revoking one of the apps that has encrpyted and stored entries in the
_publicNames
container, and there is another app which is trying to decrypt them it cannot. I presume it’s because they were re-encrypted with new keys during the revocation process.I thought that re-authorising any of apps they should be able to decrypt the entries again, but from my quick test it’s still not able to decrypt the enctries. But for sure I got an account to be in the same state as yours @safesurfer after I revoke the WHM. I’ll try to reproduce it tomorrow again and report the steps more clearly and hopefully be able to report it in a bug, don’t know yet but if it is related to revocation it’s likely to be in the safe_client_libs revocation algorithm, we’ll see…
QA verified