0Bugs[Self-Hosted] media-proxy intermittently fails S3 reads with "transport chunk exceeded its byte bound" (#872) Bug Needs triage media self-hosting9d agoby RexSystem originally by @FrigidSouls on GitHubThreadView full discussion Comment by @TheyMadeMeChangeMyUsernameRexSystem 1 vote 8d ago originally by @TheyMadeMeChangeMyUsername on GitHub the stock .ENV file absolutely REFUSED to spin up any 'storage containers' or whatever when media was being sent within a chat and just threw an error i ended up switching to mini and seems to work great for me now! seaweedfs: image: chrislusf/seaweedfs:4.47 command: ["mini", "-dir=/data"] volumes: - seaweedfs-data:/data networks: - fluxer mini uses single-node provisioning - the stock .ENV file was looking for other mounts - which didnt exist (debian 13 LXC in proxmox) Permalink
Comment by @TheyMadeMeChangeMyUsernameRexSystem 1 vote 8d ago originally by @TheyMadeMeChangeMyUsername on GitHub the stock .ENV file absolutely REFUSED to spin up any 'storage containers' or whatever when media was being sent within a chat and just threw an error i ended up switching to mini and seems to work great for me now! seaweedfs: image: chrislusf/seaweedfs:4.47 command: ["mini", "-dir=/data"] volumes: - seaweedfs-data:/data networks: - fluxer mini uses single-node provisioning - the stock .ENV file was looking for other mounts - which didnt exist (debian 13 LXC in proxmox) Permalink
Thread
Comment by @TheyMadeMeChangeMyUsername