Blossom fails on Amethyst #35

New issue

Open

opened 2025-01-19 23:41:07 +13:00 by Sakrecoer · 6 comments

Sakrecoer commented

2025-01-19 23:41:07 +13:00

(Migrated from github.com)

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.

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: ![Image](https://github.com/user-attachments/assets/0ca309a8-053e-45dd-8ad9-3aaf5994f786) While chosing a different public blossom server works fine, I understand this could be an Amethyst issue. Just posting here for reference.

mikedilger commented

2025-01-20 07:19:19 +13:00

(Migrated from github.com)

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.

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 commented

2025-01-20 10:27:28 +13:00

(Migrated from github.com)

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.

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 commented

2025-01-20 12:56:56 +13:00

(Migrated from github.com)

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

Sakrecoer commented

2025-01-20 21:49:13 +13:00

(Migrated from github.com)

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™ 💜

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 commented

2025-01-22 09:17:40 +13:00

(Migrated from github.com)

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

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

Sakrecoer commented

2025-01-23 01:20:22 +13:00

(Migrated from github.com)

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!

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!