custom v1 -> v2 client upgrade - le stage not reaching out via http to verify?
hi,

i have a custom v1 client that i wrote over 2 years ago, it’s currently

handling the provisioning and renewal of over 500 certs without any issues.

i recently received a notification email from le - indicating i should upgrade it to use v2.

so thanks for the heads up and that’s what i’m atte…
you should extract from the reply json object the “url”, and send a post with “{}” payload to trigger the identifier challenge verification. check rfc8555.
first of all, you need to check if you are using a self-signed certificate.

if so, you have to accept it first: double-clicked on the request in the network pane, and ow prompted you whether you wanted to accept the certificate.

other option will be to use the [overwolf.web.sendhttprequest()](http://developers.overwolf.com/documentation/sdk/overwolf/web/#sendhttprequest) funct… well, i raised an issue with id support whom escalated it with engineering or something and it's now working. they did say they'd text me updates and haven't received anything from them so whether they did anything or whether it just started working.. who knows. 

but yeah, looks like the answer is calling / talking to support. we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: you could use on-demand tls with local certs if you don’t know ahead of time which ip the request will come from:

tls internal {

on\_demand

}

[image]

[tls (caddyfile directive) - caddy documentation](https://caddyserver.com/docs/caddyfile/directives/tls)

caddy is a powerful, enterprise-ready, open source web server with automatic https writ… <http://www.wikitree.com/contact/cert/> 


<http://www.wikitree.com/g2g/210706/how-to-become-pre-1500-certified?show=210706#q210706> i seem to have fixed this by myself. i disabled probe on my .vcl and this seemed to fix the 503 issues. here is my .vcl for varnish incase anyone needs it(this might work for you)! :slight\_smile:

vcl 4.0;

backend default {

.host = "127.0.0.1";

.port = "81";

.connect\_timeout = 5s;

.… all the info you need can be found in http://community.spiceworks.com/topic/291089-6-2-beta-release-candidate-ii-build-now-available-6-2-00797

 we strongly caution you against using the beta in production. if you hit a serious bug you may have to start from scratch! it is possible that responsiveness may suffer and customers needs may not be met within business timescalesleading the way in it testing and certification tools wwwtestkingcom well, there is no sla as such. if you want faster response, you should upgrade to premium processing. 
you can go for stamping anytime, there is no rule as such. there are two things visa stamping and petition approval. once your petition is close to expiration, they can file extension. 
no need to… You were unfortunately fooled by the marketing. The actual updated Lightroom is called Lightroom Classic. It is exactly like you remember with a develop panel, ability to print, etc and will behave and work like the Lightroom you are used to. What you likely installed is a port of the mobile operating system version of Lightroom to desktop operating systems. Adobe calls this Lightroom Desktop which is extremely confusing. What you want to do is to call adobe and transfer your subscription to Lig...