Getting 403 user unauthorized while connecting to my solid server with angular demo app

[jason076]

@ztein

I’m not familiar with the EAI_AGAIN error, but it looks node related - timeout on dns lookup according to this post: javascript - What's the cause of the error 'getaddrinfo EAI_AGAIN'? - Stack Overflow

So I would check if hostnames are ok everywhere - make sure you also have the jason07 subdomain correctly setup in the host file or dns.

I managed to get rid of the EAI_AGAIN error. I am running the solid server in a docker container and the problem was that the container had no internet access. I could not ping the public google DNS at 8.8.8.8 from inside the container, but the server answered my request anyway. That behavior was a little bit weird. It seems that a container restart fixed this. Now the server starts without any errors, but the issue with the null agent still persist.

@megoth

It sounds like you might be experiencing a known regression bug on NSS v5 . There is a fix waiting to be merged , but stuff takes a bit of time.

If you’ve set up the server by cloning the NSS repo, you can check out the branch fix/faulty-403 if you want to try out the fix.

I have installed solid from npm in a docker container. I have done a rollback to version 4.4.1 and now the angular app has access as intended. If I have some time to test the fix I will post the result here.
Thank you for your answers!