nodeSolidServer / nodeSolidServer/node-solid-server

GET https://tonda.inrupt.net/inbox times out

Open
#1,558 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

  1. go to https://inrupt.net/
  2. login as "tonda"
  3. try opening any profile page (in browser), like https://tonda.inrupt.net/profile/card#me, https://tonda.inrupt.net/, https://tonda.inrupt.net/inbox. Or try HTTP GET of https://tonda.inrupt.net/inbox. Everything ends up with timeout ('ERR_EMPTY_RESPONSE' or "Error: socket hang up")

I have another profiles on both inrupt.net and solidcommunity.net and those work just fine. I don't remember doing anything special with the problematic "tonda" profile, but I guess I must have done something (maybe something with permissions).

I don't know where else to report this/investigate how to fix/reset the profile. But even if the profile is broken, I think the solid server should handle it "gracefully".

I have discovered this bug together with https://github.com/inrupt/solid-client-authn-js/issues/981 - I am able to login in my app using this user, but then the "handleRedirect" times out as well (on fetch https://tonda.inrupt.net/profile/card).

Server info

Name

inrupt.net

Details

Running on Solid 5.6.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the timeout against https://tonda.inrupt.net/profile/card, /, and /inbox with the profile and server details in the report, then inspect the server logs for the failing request. Compare the behavior with the working profiles and the related solid-client-authn-js issue; done means the affected profile returns a response instead of timing out.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.