uninitialized constant Acme::Client::Resources::Directory::InvalidDirectory
jeromegn opened this issue · comments
This happened once. I guess it needs to be a more explicit constant here.
gems/acme-client-2.0.0/lib/acme/client/resources/directory.rb:66:in `rescue in load_directory': uninitialized constant Acme::Client::Resources::Directory::InvalidDirectory (NameError)
from gems/acme-client-2.0.0/lib/acme/client/resources/directory.rb:58:in `load_directory'
from gems/acme-client-2.0.0/lib/acme/client/resources/directory.rb:54:in `directory'
from gems/acme-client-2.0.0/lib/acme/client/resources/directory.rb:25:in `endpoint_for'
from gems/acme-client-2.0.0/lib/acme/client.rb:291:in `endpoint_for'
from gems/acme-client-2.0.0/lib/acme/client.rb:179:in `get_nonce'
from gems/acme-client-2.0.0/lib/acme/client/faraday_middleware.rb:110:in `get_nonce'
from gems/acme-client-2.0.0/lib/acme/client/faraday_middleware.rb:103:in `pop_nonce'
from gems/acme-client-2.0.0/lib/acme/client/faraday_middleware.rb:41:in `jws_header'
from gems/acme-client-2.0.0/lib/acme/client/faraday_middleware.rb:19:in `call'
from gems/faraday-0.12.2/lib/faraday/rack_builder.rb:141:in `build_response'
from gems/faraday-0.12.2/lib/faraday/connection.rb:386:in `run_request'
from gems/faraday-0.12.2/lib/faraday/connection.rb:149:in `get'
from gems/acme-client-2.0.0/lib/acme/client.rb:254:in `get'
from gems/acme-client-2.0.0/lib/acme/client.rb:140:in `authorization'
I have no idea why this happened either, I've been using the correct directory!
Might be that the server returned an invalid response.
Fixing in #144