i made a mattermost-installation available on another URL, mm.internal.foo.com before and mm.foo.com now. My problem is, that i dont find a place to change the “base url” of the installation, which i need to do, because all invitation emails and notification contain the old, potential invalid url.
I have a related problem: I’m using the Elastic Beanstalk installation for a test drive of mattermost, and the AWS ELB to terminate HTTPS. Now in some places, such as mail authentication, MM generates links with HTTP instead of HTTPS as the protocol, which obviously doesn’t work. This would be easy to fix if I could set the “base url”.
The URL is set by looking at how the users access the site. So if you have users using the old URL they will send invites to the old URL.
Same thing for the HTTP vs HTTPs problem. I would suggest setting up a redirect from HTTP to HTTPs to get the users moved over.
Any update on this request? The web pages of mattermost don’t support “base url”. This makes me not being able to deploy mattermost in a kubernetes environment with ingress controller based on path:
(index):1 GET https://s1s005my.be.srv.acc.sys/static/main.85719f8a07aef45169c3.js
(index):1 Uncaught TypeError: window.setup_root is not a function
at (index):1
(anonymous) @ (index):1