Nextcloud Social federation not working; webfinger seems OK

Support
,
1

Since this afternoon I my Nextclouds are webfinger-enabled, and the test at webfinger.net replies with something useful.

Nextclouds still cannot federate the social calls to each other :frowning:

My YunoHost server

Hardware: Other ARM board (orange pi zero)
YunoHost version: 3.5.2
I have access to my server : Through SSH | through the webadmin | serial |
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

If I run https://webfinger.net/lookup/?resource=wbk%40online.osba.nl , there is some readable JRD.
Connecting from one Nextcloud to the other does not work though.

If someone got a hint where to start troubleshooting I would be much obliged :slight_smile: Just a message “I got it working, no idea how” gives some hope that I might solve the problem as well, so please let me know if you do!

2

My nginx access log tells me that access from webfinger.net is http2, while curl from my machine uses http1.1 and receives a http-302 found-message, but no reply after that.

Webfinger.net:

GET https://online.osba.nl/.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl

access.log:

“GET /.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl HTTP/2.0” 302 566 “-” “Go-http-client/2.0”
“GET /nextcloud/public.php?service=webfinger&&resource=acct%3Awbk%40online.osba.nl HTTP/2.0” 200 1330 “https://online.osba.nl/.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl” “Go-http-client/2.0”

curl:

curl -H "Accept: application/ld+json" -X GET https://online.osba.nl/.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl

reply:

   <html>
    <head><title>302 Found</title></head>
    <body bgcolor="white">
    <center><h1>302 Found</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>

access.log:

"GET /.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl HTTP/1.1" 302 154 "-" "curl/7.38.0"

If I add --http2 anywhere in the curl line, it answers:

curl: (1) Unsupported protocol

Curl should have http2 support:

$ curl --help |grep http2
     --http2         Use HTTP 2 (H)

Edit: another machine (with more recent curl) does not throw an error, but also does not follow the redirect:

curl -H “Accept: application/ld+json” -X GET https://online.osba.nl/.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl --http2

Same 302, slightly different access.log entry:

“GET /.well-known/webfinger?resource=acct%3Awbk%40online.osba.nl HTTP/2.0” 302 566 “-” “curl/7.64.0”

3

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.