Skip to content
This repository was archived by the owner on Dec 25, 2025. It is now read-only.

Commit 79b82a4

Browse files
committed
Initial version
1 parent 18f6d2a commit 79b82a4

File tree

5 files changed

+2525
-2
lines changed

5 files changed

+2525
-2
lines changed

README.md

Lines changed: 57 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,57 @@
1-
# whmcs-epp-cocca
2-
CoCCA EPP Registrar Module for WHMCS
1+
# Compatibility
2+
3+
This module is supposed to work with all registries using the CoCCA platform.
4+
5+
# WHMCS Module Installation instructions
6+
7+
1. Download and install [WHMCS](https://whmcs.com/)
8+
9+
2. Place the repository as **cocca** directory in `[WHMCS]/modules/registrars`, place your key.pem and cert.pem files in the same cocca directory.
10+
11+
3. Activate from Configuration -> Apps & Integrations -> (search for cocca) -> Activate
12+
13+
4. Configure from Configuration -> System Settings -> Domain Registrars
14+
15+
5. Add a new TLD using Configuration -> System Settings -> Domain Pricing
16+
17+
6. Create a **whois.json** file in `[WHMCS]/resources/domains` and add the following:
18+
19+
```
20+
[
21+
{
22+
"extensions": ".yourtld",
23+
"uri": "socket://your.whois.url",
24+
"available": "NOT FOUND"
25+
}
26+
]
27+
```
28+
29+
You should be good to go now.
30+
31+
# Troubleshooting
32+
33+
## Fixing "Oops!" Issues in WHMCS
34+
35+
If you experience "Oops!" or blank page errors in WHMCS after activating the CoCCA EPP module, it might be caused by incorrect file permissions or ownership. Follow these steps to fix it:
36+
37+
```bash
38+
chown -R www-data:www-data /var/www/html/whmcs/modules/registrars/cocca
39+
chmod -R 755 /var/www/html/whmcs/modules/registrars/cocca
40+
```
41+
42+
Replace `/var/www/html/whmcs` with the path to your WHMCS installation, if different.
43+
44+
## Generating an SSL Certificate and Key
45+
46+
If you do not have an SSL certificate and private key for secure communication with the registry, you can generate one using OpenSSL.
47+
48+
```bash
49+
openssl genrsa -out key.pem 2048
50+
openssl req -new -x509 -key key.pem -out cert.pem -days 365
51+
```
52+
53+
**Note:** For production environments, it's recommended to use a certificate signed by a trusted Certificate Authority (CA) instead of a self-signed certificate.
54+
55+
## Need More Help?
56+
57+
If the steps above don’t resolve your issue, refer to the WHMCS logs (`/path/to/whmcs/logs`) or enable `Display Errors` in the WHMCS Admin under `Utilities > System > General Settings > Other` to identify the specific problem.

0 commit comments

Comments
 (0)