question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

{"success":false}

See original GitHub issue

Hi! Whenever I try to submit something with Staticman, it fails with just {"success":false}.

staticman.yml: https://github.com/StratofortressDNS/Domain-Requests/blob/master/staticman.yml

Form (site’s on custom DNS): https://github.com/StratofortressDNS/tools/blob/master/register.html#L23

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:25 (10 by maintainers)

github_iconTop GitHub Comments

2reactions
deadlydogcommented, Aug 10, 2019

I recently had this problem, and it was due to ReCaptcha. It turned out that I encrypted my ReCaptcha secret with the public staticman instance, so then obviously my private instance didn’t know how to decrypt the value.

The real issue here though is that more details about the error don’t get returned back through the web response, so I think that error handling code needs to be updated a bit. For me, getSiteConfig() in this line was failing and throwing an exception, which was getting caught and sent to the sendResponse function in this line. The issue is that the sendResponse only attaches error details if it’s a known error, due to the logic of the if statement in this line. So it seems the solution is we want to attach the error details back in the response, even when it’s an unknown type of error.

I’m going to take a crack at a PR to fix this, but my javascript skills are 10+ years rusty, so we’ll see how it goes. If I’m unable to get to it, at least I’ve posted the details of what changes are needed for someone else to do it 😃

2reactions
pedroprietocommented, Oct 27, 2017

Hi guys,

I was trying to use staticman and came across the same problem. I copied the sample config file from the repo and got the same error, {"success":false}.

After changing everything once and again, I finally noticed that my staticman.yml file was not well formatted: the last line, email: md5, was not correctly indented (it appeared at the beginning of the line). That happened when I copied and pasted the code directly from the normal GitHub file view; when I switched to the raw view of the file in GitHub, the copy & paste worked like a charm (the last line was correctly indented).

I hope it helps!!

Read more comments on GitHub >

github_iconTop Results From Across the Web

false,”data”:{“message”:”Wrong Request.”,”errorCode”:23}
I've investigated this issue, and, this error code comes only when there is no JWT in request,cookie,session or header. Please go to plugin...
Read more >
API Requests and Responses
The json response includes: The first element of any API response will be the "Success" element, which will either be true or false....
Read more >
Is It True Success or False Success?
False success is different. Under its influence you can think you are winning when in fact you are losing. By the time you...
Read more >
Test works but "success: false"
Anyone have an idea why a test Zap would be successful but a) it doesn't actually work, and b) it says “success: false”?...
Read more >
Code: 200 OK {"success":false,"message":"Permission ...
{"success":false,"message":"Permission denied!","total":0,"data":[],"object":[]} 2- Menu items in topnav do not display for non-super user ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found