You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Attempting to connect my organization's mattermost instance, at a domain hosted on GoDaddy (certificates appear valid in my browser) like this:
mm = mattermostdriver.Driver({
'url': 'myurl.net/chat',
'token': 'omitted-here'
})
Results in this error:
[SSLError: HTTPSConnectionPool(host='myurl.net', port=443): Max retries exceeded with url: /chat:8065/api/v4/users/me (Caused by SSLError(CertificateError("hostname 'myurl.net' doesn't match either of '*.dynadot.com', 'dynadot.com'")))]()
However if I switch add in the flag 'verify: False`, then it gives me a 200 response, and lets me run queries, acting like everything is working fine, but all it returns i the HTML code for my organizations landing page.
For example I can run me = mm.users.get_user(user_id='me') and it will not give me any errors. But if I call me.text, it just shows the HTML of our main landing page at myurl.net...super weird. Would be nice if this threw an error when I'm not actually connected to mattermost. Also, what do I do to address this certificate error?
Attempting to connect my organization's mattermost instance, at a domain hosted on GoDaddy (certificates appear valid in my browser) like this:
Results in this error:
However if I switch add in the flag 'verify: False`, then it gives me a 200 response, and lets me run queries, acting like everything is working fine, but all it returns i the HTML code for my organizations landing page.
For example I can run
me = mm.users.get_user(user_id='me')and it will not give me any errors. But if I callme.text, it just shows the HTML of our main landing page atmyurl.net...super weird. Would be nice if this threw an error when I'm not actually connected to mattermost. Also, what do I do to address this certificate error?