Connection to Mastodon users on one specific instance fails - action: likely fixed, please retest #40

morph commented 2025年09月25日 11:30:16 +02:00

So far I noticed no problems regarding to connections. Any contact from Hubzilla, Friendica, Pixelfed and various Mastodon instances was able to be added.
But follow requests for accounts on mastoart[.]social will return an error.
Remote channel or protocol unavailable.
I tried from my Hubzilla. From there indeed I can add people from this instance.

Log of a failed API request:

2025年09月24日T17:01:14Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array
(
[req] => /api/v1/instance
)

2025年09月24日T17:01:52Z:LOG_INFO:f0b9b7b993:Activity.php:276:fetch: fetch failed: https[:]//mastoart[.]social/users/username
2025年09月24日T17:01:53Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array

So far I noticed no problems regarding to connections. Any contact from Hubzilla, Friendica, Pixelfed and _various_ Mastodon instances was able to be added. But follow requests for accounts on mastoart[.]social will return an error. `Remote channel or protocol unavailable.` I tried from my Hubzilla. From there indeed I can add people from this instance. Log of a failed API request: > > 2025年09月24日T17:01:14Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array > ( > [req] => /api/v1/instance > ) > > 2025年09月24日T17:01:52Z:LOG_INFO:f0b9b7b993:Activity.php:276:fetch: fetch failed: https[:]//mastoart[.]social/users/username > 2025年09月24日T17:01:53Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array

abanink commented 2025年09月25日 12:04:03 +02:00

For the mastoart user in the log you provide, that seems to point to the same username on mastodon.social (use "Open original page").
[edit] DELETED

There is no webfinger response to the mastoart user.
[edit] DELETED

While it's ok for the user on mastodon.social:
[edit] DELETED

So I'd think this is a broken case which cannot be supported.

Do you have an example of a user of mastoart that you could add from Hubzilla but not from forte, so the issue would be reproducible?

For the mastoart user in the log you provide, that seems to point to the same username on mastodon.social (use "Open original page"). [edit] DELETED There is no webfinger response to the mastoart user. [edit] DELETED While it's ok for the user on mastodon.social: [edit] DELETED So I'd think this is a broken case which cannot be supported. Do you have an example of a user of mastoart that you could add from Hubzilla but not from forte, so the issue would be reproducible?

morph commented 2025年09月25日 19:54:26 +02:00

😬 Oh noo ... that's not a real user URI. I didn't want to publish someone's credentials, so I replaced the real username. I've requested an account on the instance for checking it out. The account has to be confirmed by a moderator though.
[edit] The account on mastodon.social is totally unrelated. Would you mind deleting the link to it, please?

[edit] ...

Same result as for the others when I try my test account.

2025年09月25日T17:58:27Z:LOG_INFO:f0b9b7b993:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph
2025年09月25日T17:58:27Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array
(
[req] => /api/v1/instance
)

I tried to follow my Forte account from there. No notice will come in. Ping per @-mention also fails.

2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph
2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph
2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:network.php:124:http_status: inbox:403 Permission denied
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:46:post: inbox_args: Array
(
[0] => inbox
)

2025年09月25日T18:09:17Z:LOG_INFO:baee998274:HTTPSig.php:328:verify: Content_Valid: true
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:items.php:2528:tag_deliver: checking tags
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Activity.php:4572:store: Item exists and no update required.
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Activity.php:4572:store: Item exists and no update required.
2025年09月25日T18:09:17Z:LOG_INFO:baee998274:network.php:124:http_status: inbox:200 OK
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:46:post: inbox_args: Array
(
[0] => inbox
)

2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:HTTPSig.php:328:verify: Content_Valid: true
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required.
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required.
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required.
2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:network.php:124:http_status: inbox:200 OK

I got no idea what's going on. As said, had no issues so far with connections other Mastodon instances or other software.
So I managed to create a mutual connection from Hubzilla to the mastoart morph. The handshake lasted unusully long as well as the delivery of mentions in both directions.

