Blossom fails on Amethyst

[Sakrecoer]

The blossom server works fine on most clients, but Amethyst gives an error.

Steps to reproduce:

• press the add attachement button and pick a medium
• Chose the blossom server provided by your chorus relay/blossom server
• Hit "add to message"
• See the following error message:

While chosing a different public blossom server works fine, I understand this could be an Amethyst issue. Just posting here for reference.

[mikedilger]

This error message doesn't refer to anything I recognize api_url or apiUrl, neither in my code nor in the blossom specs. So I think we should ask Vitor. If it was my server, maybe it gets tripped up on the port 444 part.

[Sakrecoer]

Thanks for the feedback. I'm not sure i understand the reference to port 444, could you elaborate?

I understand the doc isn't really up to speed and i also know the burden of documenting progress, but if you have a moment to help me understand better, i could help unburden you with contribution to the documentation.

[mikedilger]

Sorry, I wasn't sure what server you used. I was thinking of my server at wss://chorus.mikedilger.com:444/

[Sakrecoer]

ah! ok :) I am using my own, which i set behind a proxy: wss://relay.basspistol.org

Still willing to help out with doc, have identified a couple of things i think i can address. Don't have an ETA, but i'm pretty sure you will recieve some gentle PRs soon™ 💜

[mikedilger]

What if you try https://relay.basspistol.org instead of with wss? Blossom doesn't use websockets.

[Sakrecoer]

Thanks @mikedilger ! The relay is indeed on wss:// but in the app, i have used https:// for the blossom server settings.

I will file an issue on amethyst repo as soon as i have a minute, and reference this one. Many thanks for taking the time to look into this!