I was trying to do essentially the same thing (docker 12.0 HTTPS on a custom port), but on Raspberry Pi OS. I couldn’t forward port 443 on my router at all - instead, I forwarded the external port 4430 to raspberrypi:443. I managed to get the web version running on HTTPS, but only the thumbnails and metadata worked - I couldn’t download existing files or upload new ones. Devtools revealed that the client is trying to get the files without using the provided port (image), which obviously fails - is that the “malformed file transfer urls” bug you mentioned, mqmoore?
The above was the result I got after I added :4430 in seahub_settings.py (FILE_SERVER_ROOT and SERVICE_URL). I left the hostname in .env unchanged though. Because, for some reason, adding the port to the SEAFILE_SERVER_HOSTNAME results in it not being accesible at all. It just throws a PR_CONNECT_RESET_ERROR in the web browser, not providing any more info, and the seafile and seafile-caddy docker logs don’t show any errors as well (and this happens during a connection through a VPN or a different network - so it’s not because of LAN)
Do you know if this can be somehow fixed? It’s already driving me crazy, so if it’s going to require modifying the client’s code, then it would already be easier to switch to a different software. Thanks in advance for any help