😬 Oh noo ... that's not a real user URI. I didn't want to publish someone's credentials, so I replaced the real username. I've requested an account on the instance for checking it out. The account has to be confirmed by a moderator though. [edit] The account on mastodon.social is totally unrelated. Would you mind deleting the link to it, please? [edit] ... Same result as for the others when I try my test account. > 2025年09月25日T17:58:27Z:LOG_INFO:f0b9b7b993:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph 2025年09月25日T17:58:27Z:LOG_INFO:f0b9b7b993:api.php:142:api_call: API call not implemented: api/v1/instance - Array ( [req] => /api/v1/instance ) I tried to follow my Forte account from there. No notice will come in. Ping per @-mention also fails. > 2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph 2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:Activity.php:276:fetch: fetch failed: https://mastoart.social/users/morph 2025年09月25日T18:09:14Z:LOG_INFO:5bd78a17ac:network.php:124:http_status: inbox:403 Permission denied 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:46:post: inbox_args: Array ( [0] => inbox ) 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:HTTPSig.php:328:verify: Content_Valid: true 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:items.php:2528:tag_deliver: checking tags 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Activity.php:4572:store: Item exists and no update required. 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:Activity.php:4572:store: Item exists and no update required. 2025年09月25日T18:09:17Z:LOG_INFO:baee998274:network.php:124:http_status: inbox:200 OK 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:46:post: inbox_args: Array ( [0] => inbox ) 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:HTTPSig.php:328:verify: Content_Valid: true 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Inbox.php:360:post: delivery_channel: morph 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required. 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required. 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:Activity.php:4572:store: Item exists and no update required. 2025年09月25日T18:09:19Z:LOG_INFO:738f19962c:network.php:124:http_status: inbox:200 OK I got no idea what's going on. As said, had no issues so far with connections other Mastodon instances or other software. So I managed to create a mutual connection from Hubzilla to the mastoart morph. The handshake lasted unusully long as well as the delivery of mentions in both directions.

abanink commented 2025年09月27日 11:36:20 +02:00

@morph I had no issues adding a connection to your account on mastoart on my forte instance.

I'm running forte version 25.9.13.

image

@morph I had no issues adding a connection to your account on mastoart on my forte instance. I'm running forte version 25.9.13. 

morph commented 2025年09月27日 13:15:34 +02:00

@abanink I'm puzzled. Even there is no preview while typing the handle like for others.

@abanink I'm puzzled. Even there is no preview while typing the handle like for others.

fortified commented 2025年10月01日 02:49:05 +02:00

The lack of preview probably means there is not yet a locally cached actor record (aka 'xchan'). A signature or basic communications issue is most likely at fault; as the software otherwise goes out of its way to discover and cache new actor records. The string 'verified' can be used to find signature validation issues in log files.

Ensure that the RFC9421 signature feature toggle is not enabled (at this time) on the admin/security page. That is intended for future use. Also ensure that mandatory checking signatures on actor records is disabled -- on the same page; and that your forte version is up to date. Some related issues were fixed just a few weeks ago.

At the endpoint /dev/ap_probe on your site, one can test communication by pasting the mastoart url and turning on the signature toggle to use the credentials of the logged in channel. /dev/finger can be used to inspect webfinger issues.

An infrequent but notable cause of such issues which has been seen on a few occasions is a site that was marked dead (site_dead = 1 in the site table) after prolonged signature failures; which may require setting manually by changing the value to 0 in the database.

The lack of preview probably means there is not yet a locally cached actor record (aka 'xchan'). A signature or basic communications issue is most likely at fault; as the software otherwise goes out of its way to discover and cache new actor records. The string 'verified' can be used to find signature validation issues in log files. Ensure that the RFC9421 signature feature toggle is not enabled (at this time) on the admin/security page. That is intended for future use. Also ensure that mandatory checking signatures on actor records is disabled -- on the same page; and that your forte version is up to date. Some related issues were fixed just a few weeks ago. At the endpoint /dev/ap_probe on your site, one can test communication by pasting the mastoart url and turning on the signature toggle to use the credentials of the logged in channel. /dev/finger can be used to inspect webfinger issues. An infrequent but notable cause of such issues which has been seen on a few occasions is a site that was marked dead (site_dead = 1 in the site table) after prolonged signature failures; which may require setting manually by changing the value to 0 in the database.

abanink commented 2025年10月12日 14:10:04 +02:00

@morph have you tried the /dev/ap_probe and /dev/finger endpoints on your forte site, pasting the mastoart url?
The resulting output might give a nice hint about the issue.

Also, as Mike suggested, check for dead sites in your database.

I've created this MR which works for my installation, which runs nginx & php-fpm, and I saw that yunohost is doing this as well, so that might solve the issue.

@morph have you tried the /dev/ap_probe and /dev/finger endpoints on your forte site, pasting the mastoart url? The resulting output might give a nice hint about the issue. Also, as Mike suggested, check for dead sites in your database. I've created this [MR](https://codeberg.org/fortified/forte/pulls/42) which works for my installation, which runs nginx & php-fpm, and I saw that yunohost is doing this as well, so that _might_ solve the issue.

fortified commented 2026年05月05日 22:29:04 +02:00

This may be an artifact of issue #61, which had similar symptoms and was fixed recently.

This may be an artifact of issue #61, which had similar symptoms and was fixed recently.