Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certificate Issue. Warning: Potential Security Risk Ahead #7

Open
faxotherapy opened this issue Dec 25, 2021 · 0 comments
Open

Certificate Issue. Warning: Potential Security Risk Ahead #7

faxotherapy opened this issue Dec 25, 2021 · 0 comments
Assignees

Comments

@faxotherapy
Copy link

faxotherapy commented Dec 25, 2021

Hi,

Trying to update my Mattermost instance.

I had no SSL issue using prior version of Mattermost/Traefik, i.e. stack version 3.7

In version 3.8, does the new configuration include accessing the service using HTTPS by default, because in the end, we often want to access the service from the Internet and not necessary locally.

Since update, after following the “Get started”, I've got the following message from Firefox and everything is broken and can no longer access Mattermost on my VPS:

Warning: Potential Security Risk Ahead
[domain] uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT

I did not have any certificate issue before when using an older version of the stacks. I used “traefik-ssl.yml”, version 3.7.

Obviously, the content between “traefik-ssl.yml”, version 3.7 and “traefik.yml” version 3.8 dramatically changed. In version 3.8 of “traefik.yml” I see the use of letsencrypt. So, don't understand why Firefox still showing “self-signed” certificate.

Also, when forcing the visit, I now have the message:

404 page not found

This is what happened when going from stack version 3.7 to stack version 3.8. I reverted back to stack version 3.7, and I can now access Mattermost.

Even though after issuing the command:

DOMAIN=[MY_DOMAIN] docker stack deploy -c mattermost.yml mattermost

I also put the SCHEME=https argument like I used in the previous version, but not working either.


Thanks for your help.

@johackim johackim self-assigned this Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants