For Azure, perhaps this helps?
Otherwise, our standard point of reference: https://docs.nodebb.org/en/latest/configuring/proxies.html
Is there a solution for this?
Actually, other people including us are also interested with this kind of configuration... It would be great if there is a neat and reliable solution.
I'm having a really hard time thinking of cases where a redirect isn't the best solution.
The only case I've seen that makes sense is when you want it accessible through TOR and clearnet.
Also, nobody has really detailed what still doesn't work when the socket.io origins are set up correctly.
FYI instructions for setting up origins are here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins
I will offer up one more solution:
Embedding your new url within a lightweight iframe wrapper on your old url.
So far as I know multiple domains works fine so long as the appropriate socket.io origins are configured.
There will always be one canonical URL, however, which is what is defined in config.json
@scottalanmiller mind opening an issue detailing your specific problems?