Problem with EPAG domain registrar plug-in

Discussion in 'Troubleshooting' started by Netzhaus, Sep 26, 2014.

  1. Netzhaus

    Netzhaus Kilo Poster

    Messages:
    46
    We setup the EPAG plug-in, but for every domain requested by a customer in the shop it shows, that the domain is not available. Even if it is definetly not and whois output shows, that it is free.
    Playing around with the WHOIS available and not available patterns did not change anything.
    (And no problem here with other plug-ins.)

    The debug log showed up messages like shown below.
    It seems that the plug-in is talking to the EPAG API and is getting an answer which it is handling as an error.
    The Answer from EPAG API is not logged.

    A search for that error brought up an KB article
    http://kb.odin.com/en/117564
    It says that this is an authentication issue.
    So we checked the credentials with test script from the same host and were able to communicate with the EPAG API. We also asked the EPAG support if they could see any authentication failures, but they told us that there were only successfull logins.

    Are there any other reasons, which may lead to this problem?
    Maybe a parse problem of EPAG APIs answer?

    Example logentry:
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] sent to EPAG __start_message
    action: login
    username: ourusername
    password:*****
    __stop_message

    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] recieved from EPAG
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] sent to EPAG __start_message
    ## VERSION 6.4 DOMAIN -- DO NOT REMOVE OR CHANGE !!!!
    0a . Requested Action : DOMAINCHECK
    1a . Domainname ..... : keinemeindeineunsere.com
    __stop_message

    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] recieved from EPAG
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] sent to EPAG __start_message
    action: logout
    __stop_message

    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_send_request
    ] recieved from EPAG
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::plugin::DM::EPAG::_parse_respon
    se] EPAG command: DOMAINCHECK
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::DM::pluginEngine::check_registe
    r] New_DM_Plugin_Engine->check_register() result=$VAR1 = {
    'keinemeindeineunsere.com' => 2
    };
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::DM::RegEngine::bulk_lookup_for_plugin] New_DM_Plugin_Engine->lookup_method() lookup_result=$VAR1 = {
    'keinemeindeineunsere.com' => 2
    };

    [2014/09/26 10:15:12] [WARN] [46736] [HSPC::MT::DM::RegEngine::bulk_lookup_for_plugin] Registrar reported about error during lookup for domain keinemeindeineunsere.com
    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::DM::RegEngine::bulk_lookup_for_plugin] New_DM_Plugin_Engine->bulk_lookup_domains() whois_domains=$VAR1 = [];

    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::DM::RegEngine::bulk_lookup_for_plugin] New_DM_Plugin_Engine->bulk_lookup_domains() whois_results=$VAR1 = [];

    [2014/09/26 10:15:12] [DEBUG] [46736] [HSPC::MT::DM::RegEngine::bulk_lookup_for_plugin] New_DM_Plugin_Engine->result result=$VAR1 = [
    {
    'is_error' => 1,
    'domain' => 'keinemeindeineunsere.com',
    'text' => 'Error occurred during domain lookup.'
    }
    ];
     
  2. Vadim Ivanov

    Vadim Ivanov Kilo Poster

    Messages:
    36
    Dear Netzhaus,

    Anyway plugin writes to logfile an EPAG response to login request. The empty string of response means that plugin did not replied to login.

    If plugin is configured using the client-side SSL certificate you have to submit to EPAG the company name for which the certificate has been issued.

    You can test manually the ssl-connection:
    #openssl s_client -connect [..hostname..]:[..port..] -cert /usr/share/ssl/certs/mycert.pem -CApath /usr/share/ssl/CA

    Please edit [..hostname..], [..port..] as well as –cert and –CApath to reflect your situation.

    P.S.: Also you have to inform EPAG about your email address for status callbacks.
     
  3. Netzhaus

    Netzhaus Kilo Poster

    Messages:
    46
    Dear Vadim,

    thank you for your reply.
    We could solve the problem now and it had to to do with the SSL-certificate.

    We only provided our certificate to the plugin, but it was necessary to feed it with the whole chain (certicicate, intermediate certificate, root CA).
     

Share This Page