Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
So I was able to add the backblaze backend as an alias site to minio client and then list my buckets content. Even when it was restricted to that particular bucket it behaved as expected. But if I set up the replication via the GUI in minio, it suddenly logs out that the remote bucket is offline. Both URL and access parameters are the same between CLI and GUI
Try to ping the endpoint URL from your instance where minio is residing, seems to me like a network connectivity issue. Check the ports and configuration of the replication.
Just in case we misunderstood each other. I have executed the minio client inside my minio container deployment. So the network connectivity is exactly the same given that they are inside the same container.
In that case I don't know, try some forums, check the minio logs, ask ChatGPT, etc.