Unfortunately this is still a problem for us, and we cannot migrate servers, which is rather concerning.
Happy to pay someone to get this solved, but after this issue, and the acknowledgement of it numerous times without a clear solution in the forum, we are seriously considering migrating to a different forum software like Flarum. It might not be as feature filled as Discourse, but it’s LAMP and I (as a non web-dev) can get under it.
When we used the Discourse Docker container, we expected that there would be support. If we’d deployed everything separately and used our own version of Postgres, I could appreciate the response. But to date, all we’ve done is used the environment that you’ve recommended and shipped yourselves, and now we’re quite stuffed in terms of moving to a new server (we have an imminent deadline).
At this point, my best bet is a Docker volume backup and restore, because Discourse’s backups aren’t usable. This is also worrying: we have backups that are being made daily, but can’t actually be restored to a new Discourse environment. I wonder how many others will encounter such an issue in the near future.