Email message bug found

[ProductionNoob]

This summary is sent from YunoHost Forum when we haven’t seen you in a while. Change your email settings, or click here to unsubscribe.

This summary is sent from YunoHost Forum when we haven’t seen you in a while. Change your email settings, or click here to unsubscribe.

This summary is sent from YunoHost Forum when we haven’t seen you in a while. Change your email settings, or click here to unsubscribe.

This summary is sent from YunoHost Forum when we haven’t seen you in a while. Change your email settings, or click here to unsubscribe.

This summary is sent from YunoHost Forum when we haven’t seen you in a while. Change your email settings, or click here to unsubscribe.

v

[tituspijean]

Welcome!

@ProductionNoob

Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : No

@ProductionNoob

WHEN you change the port address to anything else other than 8065

We clearly do not have the same definition of “not tweaking” your server.

It fails because port 443 is you used for SSL by NGINX, the web server for your whole server. 8065 is the internal port onto which your Mattermost server is served, and NGINX takes care of proxifying it.

Why did you need to change the port?

[tituspijean]

No worries, you had overall the good reflex asking for help.

@ProductionNoob

I’m a noobie, I don’t understand these systems yet.- So I wanted to ensure that all traffic was encrypted by using 443. I figured it wouldnt hurt if it did not work (I suspected so because it refused to issue me a lets encrypt… It is afterall provided my yunohost).

Requests go that way:

Mattermost          <->  NGINX <-----> You/your visitors
(port 8095 for you,              SSL
internal only)                 port 443

@ProductionNoob

why would mattermost work any ways if I changed to port 443 and why would it break when trying to restore/upgrade it.

Most likely you did not restart the Mattermost service, so your alteration was not taken into account. Backing up, restoring, upgrading scripts would restart the service, then you would discover the issue.