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
4. You can now use the EppClient class and its functions in your code. You can refer to the **examples** directory for examples of how the package can be used.
34
+
### 3. Configure Access to the Registry
36
35
37
-
5. To test if you have access to the EPP server from your system, you may use:
36
+
Edit the `examples/Connection.php` file to configure your registry access credentials.
37
+
If the registry requires SSL certificates and you don't have them, refer to the troubleshooting section for steps to generate `cert.pem` and `key.pem`.
Replace `epp.example.com` with your EPP server's hostname and adjust the paths to your certificate files (`cacert.pem`, `cert.pem`, and `key.pem`) as needed. These tests can help identify issues with SSL/TLS configurations or network connectivity.
163
+
164
+
## Generating an SSL Certificate and Key
165
+
166
+
If you do not have an SSL certificate and private key for secure communication with the registry, you can generate one using OpenSSL.
**Note:** For production environments, it's recommended to use a certificate signed by a trusted Certificate Authority (CA) instead of a self-signed certificate.
174
+
175
+
## EPP-over-HTTPS Issues
176
+
177
+
If you experience login or other issues with EPP-over-HTTPS registries such as `.eu`, `.fi`, `.hr`, `.it`, or `.lv`, it might be caused by a corrupted or outdated cookie file. Follow these steps to fix it:
178
+
179
+
```bash
180
+
rm -f /tmp/eppcookie.txt
181
+
```
182
+
183
+
After deleting the cookie file, try logging in again. This will force the creation of a new cookie file and may resolve the issue.
184
+
185
+
## Need More Help?
186
+
187
+
If the steps above don’t resolve your issue, refer to the EPP Client logs (`/path/to/tembo/log`) to identify the specific problem.
0 commit comments