Jump to content

Whois for Venezuelan Domains (Not Working)


Recommended Posts

Buenas, tengo instalado la versión 7.6 para efecto de realizar algunas pruebas. Ahora bien, me encuentro con un detalle, en el archivo ubicado /whmcs/resources/domains/dist.whois.json puedo agregar la información para que se puedan hacer busqueda de dominios con extensión .ve, pero al agregar los datos no funciona lo cuales fueron los siguientes:

{
        "extensions": ".ve,.com.ve,.net.ve,.org.ve,.info.ve,.co.ve,.web.ve",
        "uri": "socket://whois.nic.ve",
        "available": "El dominio no se encuentra registrado"
    },
    {
        "extensions": ".ar,.com.ar,.net.ar,.gob.ar,.edu.ar,.musica.ar,.tur.ar,.org.ar,.int.ar,.mil.ar",
        "uri": "socket://whois.nic.ar",
        "available": "El dominio no se encuentra registrado"
        
    }

]

Noten que pude agregar el de Argentina y si funciona perfectamente, ¿Alguien que me pueda ayudar? por favor!.

Screenshot_2019-05-16 Whois - VE.png

Screenshot_2019-05-16 Carro de Pedidos - TecnoProjectLATAM(2).png

Screenshot_2019-05-16 Carro de Pedidos - TecnoProjectLATAM(1).png

Screenshot_2019-05-16 dist whois json - Administrador de archivos cPanel v3.png

 

English transalation

Quote

Good, I have version 7.6 installed for the purpose of performing some tests. Now, I find a detail, in the file located /whmcs/resources/domains/dist.whois.json I can add the information so that you can do search of domains with extension .ve, but when adding the data does not work what which were the following:
Note that I was able to add Argentina's and if it works perfectly, someone who can help me? please!.

 

Edited by WHMCS ChrisD
Added english translation
Link to comment
Share on other sites

Saludos, sigue presentando el mismo error, si chequeo los registros me indica lo siguiente: WHOIS Lookup Error for 'iraismejiavielma.com.ve': Error: 110 - Connection timed out.

He preguntado con otros amigos y me indica que si le funciona pero en versiones inferiores a la que poseo actualmente de WHMCS, ya que el archivo donde se modifica o se agrega la información antes suministrada pero de manera diferente es en whoisservers.php.

Link to comment
Share on other sites

On 16/05/2019 at 16:29, Cesar Wilfredo Sevilla Mej said:

Good, I have version 7.6 installed for the purpose of performing some tests.

that possibly explains why tecnoprojectlatam.com fails the WHMCS license test - but not to worry, I won't bother reporting illicit users to WHMCS Legal Dept any more.... @WHMCS ChrisD can do that if he's inclined... or more likely, he'll just edit the post! 🙂

On 16/05/2019 at 16:29, Cesar Wilfredo Sevilla Mej said:

Now, I find a detail, in the file located /whmcs/resources/domains/dist.whois.json I can add the information so that you can do search of domains with extension .ve, but when adding the data does not work what which were the following:

as per the docs, you should NOT edit dist.whois.json - for some reasons, you have 3 different entries in that file...

[
    {
        "extensions": ".com.ve,.net.ve,.org.ve,.web.ve,.info.ve,.co.ve",
        "uri": "socket://whois.nic.ve",
        "available": "No match for"
    },
    {
        "extensions": ".ve,.com.ve,.net.ve,.org.ve,.info.ve,.co.ve,.web.ve",
        "uri": "socket://whois.nic.ve",
        "available": "El dominio no se encuentra registrado"
    },
    {
        "extensions": ".ve,.com.ve,.net.ve,.org.ve,.info.ve,.co.ve,.web.ve",
        "uri": "socket://whois.nic.ve",
        "available": "No match for"
    }
]

the details that Chris gave you are correct - perhaps you've broken whois lookup limits for the .ve TLD and your server IP has been blocked by the registrar - that could explain the timeout error that you're seeing.

VUSWHXa.png

Link to comment
Share on other sites

Gracias por la acotación pero como dije, estoy haciendo unas pruebas antes de comprar la licencia ya que es primera vez que uso esta plataforma. Pero de ser así, entonces cuando lo mude de servidor y haga la contratación debería solucionarse el problema, caso contrario entonces espero que ustedes me puedan ayudar.

Link to comment
Share on other sites

No hay absolutamente ningún problema con la licencia en lo que a mí respecta. thanks.png

