You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[2024-10-27 10:42:50] ERROR: {Operation ID: 4ffe81fa-2ae7-446b-a474-a1d0097356d6} [v1_0_0HandleStoreRequestCommand] (Command ID: a2156044-c104-43f3-9fbb-eb5c419ecbfd) Command error (PublishLocalStoreRemoteError): Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].
The text was updated successfully, but these errors were encountered:
Issue description
The system is unable to fetch a required JSON-LD document from a remote URL, resulting in a failure
Expected behavior
The system should successfully retrieve the JSON-LD document from the specified URL and process its content without errors.
Specifications
Error logs
[2024-10-27 10:42:50] ERROR: {Operation ID: 4ffe81fa-2ae7-446b-a474-a1d0097356d6} [v1_0_0HandleStoreRequestCommand] (Command ID: a2156044-c104-43f3-9fbb-eb5c419ecbfd) Command error (PublishLocalStoreRemoteError): Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].
The text was updated successfully, but these errors were encountered: