Is there a way of testing it's up short of adding the url to a client?
Discussion
visit the url in a browser using http://
I cannot on that port. If I use no port or 80 it hits the Umbrel ok, but when I add the relay port number it does not. Don't know where else it would map or otherwise tell me it's up.
http://haven.my-tail.ts.net:3355 ? (Replace "haven.my-tail" with your actual "host.tailsacle-domain")
Yes that's what I did.
This is in the env (with my actual URL)
RELAY_PORT 3355
RELAY_URL umbrel.XXXXX.ts.net/
This is in the logs:
2025/04/12 17:09:09 Failed to read file: read relays_import.json: is a directory
Haven isnt starting up because youre missing the files in the directory. The docker compose file maps the "current directory", and im not sure what that means to portainer. Try changing the paths, left side of the colon only. Right side should not be changed
volumes:
- ./data/blossom:/haven/blossom
- ./data/db:/haven/db
- ./relays_blastr.json:/haven/relays_blastr.json
- ./relays_import.json:/haven/relays_import.json
- ./data/tor:/var/lib/tor
I changed the paths. When I start the logs say:
Failed to read file: read relays_import.json: is a directory
And when I look at the file structure via terminal, relays_import.json does list as a directory. Shouldn't it be a file?
Ok I removed those directories and copied the files there and now it's working. I connect and it shows the relay page: "MyName outbox relay". Are there settings or other options to access?
All settings are in the .env
Ok cool, wasn't sure if there was any settings or other info displayed in the GUI
Woot! You might be the first person other than me that's using this image. I'll reconsider platform specific packages now with a little time off from work.
Yeah pretty cool, wasn't sure if I'd get it going. I know Umbrel has on Nostr relay in their store. I'm not sure how many people would use a Haven package in Umbrel. So now that I have it running, and added to a client, is there anything I can do or see regarding what it's doing?
Check the logs
Ok. Is there any documentation on using the Blossom function, like just add the address:port as http in a client for content? How do you view the content uploaded? I realize I'm asking a lot of questions and I do appreciate your time so thanks for that.
For blossom: https://bouquet.slidestr.net/browse
Thanks nostr:npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxc
Ok so this is like a front end I add my server to?
#yestr
Yes, it’s a frontend to manage all your content on your blossom servers.
I don’t think it’ll work for me, since I use Tailscale I need to connect directly from my devices to my server (it’s not exposed publicly).
You should be able to connect from your browser to a local blossom server - but some functionality will not work (e.g. image thumbnails).
When I tried adding my server it wouldn’t connect. I added https://mytailscaleaddress:3355.
In a web browser this gives me the outbox page. Some clients connect to the relay ok (ws://…) but not sending notes. Maybe I have something misconfigured.
do you have local ssl certificates set up. I suppose you may need to use http://mytailscaleaddress:3355
Another question if you don’t mind. I’m now able to get some clients to connect to my Haven instance. When I post a note, the Portainer logs show that Haven fails to connect to three relays listed in the import file. I removed them from the import file, and restarted the stack/container, but it still tries to connect to them. How do I update things so it stops attempting to connect to those relays?
Its probably failing in the blastr list
Ah ok, I didn’t check that. Seems obvious now that you mention it 😆
I removed the three relays from the blastr file, did "Update the stack" and restarted the container, but Haven is still attempting to connect to two of the deleted relays:
2025/04/18 00:15:42 error connecting to relay
2025/04/18 00:15:57 error connecting to relay
2025/04/18 00:16:02 🔫 blasted bde3d2e8817ab4894212b48c3196ca73adc22ec126f75d8ed5267ac4b7c4dc8a to 26 relays
Nm didn’t actually delete the first time. All good.