Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mastodon users can not follow my Friendica account #3822

Closed
schiessle opened this issue Oct 23, 2017 · 13 comments
Closed

Mastodon users can not follow my Friendica account #3822

schiessle opened this issue Oct 23, 2017 · 13 comments
Milestone

Comments

@schiessle
Copy link

schiessle commented Oct 23, 2017

I run Friendica, the latest version from master. People told me that they can't follow me from mastodon so I tested it by myself. I set the log level to "debug" in my Friendica instance and tried to connect with my mastodon.social account. This is shown in the log file:

2017-10-23T20:54:02Z@sgmlvksda4eofb5tusvoqsk6eb	[DEBUG]:Probe.php:103:hostMeta	Probing for bjoern@mastodon.social
2017-10-23T20:54:02Z@sgmlvksda4eofb5tusvoqsk6eb	[DEBUG]:Probe.php:157:hostMeta	Probing successful for bjoern@mastodon.social
2017-10-23T20:54:02Z@sgmlvksda4eofb5tusvoqsk6eb	[DEBUG]:dfrn_request.php:474:dfrn_request_post	dfrn_request: url: https://mastodon.social/authorize_follow?acct={uri},network=stat
2017-10-23T20:54:02Z@hpjbg4rcsdölkölf43fdjhfkjsf6v89	[TRACE]:session.php:39:ref_session_read	no data for session hpjbg4rcsdölkölf43fdjhfkjsf6v89

on Mastodon I got this error: " Unfortunately, there was an error looking up the remote account "

Any idea what's wrong here?

@schiessle schiessle changed the title Mastodon users can follow my Friendica account Mastodon users can not follow my Friendica account Oct 23, 2017
@schiessle
Copy link
Author

I just found this mastodon/mastodon#789

I will try it tomorrow, if the suggested URL change works it is probably a Mastodon issue.

@annando
Copy link
Collaborator

annando commented Oct 24, 2017

Please list all log entries with "sgmlvksda4eofb5tusvoqsk6eb" in it. This marks a session.

This issue from Mastodon shouldn't matter. This was from April - and snarl is always on master. In the meantime we improved the OStatus connection massively.

@schiessle
Copy link
Author

@annando in debug mode I just have this messages in the log:

2017-10-24T10:00:34Z@qi8varqha4q1d8occvsepmms63	[DEBUG]:Probe.php:103:hostMeta	Probing for bjoern@mastodon.social
2017-10-24T10:00:34Z@qi8varqha4q1d8occvsepmms63	[DEBUG]:Probe.php:157:hostMeta	Probing successful for bjoern@mastodon.social
2017-10-24T10:00:34Z@qi8varqha4q1d8occvsepmms63	[DEBUG]:dfrn_request.php:474:dfrn_request_post	dfrn_request: url: https://mastodon.social/authorize_follow?acct={uri},network=stat
2017-10-24T10:00:34Z@6mmlst3upud89ikgmkl0q5a70c	[TRACE]:session.php:39:ref_session_read	no data for session 6mmlst3upud89ikgmkl0q5a70c

If I set the log level to "all" I see this (though not all seems to be relevant for the subscription process, but maybe you find something useful): https://www.schiessle.org/debug.all.log

@annando
Copy link
Collaborator

annando commented Oct 24, 2017

So there were only three lines with that value? "all" mostly doesn't matter. BTW: You had activated OStatus on your system?

@schiessle
Copy link
Author

schiessle commented Oct 24, 2017

yes, this are the only lines written to the log while I try to connect via mastodon in debug mode. The log set to "all" contain some xml content which was send back and forth, don't know if this is useful: https://wolke.schiessle.org/s/HvfU1E1cSO2mqcL

OStatus support is enabled and I can connect with my GNU Social account just fine.

@annando
Copy link
Collaborator

annando commented Oct 24, 2017

I can follow you from Friendica, GNU Social and Pleroma, but not from Mastodon. So Mastodon does something different. I will try to reproduce it. But possibly you could add a comment as well to the linked Mastodon issue?

@schiessle
Copy link
Author

@annando ok, i will add a comment to the Mastodon issue

@Alkarex
Copy link

Alkarex commented Oct 24, 2017

Related #3566

@annando
Copy link
Collaborator

annando commented Oct 25, 2017

@Alkarex no, it isn't. The reason for issue #3566 is that the salmon doesn't arrive at the target. This here is some problem inside of Mastodon that seems to be caused by some unexpected answer that we are providing.

@annando
Copy link
Collaborator

annando commented Oct 25, 2017

This seems to be a Mastodon bug concerning their used HTTP library: mastodon/mastodon#4254

@MrPetovan MrPetovan added this to the 3.6.1 milestone Mar 12, 2018
@annando
Copy link
Collaborator

annando commented Mar 18, 2018

From my point of view we can close this issue, since this seemed to be a (now solved) Mastodon Bug. All my tests looked really fine.

@AlfredSK
Copy link

Yep. Works. :-)

@MrPetovan MrPetovan modified the milestones: 3.6.1, 3.6 Mar 18, 2018
@annando
Copy link
Collaborator

annando commented Mar 20, 2018

@MrPetovan Is there a reason that we keep this issue open?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants