Error: Router not found for request ...

[maphew]

TriliumNext Version

0.90.7-beta

What operating system are you using?

Other (specify below)

What is your setup?

Server access only

Operating System Version

Pika Pods container

Description

Pika Pod container log is full of "Error: Router not found for request GET /.well-known/nodeinfo" where the path part changes. A web-crawler maybe? It's okay to keep a record of what things are being looked for, but can it be somewhere other than the container log? Or at least not be so noisy.

Paths looked for so far:

/api/nodeinfo
/.well-known/nodeinfo
/.well-known/webfinger?resource=acct%3Amatt%40www.maphew.com
/.well-known/webfinger?resource=https%3A%2F%2Fwww.maphew.com%2Fapi%2Fcollections%2Fmatt
/.well-known/host-meta
/api/.well-known/webfinger?resource=acct%3Amatt%40www.maphew.com%2Fapi
/api/.well-known/webfinger?resource=https%3A%2F%2Fwww.maphew.com%2Fapi%2Fcollections%2Fmatt
/api/.well-known/host-meta
/api/collections/.well-known/webfinger?resource=acct%3Amatt%40www.maphew.com%2Fapi%2Fcollections
/api/collections/.well-known/webfinger?resource=https%3A%2F%2Fwww.maphew.com%2Fapi%2Fcollections%2Fmatt
/api/collections/.well-known/host-meta
/api/collections/matt
/nodeinfo/2.1
/feed/

Error logs

websocket client connected
websocket client connected
[session-file-store] Deleting expired sessions
Table counts: notes: 504, revisions: 4, attachments: 72, branches: 533, attributes: 554, etapi_tokens: 0, blobs: 375
All consistency checks passed with no errors detected (took 13ms)
websocket client connected
websocket client connected
Error: Router not found for request GET /.well-known/nodeinfo
at file:///usr/src/app/src/routes/error_handlers.js:14:21
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/src/app/node_modules/express/lib/router/index.js:328:13)
at /usr/src/app/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/src/app/node_modules/express/lib/router/index.js:346:12)
at next (/usr/src/app/node_modules/express/lib/router/index.js:280:10)
at Layer.handle [as handle_request] (/usr/src/app/node_modules/express/lib/router/layer.js:91:12)
at trim_prefix (/usr/src/app/node_modules/express/lib/router/index.js:328:13)
at /usr/src/app/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/src/app/node_modules/express/lib/router/index.js:346:12) {
status: 404
}
websocket client connected
websocket client connected

[eliandoran]

Now it should look like this:

404 GET /.well-known/nodeinfo

Follows the other logs such as:

304 GET /api/note-map/H2a0lW0UIT4c/backlink-count with 11 bytes took 1ms