-
Notifications
You must be signed in to change notification settings - Fork 27
ValueError: No JSON object could be decoded #6
Comments
Is there any more context in the log? This isn't enough for me to even guess at what's happening. |
I have the same problem, and no more logs in the stack ;/ @brndnmtthws did you manage to resolve it? |
I haven't seen the problem myself, but I'll see what I can do. |
@brndnmtthws in my case that was being hooked to the wrong marathon api endpoint. I had it pointed to marathon-user API end point, so python could not find the app id. |
false hopes.. still erroring in the same manner... and no certs... just app not crashing now.. :P |
This is my test if that helps:
|
The line of code that's failing is presumably here: https://github.com/mesosphere/letsencrypt-dcos/blob/master/run.sh#L8 Can you try running that line of code with your arguments set? |
OK, I am pretty sure I know what the problem is... I have forked the repo and did some debugging... and managed to replicate this locally... The error is shown when the response returns as non json (obvious from the error message too).. tried locally with auth token and return was my domain name!
So solution would be to provide a token within curl request. I think! |
echo output dsfasfd dsfasfd dsfasfd dsfasfd dsfasfddsf Added marathon API access token key support d2iq-archive#6 d2iq-archive#10 added support for missing endpoints typo
Ah, you're using auth. I didn't bother to add auth support to this. |
I made a PR ;) would be good to consider this for merge so i am not using my forked version but default to main lib ;) |
When launching the container, it fails with:
The text was updated successfully, but these errors were encountered: