Jump to content
jlr

Waiting for my Validator to be verified

Recommended Posts

2 hours ago, jlr said:

@Mediguy I have the same experience... Do we need bigger publicity to gain any progress? Or what should we do? I am disappointed a little bit. 

Are there others who are in the same boat on this forum?

me too... I have been waiting for awhile. My contract of colocation will be end by this November. I think will not extend it. I spend a lot of money and time to make it work. But, when I have trouble it is hard to get support. So, I think it is no use to continue my colocation. 

I'm sorry but I'm out... No hard feeling..

Share this post


Link to post
Share on other sites
2 hours ago, FreedomGundam said:

me too... I have been waiting for awhile. My contract of colocation will be end by this November. I think will not extend it. I spend a lot of money and time to make it work. But, when I have trouble it is hard to get support. So, I think it is no use to continue my colocation. 

I'm sorry but I'm out... No hard feeling..

I am not planning to give up running validator. But it would be great if domain verification process was more transparent. No wonder why many people spreading FUD info about XRP ledger.

And let me repeat myself this is only the objective domain validation step by step process. It is not about who trust me.

Share this post


Link to post
Share on other sites

Would you be willing to publish the information (except the email address) here as well (please use a code text-block)? Then it would be easier to verify that you created the signature correctly for example.

Share this post


Link to post
Share on other sites
59 minutes ago, Sukrim said:

Would you be willing to publish the information (except the email address) here as well (please use a code text-block)? Then it would be easier to verify that you created the signature correctly for example.

root@jlr:~# docker exec rippledvalidator /opt/ripple/bin/rippled server_info -q | grep pubkey_validator
         "pubkey_validator" : "nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6",
root@jlr:~# 
root@jlr:~# 
root@jlr:~# 
root@jlr:~# echo nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6|openssl dgst -sha256 -hex -sign /keystore/validator.agota11.com-privkey.pem
(stdin)= 5421b0e1d1645115ad7f66b37cca6ebae93683803ffb458d88d2825ed04ceb93b24f476addc5d657be74234efcb3bf86348e7a3212d5524769ff718e81b265f48ed67c85615f81b1b01c9c0f4864b66410317bbaa438bdca660afe64d1d5f90b24853df48e487d48f8403873bafe4f9a80bb6114db78b8ac8ee4891c51dd18d00f4f84a1875118cacbd18347696c6827f3cfec7691ccb02967649361272507ae9ac03140375fdf1591afb260699c7453be59082bbd8f3fe677d442ad32b5d68c3f44ddf8b360df4d88e7d2234db2ead5a9badbd581b18e7c847608035ba8660b91a63b6f42507acc1a6b8cecb21143a21b18d962dcf348c9e21bd90a32b5cf02
root@jlr:~# 
root@jlr:~# 
root@jlr:~# 
root@jlr:~# docker exec rippledvalidator /opt/ripple/bin/validator-keys --keyfile /keystore/validator-keys.json sign validator.agota11.com
D7128828EA47E2BF21853307E8D6603B96E6941DE4106FE303002C9A0A4AF0B2034357F0A86AB8FBC46CA20A9D3D8609872ECEF7D1A4869C24989B763C889E09

Hi @Sukrim,

Thanks for looking into this. Above you can find the information (except my email address) what I sent to Ripple and you can see how I retrieved information.

https://developers.ripple.com/run-rippled-as-a-validator.html#domain-verification

Thanks in advance.

Share this post


Link to post
Share on other sites

What about those domains that use cloudfront/AWS? They don't have access to the SSL private keys to sign their validator public key. Any other methods of verification? Theres no way to contact the administrator of the validator registry, just a Google form.

Edited by karlos

Share this post


Link to post
Share on other sites
4 hours ago, karlos said:

What about those domains that use cloudfront/AWS? They don't have access to the SSL private keys to sign their validator public key. Any other methods of verification? Theres no way to contact the administrator of the validator registry, just a Google form.

In that case you are willingly MITM'ing yourself and not in full control over what gets served on your domain via TLS anyways.

Share this post


Link to post
Share on other sites

If you previously submitted information and your validator isn’t verified, please submit again and drop me an email at nikb@ripple.com to let me know you did, so I can double-check on things!

And a better verification process is coming soon; one that takes Ripple entirely out of the equation, which is great. :Laie_16:

Share this post


Link to post
Share on other sites
2 hours ago, nikb said:

And a better verification process is coming soon; one that takes Ripple entirely out of the equation, which is great. :Laie_16:

Great news! Can you give us an idea when that bottle can be uncorked? This year?

Share this post


Link to post
Share on other sites
9 hours ago, nikb said:

If you previously submitted information and your validator isn’t verified, please submit again and drop me an email at nikb@ripple.com to let me know you did, so I can double-check on things!

And a better verification process is coming soon; one that takes Ripple entirely out of the equation, which is great. :Laie_16:

Just my personal advise, maybe it would be better if there are some support email that can assist the validator server setting. I'm very excited when I first decide to run a validator, but later I'm little bit disappointing because it is hard to find assistance. So right now I'm stopping my service, but, probably if things are getting better, I probably will try again.

cheers:)

Share this post


Link to post
Share on other sites
10 hours ago, nikb said:

If you previously submitted information and your validator isn’t verified, please submit again and drop me an email at nikb@ripple.com to let me know you did, so I can double-check on things!

And a better verification process is coming soon; one that takes Ripple entirely out of the equation, which is great. :Laie_16:

Hi @nikb,

Thanks for looking into this. I have just sent a PM for you (nikb@ripple.com), resubmitted info about my domain info.

I also happy that you are improving verification process. :)

 

Share this post


Link to post
Share on other sites

Special thanks @nikb who pointed out what the problem is with my validator settings.

Ripple couldn't retrieve my SSL certificate because it was not able to connect to https://validator.agota11.com/

So it was a configuration failure because my certificate only could be accessed on 51235 validator's p2p port. 

Now it is working fine. Thanks again.

https://xrpcharts.ripple.com/#/validators/nHUNmdXFFPWGqNoMg4XQ5W4rANtk98oHjCGkkqDWmhw7ZgpXAgP6

 

@Mediguy, @FreedomGundam could you please check the config of your own validators? You might have the same/similar problem with domain validation process.

 

Share this post


Link to post
Share on other sites

×
×
  • Create New...