Originally created by @Cyborgscode on GitHub (Mar 22, 2016).
LE JSON objects contain the real error message, which is important to fix the issue.
Unfortunatly the script does only output a generalized error msg.
any time i need to know th e real reason, i have to use "strace -s 1024 -e read -f " to see the json result coming from the LE Server :=)
Request: add an override option for/or output the LE error msg directly
Originally created by @Cyborgscode on GitHub (Mar 22, 2016).
LE JSON objects contain the real error message, which is important to fix the issue.
Unfortunatly the script does only output a generalized error msg.
any time i need to know th e real reason, i have to use "strace -s 1024 -e read -f " to see the json result coming from the LE Server :=)
Request: add an override option for/or output the LE error msg directly
at which point do you get silent errors? on any errors i experience i always got the message printed on screen by my script, it's set up to print the full json on any hard errors
@lukas2511 commented on GitHub (Mar 22, 2016):
at which point do you get silent errors? on any errors i experience i always got the message printed on screen by my script, it's set up to print the full json on any hard errors
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Cyborgscode on GitHub (Mar 22, 2016).
LE JSON objects contain the real error message, which is important to fix the issue.
Unfortunatly the script does only output a generalized error msg.
any time i need to know th e real reason, i have to use "strace -s 1024 -e read -f " to see the json result coming from the LE Server :=)
Request: add an override option for/or output the LE error msg directly
@lukas2511 commented on GitHub (Mar 22, 2016):
at which point do you get silent errors? on any errors i experience i always got the message printed on screen by my script, it's set up to print the full json on any hard errors
@lukas2511 commented on GitHub (Apr 2, 2016):
Closing this as this problem should actually be solved for quite a while now...