# Rest API Potential Design Flaw

**URL:** <https://community.graylog.org/t/rest-api-potential-design-flaw/2951>\
**Category:** Development\
**Created:** [October 30, 2017, 10:09am UTC](https://community.graylog.org/t/rest-api-potential-design-flaw/2951 "2017-10-30T10:09:45Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![GTownson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gtownson/32/793_2.png) [@GTownson](https://community.graylog.org/u/GTownson)\
**Post date:** [November 6, 2017, 4:13pm UTC](https://community.graylog.org/t/rest-api-potential-design-flaw/2951/3 "2017-11-06T16:13:37Z")

</div>

I resolved the issue in this forum post.

> [@Graylog API Call Timing Out](https://community.graylog.org/t/graylog-api-call-timing-out/2868/):
>
> When I tried to start and input I got an error about the input not being able to start. The popup suggested I check my error logs, here is what I see: 2017-10-23T10:47:51.826+01:00 WARN [ProxiedResource] Unable to call http://VMExternalIP:9000/api/system/metrics/multiple on node \<0e3dcc02-a09a-4a7f-b9eb-13ff286b89f8\> java.net.SocketTimeoutException: connect timed out I have provided what I deem to be the relevant parts of my config. rest\_listen\_uri = http://InternalP:9000/api/ rest\_transpor…

---

_[View the full topic](https://community.graylog.org/t/rest-api-potential-design-flaw/2951)._