If you experience issues related to the activitypub integration in v4.0.0-beta.1 or newer specifically, please let me know here so it can be triaged.
I suspect it's a misconfiguration on my part rather than a bug, but webfinger isn't working on my new install of v4.0.0-beta2.
I'm getting a 400 error – see https://browser.pub/@caesar@forum.rewild.pt. However I can open the webfinger document manually in the browser without issues, so I'm guessing it's a CORS issue – but I'm not sure what I should change in the NodeBB settings to make it work.
I don't see any mention in the docs of anything I need to do specifically to make webfinger work – any suggestions?
@caesar said:
However I can open the webfinger document manually in the browser without issues
Actually, I cannot open that URL at the moment. I also get a 400 Bad Request
@julian said in v4.0.0-beta.1 bugs & issues thread:
Actually, I cannot open that URL at the moment. I also get a
400 Bad Request
Hmm, that's odd. I've tried from a private window and it still works for me. It's conceivable I was restarting nginx after trying a different configuration when you tried it, could you try again?
Check that
urlinconfig.jsonisforum.rewild.pt. If it does not match, the webfinger controller will throw a 400.
It's https://forum.rewild.pt. Should that work?
I tried changing it to the bare domain without the https://, but I got an infinite redirect loop.
Yes, still a Bad Request from my end. Could it be you've set up an entry in your /etc/hosts so that forum.rewild.pt points directly to the IP?
Sorry about the config.json bit, you're right, it should have the https:// prefix.
My mistake, I was logged in as a test user in my private browsing session 
It's working only when logged in, otherwise it's giving the 400 error. Any clue why that would be?
(No, nothing in /etc/hosts.)
Could it be a Cloudflare proxy issue?
I also just tried from the server:
curl 'http://127.0.0.1:4567/.well-known/webfinger?resource=acct%3Acaesar%40forum.rewild.pt'
And it still gives me Bad Request. But then, maybe that's because of what you said about the domain not matching…
Ok, found the problem. It only works with the privilege guests / View Users enabled. I had fediverse / View Users enabled anyway but that wasn't enough.
I'm not sure if that's intended? I guess it makes sense in principle…