Closed NikoGrano closed 3 years ago
With 3dc5dbc I'm getting
-----CONNECT-----2020-06-03 12:57:49-----
Connection made
-----END-----2020-06-03 12:57:49-----
-----WRITE-----2020-06-03 12:57:52-----
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<login>
<clID>XXXXXXXXXXXXXXXX</clID>
<pw>XXXXXXXXXXXXXXXX</pw>
<options>
<version>1.0</version>
<lang>en</lang>
</options>
</login>
<clTRID>5ed782304feca</clTRID>
</command>
</epp>
-----END-----2020-06-03 12:57:52-----
-----READ-----2020-06-03 12:57:54-----
<?xml version="1.0" encoding="utf-8"?>
<epp xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:obj="urn:ietf:params:xml:ns:obj-1.0" xmlns="urn:ietf:params:xml:ns:epp-1.0">
<response>
<result code="2400">
<msg>Command failed</msg>
</result>
<trID>
<clTRID>5ed782xxxxa</clTRID>
<svTRID>t7bxxxxz</svTRID>
</trID>
</response>
</epp>
-----END-----2020-06-03 12:57:54-----
-----DISCONNECT-----2020-06-03 12:57:54-----
Disconnected
-----END-----2020-06-03 12:57:54-----
However, its non related as with latest version there is more issues with it...
@metaregistrar
This adds unwated data to the request, how can we not add this line? Ficora is anyways also renamed to Traficom, meaning all links to ficora.fi is invalid.
However, stuff still stays stuck... Old commit works now after #269 changes. But now with current head.
With current head it just gets stuck and timeouts.
I have merged your pull request. The extension 'ficora' was made because ficora does not really adhere to the EPP standards. At least that was the case when it was still called ficora. If things are better now, please feel free to add the correct extension names to the Extensions directory, and we can depreciate the ficora extension.
Thanks, however still I am unable to resolve issues with current master head...
Im stuck in fixing DNSSEC issues in 3dc5dbc4798bd1d99d76bb8ca95b656377e15c60. I'll try fix as much as I can do of those and then I'll update to latest master and try fix the issues there... Seems pretty weird EPP getting stuck with latest master.
What Major changes were made to connection logic between these versions? @metaregistrar
Closed as inactive. Using old version of client and it works.
@NikoGrano did you handle to get thr things works on the last version ? I'm facing to the same issue
After 5 minutes it just timeouts. Nothing happens. I do not how I can debug this.
Even more weird, version 3dc5dbc4798bd1d99d76bb8ca95b656377e15c60 works, but that just gives error 2400 as the request is invalid due it doesnt follow https://registry.domain.fi/s/docs/EPP_interface.pdf.