Using Websockets Error

Hello all,

I’m trying to use the websockets api for ESS and I am following the example, however I am receiving and XHR error: GET, which is then followed by an uncaught promise error: Uncaught (in promise) Error: Unable to fetch negotiation gateway url: returned [403] Forbidden. I am not sure how to resolve this error as the container url has public read and write agent access, and the url’s I am using all seem correct. Any help would be appreciated, thank you.

@gaz009 hi, can you try updating to the latest version, we did a release yesterday that should fix this.

edit: You’ll need to upgrade both @inrupt/solid-client-notifications and @inrupt/solid-client for the fix.

1 Like


Yes, I upgraded today and the Negotiation Gateway error was resolved, thank you guys for doing that! However, the GET https://…/.well-known/solid url is still sending back a 401 error - is this intended behavior or an error on my end?


We do expect with the API used (getWellKnownSolid) to receive at least one network error, as this changes between two different versions of the enterprise solid server; we first try at the root of the storage server, then fallback to within a pod. There is ongoing work on a standard for storage server metadata.

The 401 network error isn’t anything to worry about.


Okay, thank you!