For the most part, our tests with FRED 2026.1 has been successful as follows:
-
We use a copy of a development DB and modify it so the log tables in the DB FRED are eliminated
-
We configured the fred-app services properly
-
We have successfuly generated DNS tables (and signed them, BTW)
-
FERDA, whois, web whois and RDAP work as expected
-
Messenger, secretary and fileman are properly configured.
There is one curious problem with eppic (and it happens with our homemade EPP client, too).
eppic works mostly well, but there is one command that does not:
root@fred26-app:~# eppic
2026-09-03 09:59:15,956 WARNING transport:connect:105 Verification of the peer certificate is disabled.
NIC-REG1@192.168.81.203 > info-contact --id=CN_1
2026-09-03 09:59:18,244 WARNING epp:send_request:163 Communication with the server failed. Retrying...
2026-09-03 09:59:18,245 WARNING epp:logout:71 Logout failed.
2026-09-03 09:59:18,287 WARNING transport:connect:105 Verification of the peer certificate is disabled.
2026-09-03 09:59:18,530 ERROR epp:send_request:166 Communication with the server failed. Logging out and closing connection...
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/eppic/epp.py", line 159, in send_request
return self._send_request(request, cltrid)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/eppic/epp.py", line 175, in _send_request
response = self._client.send(request, tr_id=cltrid)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/epplib/client.py", line 109, in send
response = cast(ResponseT, self._receive(request.response_class))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/epplib/client.py", line 121, in _receive
response_raw = self.transport.receive()
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/epplib/transport.py", line 158, in receive
raise TransportError('Empty response recieved.')
epplib.exceptions.TransportError: Empty response recieved.
2026-09-03 09:59:18,531 WARNING epp:logout:71 Logout failed.
2026-09-03 09:59:18,531 ERROR app:run:184 Communication with the server failed.
If only happens with this particular operation. The other info operations and the rest of commands, including creation of a contact, work perfect.
And it seems that it happens on the backend, because the corresponding XML generated from our page, which is a homemade XML, equivalent to info-contact, fails too.
As I said, info-nsset, etc. work well, too.
What do you think?
BTW, we have copied our dev DB and modified it (exporting or eliminating the log tables, now in the fredlog DB). And that's it.
Best regards.
Mario Guerra - NIC-CR