con respecto al problema de los dominios .ve, lo primero que debe hacer es devolver a dist.whois.json a su condición original con una sola entrada para .ve: no creo que esté causando su problema específico (probé su archivo localmente y todavía funciona), pero no va a ayudar a la situación.

RGYRWjS.png
Los detalles que Chris le proporcionó, que están en el archivo dist.whois.json predeterminado de v7.7.1 de todos modos, son correctos, por lo que no debería haber tenido que hacer ningún cambio en el archivo.

Creo que también podría ser un problema con Captcha habilitado; intente deshabilitar Captcha de la configuración del área de administración y vea si eso lo soluciona. Si uso la plantilla "Modern" (que no usa Captcha) en lugar de "Standard Cart" en su sitio, entonces la búsqueda de dominio funciona bien.

ofXtYpF.png

Spoiler

there is absolutely no issue about the license as far as I am concerned. thanks.png

with regards to the problem of .ve domains, the first thing to do is to return dist.whois.json to its original condition with only one entry for .ve - I do not think it's causing your specific issue (I tried your file locally and it still works), but it won't be helping the situation.

the details that Chris gave you, which are in the default dist.whois.json file from v7.7.1 anyway, are correct - so you should not have needed to make any changes to the file.

I think that it could also be an issue with Captcha being enabled - try disabling Captcha from the admin area settings and see if that fixes it - if I use the "Modern" template (which doesn't use Captcha) instead of "Standard Cart" on your site, then the domain search works fine.

Link to comment
Share on other sites

  • 6 months later...

Hola, tengo el mismo problema con el Standard Cart , cuando lo cambio al Modern funciona pero no quisiera tener que cambiar la plantilla.

¿por qué funciona con una plantilla y con la otra no?

¿de qué manera se puede resolver?

este es el contenido de /resources/domains/dist.whois.json:

 

{
        "extensions": ".com.ve,.net.ve,.org.ve,.web.ve,.info.ve,.co.ve",
        "uri": "socket://whois.nic.ve",
        "available": "No match for"
    },

 

Se supone que es el mismo para todas las plantillas,  ¿correcto?

¿Alguna ayuda por favor?

Gracias!

WHMCS versión 7.8.3 con licencia
PHP 7.3.11

 

Link to comment
Share on other sites

13 minutes ago, gfserver999 said:

Se supone que es el mismo para todas las plantillas,  ¿correcto?

el problema es que el servidor whois venezolano no está funcionando actualmente: WHMCS está recibiendo un mensaje de error del servidor whois.

  • standard_cart asumirá que el dominio no está disponible y no le permitirá ordenarlo;
  • Modern asumirá que el dominio está disponible y le permitirá ordenarlo.

para demostrar eso, si trato de ordenar google.com.ve usando Modern, WHMCS me dirá que está disponible (cuando no lo está).
qRENNLU.png
puede intentar ponerse en contacto con la dirección de correo electrónico en la parte inferior del sitio a continuación y preguntarles por qué el whois del puerto 43 no funciona: ¡su español será mejor que el mío!

Link to comment
Share on other sites

Just now, brian! said:

el problema es que el servidor whois venezolano no está funcionando actualmente: WHMCS está recibiendo un mensaje de error del servidor whois.

  • standard_cart asumirá que el dominio no está disponible y no le permitirá ordenarlo;
  • Modern asumirá que el dominio está disponible y le permitirá ordenarlo.

para demostrar eso, si trato de ordenar google.com.ve usando Modern, WHMCS me dirá que está disponible (cuando no lo está).
qRENNLU.png
puede intentar ponerse en contacto con la dirección de correo electrónico en la parte inferior del sitio a continuación y preguntarles por qué el whois del puerto 43 no funciona: ¡su español será mejor que el mío!

Hola Brian, lo haré, muchas gracias por tu respuesta.

Kind Regards

Link to comment
Share on other sites

  • 6 months later...

Hello,

Apparently I am the only one who has solved this problem. (I feel good about it).

After dwelling on this matter for a long time, I found how to fix it. 

just create a file called: 

whois.json

on the following route:

/whmcs/resources/domains/

and paste the following code, save and upload to your server:

[
   {
        "extensions": ".com.ve,.org.ve,.info.ve,.net.ve,.web.ve,.co.ve",
        "uri": "socket://whois.nic.ve:43/whois/domain/",
        "available": "no entries found"
    }
]

* Then go to your whmcs admin> settings> products / services> domain prices

* Add the following extensions: .COM.VE, .ORG.VE, .INFO.VE, .NET.VE, .WEB.VE, .CO.VE (these are the only extensions supported by nic.ve)

* Add a price for each domain, (all)

* In your administrator area go to "utilities> system> system cleaning> Empty template cache (this can cause a lot of headaches if not done).

I leave you a video so you can see that it works perfectly in my company. https://cangurohosting.com

 

I hope you appreciate my effort 🙂
Regards.

 

Link to comment
Share on other sites

On 5/19/2019 at 2:08 PM, Cesar Wilfredo Sevilla Mej said:

Gracias por la acotación pero como dije, estoy haciendo unas pruebas antes de comprar la licencia ya que es primera vez que uso esta plataforma. Pero de ser así, entonces cuando lo mude de servidor y haga la contratación debería solucionarse el problema, caso contrario entonces espero que ustedes me puedan ayudar.

¿Estás robando el software pero deseas ayuda con el mismo sin pagarlo?

Link to comment
Share on other sites

10 hours ago, JesusSuarz said:

Hello,

Apparently I am the only one who has solved this problem. (I feel good about it).

After dwelling on this matter for a long time, I found how to fix it. 

just create a file called: 


whois.json

on the following route:


/whmcs/resources/domains/

and paste the following code, save and upload to your server:


[
   {
        "extensions": ".com.ve,.org.ve,.info.ve,.net.ve,.web.ve,.co.ve",
        "uri": "socket://whois.nic.ve:43/whois/domain/",
        "available": "no entries found"
    }
]

* Then go to your whmcs admin> settings> products / services> domain prices

* Add the following extensions: .COM.VE, .ORG.VE, .INFO.VE, .NET.VE, .WEB.VE, .CO.VE (these are the only extensions supported by nic.ve)

* Add a price for each domain, (all)

* In your administrator area go to "utilities> system> system cleaning> Empty template cache (this can cause a lot of headaches if not done).

I leave you a video so you can see that it works perfectly in my company. https://cangurohosting.com

 

I hope you appreciate my effort 🙂
Regards.

 

Hello my friend, it works!

Thanks very much for your effort and contribution

Regards

 

Link to comment
Share on other sites

5 hours ago, brian! said:

the whois entry will only need to be...


    {
        "extensions": ".ve,.com.ve,.net.ve,.org.ve,.info.ve,.co.ve,.web.ve",
        "uri": "socket://whois.nic.ve",
        "available": "no entries found"
    }

there's no need to enter ports or paths.

Hi.  Sorry but it is in the right way to work with this specific server.  The way you say it doesn't work.  everyone tried that way and it never works that way.  is the correct way to work with this server.   🙂

Link to comment
Share on other sites

16 hours ago, JesusSuarz said:

The way you say it doesn't work

I think below proves differently. 🙂

ckawH7m.pngTWqYnMm.png

16 hours ago, JesusSuarz said:

everyone tried that way and it never works that way.

no - everyone tried the old availability string... those strings often change over time, otherwise WHMCS wouldn't occasionally update the dist.whois.json file with those changes.

Link to comment
Share on other sites

I understand,

However, this problem has been unresolved for many years, even you answered several posts explaining some ways to solve it and nobody could solve it. None of the answers you gave before worked for anyone on the community.

suddenly everything works fine?

However. the idea is always to contribute to the community 🙂

 

Link to comment
Share on other sites

10 hours ago, JesusSuarz said:

However, this problem has been unresolved for many years, even you answered several posts explaining some ways to solve it and nobody could solve it. None of the answers you gave before worked for anyone on the community.

possibly because there were no valid answers at the time - availability strings change, servers go down etc etc... would I spend my time updating 5 year old threads with new availability strings every time one changes ? no.

10 hours ago, JesusSuarz said:

suddenly everything works fine?

because the availability string has changed - that's why I replied to your post, you don't have to change paths, only the string.

Link to comment
Share on other sites

On 7/5/2020 at 10:35 PM, JesusSuarz said:

I understand,

However, this problem has been unresolved for many years, even you answered several posts explaining some ways to solve it and nobody could solve it. None of the answers you gave before worked for anyone on the community.

suddenly everything works fine?

However. the idea is always to contribute to the community 🙂

 

@brian! is correct. The extra port parameter is redundant and not required. It will work fine without it.

Link to comment
Share on other sites

  • 2 years later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated