[Federation]: Adding a Relay fails (using Aoderelay) #392
Description
Description
Going into the Loops admin panel and adding a relay, the following error is produced :
Failed to add relay: can't access property "status", a is undefined
This happens when adding the relay URL, the same result is produced if suffixing with either /inbox or /actor
After pressing "Cancel" and going back to the Loops relay menu, the relay address can be seen but with a "Pending" status which never changes.
On the relay side: I am using the latest version (v0.3.120) of AodeRelay which is a standard relay implementation available at https://git.asonix.dog/asonix/relay and which works fine with Mastodon and Friendica servers as tested.
I control that relay on address https://relay.gayfr.social and have pre-authorized my Loops domain. I also obtain the same result on another AodeRelay v0.3.114 on a completely different domain.
No logs are produced by the relay, confirming the request to join from Loops is likely never processed.
Looking into the JSON response from https://relay.gayfr.social/actor there is indeed no status key and I suspect this is the root cause: Loops implementation should probably rely on a HTTP return code and not on an inexistent status key?
Steps to reproduce
- Go to the Loops Admin dashboard and section "relay"
- Try to add a relay (e.g. https://relay.gayfr.social ), same result is obtained if suffixing with
/inboxor/actor - Error is produced:
Failed to add relay: can't access property "status", a is undefined - You have to press "Cancel", going back to the "relay" menu lists the added URL but with "Pending" status which never changes.
- On the relay side, Loops server is not added (of course, it was pre-authorized).
Tested with AodeRelay latest version v0.3.120.
Loops version
v1.0.0-beta9
Acknowledgements
Yes