Hello,
The Mattermost have been having recurring issues. Does someone have an idea for a longer term fix ?
Not at the moment. This is clearly something that the IT team will have to look into, once there is a head of IT to lead the work with this.
The certificate expired. Same issue as three months ago.
You remember how to install it as to not break the android app, right?
I don’t, and I’m a bit reluctant on going through the whole discovery process again.
Do we… want to leave it off and redirect people here?
Had a try yesterday, did not succeed despite reading through the official documentation.
Tried replicating a Mattermost install on a fresh VPS, makes me think the PPEU Mattermost setup is not the cleanest.
I’m not a fan of Mattermost as a tool, but transferring the users / network elsewhere would have to be done smoothly, which means fixing the certificate should be done still, while an off-boarding is schemed.
No, it’s not. We could try backing it up and spinning up a new setup. @Bastian @Mab what do you think?
copying it on a testserver to try and fix it would be a nice little adventure (and that’s how updating is usually tested)
Discourse makes it pretty easy, install and import backup. Mattermost… I have no idea.
No comment … 
I’ve been remembering the time I set up certbot as a user before it was available as a package.
The most it needed was a .conf file?
Then fixed by putting a new job in cron?
There’s a few containers for app and reverse proxy and I’m not actually sure where certbot runs. It can be scripted but it’s not as easy or clean as it could be.
Depends on the validation method that is chosen, if it’s DNS, .well-know or something else.
Then it should run on the machine that is authoritative on that method, and the certificates generated should be put to use on the reverse proxy.
Can we remove all unnecessary SSH key please? Meanwhile…
There are three docker’s containers up: reverse proxy, mattermost app and DB. Previous certificate was installed outside containers.
I can report the iOS app is working.
1 Like
Not for Android: ‘invalid SSL certificate’.
Ruben fixed that.
3 Likes