-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orders required but not set when getting orders #87
Comments
Thank you for the report! 😄 The problem here is that the In issue #74 there was a discussion about that problem and a possible workaround. I'm closing this bug because of that. If you have further questions, please use issue #74, so the discussion is kept in one place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I try to get orders from a logged in account, it throws the following error:
org.shredzone.acme4j.exception.AcmeProtocolException: orders: required, but not set
org.shredzone.acme4j.toolbox.JSON$Value.required(JSON.java:501), org.shredzone.acme4j.toolbox.JSON$Value.asURL(JSON.java:445), org.shredzone.acme4j.Account.getOrders(Account.java:131)
This is from an account logged into Let's Encrypt staging. I can create a new order and utilize that normally, but getting orders from the account throws an error.
The text was updated successfully, but these errors were encountered: