~tsileo/microblog.pub#51: 
Timeout on webfinger resolution

When attempting to lookup a user to follow, I'm running into an error:

Unexpected error, please check the logs and report an issue if needed.

The logs report that the request failed:

2022-11-07 01:26:55.384 | INFO     | app.webfinger:webfinger:15 | fc90229c7c3cd066 - performing webfinger resolution for @lramalho@toot.thoughtworks.com
2022-11-07 01:27:00.765 | ERROR    | app.webfinger:webfinger:55 | fc90229c7c3cd066 - req failed

Followed by a lot of Python tracebacks of different timeout exceptions, until we get to the (potentially) relevant part:

> File "/app/./app/admin.py", line 94, in get_lookup
    ap_object = await lookup(db_session, query)
                      │      │           └ '@lramalho@toot.thoughtworks.com'
                      │      └ <sqlalchemy.orm.session.AsyncSession object at 0x7fc210c35a20>
                      └ <function lookup at 0x7fc219c8f6d0>

  File "/app/./app/lookup.py", line 18, in lookup
    raise ap.NotAnObjectError(query)
          │  │                └ None
          │  └ <class 'app.activitypub.NotAnObjectError'>
          └ <module 'app.activitypub' from '/app/./app/activitypub.py'>

app.activitypub.NotAnObjectError: None is not an AP activity

curl-ing the request appears to return the expected output without issues. I'm wondering if something may be wrong in my setup and causing timeouts or if this is worth investigating. I can provide more details as requested.

Thanks!

Status
REPORTED
Submitter
Tomás Farías Santana
Assigned to
No-one
Submitted
10 months ago
Updated
10 months ago
Labels
No labels applied.

~tsileo 10 months ago

Hey!

I looks like there's an issue with the toot.thoughtworks.com server, I keep getting error when trying to go to the server with a web browser: "504 Gateway Time-out".

There's nothing that can be done here except trying again later to see if the server is responsive again,

Does that make sense?

Thanks!

Tomás Farías Santana 10 months ago · edit

Thanks for the quick reply!

That would make sense. I'll keep retrying on my end.

This ticket can be used to offer a better error message/error handling just so that users can get this insight when a server is unresponsive (and don't come here to open issues). Closing it would be fine too as ultimately my issue was about the failure :) I'll leave that decision up to you (I'm open to contribute some work if it's appropriate).

Nov 7, 2022, 08:07 by outgoing@sr.ht:

Hey!

I looks like there's an issue with the toot.thoughtworks.com server, I keep getting error when trying to go to the server with a web browser: "504 Gateway Time-out".

There's nothing that can be done here except trying again later to see if the server is responsive again,

Does that make sense?

Thanks!

-- View on the web: https://todo.sr.ht/~tsileo/microblog.pub/51#event-211605

Register here or Log in to comment, or comment via email.