AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Trying to download an archive takes you to http://seaweedfs:8333/

(#585) Bug Needs triage self-hosting
by RexSystem edited originally by @snow99as on GitHub

Summary

When I go to download an archive of a Guild I expect it to give me the download but upon clicking the download it redirects you to a invalid domain

Steps to reproduce

Install fluxer server Trigger a Guild archive Go to Download Guild archive. It does not work and doesn't redirect you so copying the link from the download button will cause the redirect

Environment

There's no obvious self hosting version number Version 149.0.7827.103 (Official Build) (64-bit) Ubuntu 26.04 LTS

7 comments

Sign in with Fluxer to comment and vote.
Comment by @creeperita09
RexSystem 1 vote originally by @creeperita09 on GitHub
Happens on my instance too, it's trying to redirect to the internal seaweedfs container url
Permalink
Comment by @snow99as
RexSystem 1 vote originally by @snow99as on GitHub OP
I set up S3 buckets externally and can confirm nothing is even uploaded when you trigger guild archive
Permalink
Comment by @D1reW0lf
RexSystem 1 vote originally by @D1reW0lf on GitHub
Yup, same here. From user backups to anything that can be downloaded on the admin area.
Permalink
Comment by @ztx-lyghters
RexSystem 1 vote originally by @ztx-lyghters on GitHub
Same issue, server was deployed according to the currently available self-host guide, archive download links lead to http://seaweedfs:8333, which is an internal docker container hostname
Permalink
Comment by @D1reW0lf
RexSystem 1 vote originally by @D1reW0lf on GitHub
Just in case anyone has this problem, using an external S3 storage makes the links work, since it starts pointing to the external service URL.
Permalink
Comment by @ztx-lyghters
RexSystem 1 vote originally by @ztx-lyghters on GitHub
Just in case anyone has this problem, using an external S3 storage makes the links work, since it starts pointing to the external service URL.
But it also should not require having an external S3 storage. I personally don't have one and will never have one.
Permalink
Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub
Indeed, I'm getting this fixed on the next update where I've reworked a few things to simplify the self-hosted setup. SeaweedFS is no longer necessary but it can use the regular filesystem with a custom system to power pre-signed URLs and the such on top of it.
Permalink
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.