Hi there, I am self running Mattermost server and just got this connection issues “Error: net:ERR CERT DATE INVALID”. I have OMNIBUS version on Ubuntu server installed some 3 month ago and it is probably LetsEncrypt SSL certificate expiration issue as I use it. Can anyone guide how to best fix it step by step? Being a Linux beginner don’t want to mess things up. Thanks!

Hi noidsr,

No worries at all! It indeed sounds like it might be an issue with your SSL certificate not being renewed properly. But don’t worry, I’m here to assist you on how to fix it.

Here’s a step-by-step guide to help you out:

  1. Log in to your Ubuntu server via SSH using the command: ssh username@yourserverip

  2. Check the status of your GitLab and Mattermost services using:

sudo gitlab-ctl status sudo gitlab-ctl status mattermost

  1. Since you’re using OMNIBUS, the openssl and acme (Let’s Encrypt) client is included in the package. You can renew your certificate using:

sudo gitlab-ctl renew-le-certs

  1. Once done, check your certificate’s status using:

sudo gitlab-ctl check-config

  1. If everything checks out without errors, restart Mattermost with:

sudo gitlab-ctl restart mattermost

Please remember to replace “username” and “yourserverip” with your actual username and server IP respectively in the first step.

I hope these steps will be helpful for you. However, if you encounter any issues along the way, feel free to post back here in more detail and I’d be glad to assist further.

~Mattermost AI Assistant :robot:

[Disclaimer: This was an AI assisted response powered by Mattermost AI. Were any of the above suggestions inaccurate? Let us know by replying to this comment!]

Hi there!

sudo gitlab-ctl status sudo gitlab-ctl status mattermost

sudo: gitlab-ctl: command not found

sudo gitlab-ctl renew-le-certs

sudo: gitlab-ctl: command not found


You need to install gitlab: Download and install GitLab | GitLab

1 Like


Thanks for helping on troubleshooting. However after installing Gitlab I ran into other problems:

biovisata:~# gitlab-ctl renew-le-certs
/opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/util.rb:50:in parse_json_file': **Attributes not found in /opt/gitlab/embedded/nodes/, has reconfigure been run yet? (****GitlabCtl::Errors::NodeError****)** from /opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/util.rb:65:in get_node_attributes’
from /opt/gitlab/embedded/service/omnibus-ctl/letsencrypt.rb:21:in block in load_file' from /opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:204:in block in add_command_under_category’
from /opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:746:in run' from /opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/omnibus-ctl-0.6.0/bin/omnibus-ctl:31:in <top (required)>’
from /opt/gitlab/embedded/bin/omnibus-ctl:25:in load' from /opt/gitlab/embedded/bin/omnibus-ctl:25:in

Gitlab installation also must have some problems (IP and web is masked):

[2023-10-18T18:38:52+03:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/cinc-stacktrace.out
[2023-10-18T18:38:52+03:00] FATAL: ---------------------------------------------------------------------------------------
[2023-10-18T18:38:52+03:00] FATAL: PLEASE PROVIDE THE CONTENTS OF THE stacktrace.out FILE (above) IF YOU FILE A BUG REPORT
[2023-10-18T18:38:52+03:00] FATAL: ---------------------------------------------------------------------------------------
[2023-10-18T18:38:52+03:00] FATAL: RuntimeError: letsencrypt_certificate[] (letsencrypt::http_authorization line 6) had an error: RuntimeError: acme_certificate[staging] (letsencrypt::http_authorization line 43) had an error: RuntimeError: ruby_block[create certificate for] (letsencrypt::http_authorization line 110) had an error: RuntimeError: [] Validation failed, unable to request certificate, Errors: [{url:, status: invalid, error: {“type”=>“urn:ietf:params:acme:error:unauthorized”, “detail”=>” Invalid response from "<!doctype html><html lang=\"en\"><meta charset=\"utf-8\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1,max"", “status”=>403}} ]
dpkg: error processing package gitlab-ee (–configure):
installed gitlab-ee package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hello again noidsr,

It looks like there could be a few potential issues here.

Firstly, the error you’re getting after “gitlab-ctl renew-le-certs” (i.e., Attributes not found in /opt/gitlab/embedded/nodes/, has reconfigure been run yet?) suggests that the GitLab Omnibus configuration has not been run yet.

You can run the GitLab configuration with this command:

sudo gitlab-ctl reconfigure

If you have already run this command and still see the error, I suggest taking a backup of the current GitLab files, especially the .json mentioned in the error, and then reinstalling GitLab Omnibus.

Regarding the second error log: it appears your certificate challenge failed. The HTTP-01 challenge is performed by the Let’s Encrypt client making a HTTP request on port 80 to your domain. The error being thrown (Invalid response from .well-known/acme-challenge) means the Let’s Encrypt server was expected to find a file in the .well-known/acme-challenge directory via HTTP, but it either did not find it or was not accessible.

Please ensure your domain is pointed to the correct server IP and that your server is accepting requests on port 80. Also, check that your server is allowing the Let’s Encrypt servers to complete the HTTP-01 challenge.

Finally, the dpkg error suggests there was an error while installing the GitLab package or perhaps a problem with the package itself. You could attempt to fix this with the following commands:


1 2 3 4 5

sudo apt-get update sudo apt-get clean sudo apt-get autoremove sudo dpkg --configure -a sudo apt-get install -f

After running those, try to reinstall GitLab using the command you used before.

Please try these steps and let me know the results. I’m here to help you resolve the issue!

~Mattermost AI Assistant :robot:

[Disclaimer: This was an AI assisted response powered by Mattermost AI. Were any of the above suggestions inaccurate? Let us know by replying to this comment!]