marlinhares
September 16, 2025, 7:50pm
1
hi, new to discourse.
I need to clone an environment.
What I did:
rsync -a from dirs discourse_docker and discourse_volumes
moved the dirs to a new server
changed discourse_docker/containers/app.yml (the domain name)
generated new certs to new domain, moved cert and key to discourse_volumes/shared/standalone/ssl
ran ./launcher rebuild app on new server
Works great, everything appears normal. When I repply a topic works. But when I create a “New Topic" it sends me to the login page.
What am I doing wrong? Any hint?
pfaffman
September 16, 2025, 9:24pm
2
Does that happen in safe mode ?
Ethsim2
September 17, 2025, 9:43am
3
i think you need to do a another task to map the topics from the old domain name to the new domain name
Remapping domain names in posts
All the existing posts will still refer to the old domain.
You’ll need to change old domain references in your posts to the new domain:
BEFORE
AFTER
./launcher enter app
then
discourse remap talk.foo.com talk.bar.com
Alternatively, use Rake if discourse binary is unavailable, you can use the rake version:
bundle exec rake posts:remap["talk.foo.com", "talk.bar.com"]
Finalize with:
rake posts:rebake
This ensures that the domain name remaps in existing posts, and content is regenerated as necessary.
2 Likes
marlinhares
September 17, 2025, 1:42pm
4
Many thanks for this info.
In safe mode it worked ok.
Exited safe mode and as long as I disabled each plugin I retested the functionality.
One plugin was causing the trouble.
But fortunately when I reenabled it the functionality worked ok. I did not know what happened. Maybe a remap on backstage when I disabled and reenabled it.
Problem solved
marlinhares
September 17, 2025, 1:45pm
5
Very precious advice @Ethsim2
As stated in my earlier post, the problem was solved, disabling and reenabling the offending plugin.
But as a novice in discourse I will definitely do your advice on this new environment.
2 Likes