【BUGS!!!】Unable to upload/download files via Web/Mobile after configuring a custom port in v12

Okay, here is a polite, professional, and accurate English translation of your forum post:

Subject: BUG!: Unable to upload/download files via Web/Mobile after configuring a custom port in v12

Hello everyone,

I’m excited to see Seafile enter its 12th version!

Unfortunately, I’ve encountered an issue when using the new Caddy reverse proxy with a custom port. While I can successfully access and log in to Seafile from any platform using the format 【https://xxx.sample.com:<custom_port>】, I’m facing problems with file downloads.

When I attempt to download a file, the generated share link 【https://xxx.sample.com/seafhttp/repos/xxxxxxx?op=download】. As you can see, this link does not automatically include the custom port number. If I manually change the link to 【https://xxx.sample.com:<custom_port>/seafhttp/repos/xxxxxxx?op=download】, the download works perfectly.

It seems that the synchronization via the mapped drive/desktop client worksFine.

Furthermore, in version 12, the options for SERVICE_URL and FILE_SERVER_ROOT appear to be missing from the system settings, which has thwarted my attempts to manually add the port number through those settings. Modifying SERVICE_URL and FILE_SERVER_ROOT directly in the seahub_settings.py file also does not seem to take effect.

I’m nearing my wit’s end trying to resolve this. I suspect it might be a small oversight and hope it can be addressed soon, or perhaps there’s an immediate workaround available.

Thank you to the forum members and the great developers for your work.

Hi!
I understand that you’ve installed SF 12 via Docker, is that correct?
I’ve never install SF on Docker, but the documentation of SF 11 says that you can set the SERVICE_URL as a Docker env variable.
https://manual.seafile.com/11.0/docker/deploy_seafile_with_docker/#deploy-seafile-docker-with-custom-port
Might be worth giving a try