nodeSolidServer / nodeSolidServer/node-solid-server
Error fetching openid configuration: 502 Bad Gateway
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I get an error when running the server behind NGINX. NSS and NGINX are running on two different machines.
I do solid start with the following config:
{
"root": "/users/pheyvaer/nss/data",
"port": "8443",
"serverUri": "https://dev.inclusie-in-4d.ilabt.imec.be",
"webid": true,
"mount": "",
"configPath": "./config",
"configFile": "./config.json",
"dbPath": "",
"sslKey": "privkey.pem",
"sslCert": "fullchain.pem",
"multiuser": true,
"enforceToc": false,
"disablePasswordChecks": false,
"supportEmail": "pieter.heyvaert@ugent.be",
"server": {
"name": "Inclusie in 4D",
"description": "",
"logo": ""
}
}
I get this error
Error registering a new client: Error: Error fetching openid configuration: 502 Bad Gateway
at /users/pheyvaer/.nvm/versions/node/v12.19.0/lib/node_modules/solid-server/node_modules/@solid/oidc-rp/src/onHttpError.js:32:17
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
response: Response {
size: 0,
timeout: 0,
[Symbol(Body internals)]: { body: [PassThrough], disturbed: false, error: null },
[Symbol(Response internals)]: {
url: 'https://dev.inclusie-in-4d.ilabt.imec.be/.well-known/openid-configuration',
status: 502,
statusText: 'Bad Gateway',
headers: [Headers],
counter: 0
}
},
statusCode: 502
}
A wildcard certificate is implemented for the *.dev.inclusie-in-4d.ilabt.imec.be. I'm also wondering where the .well-known/openid-configuration is coming from. Is it something that is provided by NSS?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failing request to /.well-known/openid-configuration and the stack entry at node_modules/@solid/oidc-rp/src/onHttpError.js, then trace how NSS and NGINX route it between the two machines. Done means identifying the source of the 502 and documenting or correcting the relevant server or proxy configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nginx, node.js
- Domain
- authentication, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100