# Issue in 2.5.0rc1 with digital\_ocean module: "Server was unable to give you a response"

**URL:** <https://forum.ansible.com/t/issue-in-2-5-0rc1-with-digital-ocean-module-server-was-unable-to-give-you-a-response/26907>\
**Category:** Ansible Project\
**Created:** [March 6, 2018, 7:58am UTC](https://forum.ansible.com/t/issue-in-2-5-0rc1-with-digital-ocean-module-server-was-unable-to-give-you-a-response/26907 "2018-03-06T07:58:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Denise\_Draper](https://avatars.discourse-cdn.com/v4/letter/d/90db22/32.png) [@Denise\_Draper](https://forum.ansible.com/u/Denise_Draper)\
**Post date:** [March 6, 2018, 7:58am UTC](https://forum.ansible.com/t/issue-in-2-5-0rc1-with-digital-ocean-module-server-was-unable-to-give-you-a-response/26907/1 "2018-03-06T07:58:47Z")

</div>

Hi —

Previously working command isn’t working as of tonight. I’m pretty sure it did previously work after I upgraded to ansible 2.5.0rc1, but I could be wrong about that. The specific and the response are below. I think the “Server was unable to give you a response” message can occur whenever the payload is malformed; I don’t know if it may also occur for other reasons.

So questions: (a) is this a known issue, and (b) if it is caused by changes in digital ocean API, what is the right way to keep up to date on this?

The command is the following (executed on localhost):

> - name: initialize the master ssh key
> 
> digital\_ocean:
> 
> state: present
> 
> command: ssh
> 
> # key name in digitalocean
> 
> name: BRIDGE
> 
> ssh\_pub\_key: “{{ lookup(‘file’, ‘~/.ssh/id\_rsa.pub’) }}”
> 
> api\_token: “{{do\_token }}”
> 
> register: ssh\_key

The error I get out is: