This guide is for instance admins who may be having trouble with Enafore compatibility.
By default, Mastodon allows cross-origin access to the /api endpoint. Thus Enafore should "just work" for most Mastodon servers.
If the nginx/Apache settings have been changed, though, then Enafore might not be able to connect to an instance. To check if the instance is supported, run this command (replacing myinstance.com with your instance URL):
curl -sLv -H 'Origin: https://enafore.social' -o /dev/null \
myinstance.com/api/v1/instanceIf you see this in the output:
Access-Control-Allow-Origin: *
Then Enafore should work as expected!
Otherwise, if the instance admin would like to whitelist only certain websites (including Enafore) to work with CORS, then they will need to make sure that the server echoes:
Access-Control-Allow-Origin: https://enafore.social
when Enafore tries to access it. Note that this is a bit complicated to configure (compared to the simpler * approach), but there are instructions on StackOverflow for nginx, Apache, and other servers.