> For the complete documentation index, see [llms.txt](https://nobraintools.gitbook.io/maya-groomers-tool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nobraintools.gitbook.io/maya-groomers-tool/getting-started/problem-errors/url-error-linux.md).

# URL Error (Linux)

## Case 1 - URL Error: unknown url type: https

When validating Groomer’s Tool license inside Maya on **Rocky/Alma/RHEL Linux,** the Script Editor shows:

```
URL Error: unknown url type: https
# Warning: Failed to Verify The License. Please check your key and email.
```

This happens because **Maya’s bundled Python** is linked against **OpenSSL 1.1**, but Rocky/Alma Linux 9 only ships **OpenSSL 3** by default. Without the compatibility library, Maya cannot use HTTPS (so Gumroad/Render checks fail).

***

### Solution

Enable CRB repo and install compatibility SSL + CA certs:

```bash
sudo dnf config-manager --set-enabled crb
sudo dnf install -y compat-openssl11 ca-certificates
```

* **compat-openssl11 -** provides OpenSSL 1.1 runtime so Maya’s Python can talk HTTPS.
* **ca-certificates** - provides updated root certificates for secure HTTPS connections.

After this, restart Maya and license validation should work normally.

## Case 2 - urlopen error \[SSL: CERTIFICATE\_VERIFY\_FAILED] certificate verify failed: certificate has expired (\_ssl.c:1006)

### Problem

Usually it means Python’s TLS check found an expired certificate in the HTTPS certificate chain.

Most common causes:

1. The website/server certificate actually expired.
2. A corporate proxy, antivirus, or firewall is intercepting HTTPS and presenting its own expired certificate.
3. The machine’s date/time is wrong, making a valid cert appear expired.
4. Python’s CA bundle is stale, especially with certifi, embedded Python, old Maya Python, or bundled tools.

### Solution

* Check system date is not tampered
* Update OS root certificates and TLS stack (e.g., OpenSSL; for Python, update certifi).
* This often happens when our platform providers are undergoing maintenance. In most cases, waiting about an hour or two resolves the issue automatically. If not, please contanct <info@nobraintools.com>