# Rancher host proxy always has "starting" status **URL:** \ **Category:** Rancher 1.x\ **Created:** [July 15, 2015, 12:59am UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80 "2015-07-15T00:59:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dsapala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dsapala/32/35_2.png) [@dsapala](https://forums.suse.com/u/dsapala)\ **Post date:** [July 15, 2015, 12:59am UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/1 "2015-07-15T00:59:31Z")
The rancher host proxy always show a status of “starting” in the containers tab of the ui. screenshot: [https://db.tt/OKfx0mMB](https://db.tt/OKfx0mMB) As a side note, how can I get the ability to upload a screenshot? It denied me. ---
**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\ **Post date:** [July 15, 2015, 6:06am UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/2 "2015-07-15T06:06:31Z")
Not sure why it’s not starting, but you shouldn’t need the `host-proxy` container as of the last release a couple weeks ago. There is a newer [websocket-proxy](https://github.com/rancher/websocket-proxy) which runs inside `rancher/server` and multiplexes over an extra connection opened from each host to it to handle any requests for host-specific things (stats, logs, shell). It’s automatically configured this way with no complicated setup as was needed for `rancher/host-proxy`. This also means that `9345/tcp` and `9346/tcp` no longer need to be exposed from hosts to the internet, just `500/udp` and `4500/udp` for IPSec between the hosts. What the forum considers “new users” can’t upload attachments… You should be able to upload images now. ---
**Author:** ![dsapala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dsapala/32/35_2.png) [@dsapala](https://forums.suse.com/u/dsapala)\ **Post date:** [July 15, 2015, 2:40pm UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/3 "2015-07-15T14:40:05Z")
If I restart the rancher agent on the slave without the host-proxy running and the CATTLE\_HOST\_API\_PROXY env var not set I no longer get stats in rancher server. I’m using rancher/agent:v0.7.9. How can I verify what you’re expecting? ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [July 15, 2015, 9:22pm UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/4 "2015-07-15T21:22:25Z")
Can you let us know what version of Rancher server you are using by clicking on the cow in the upper left corner? ---
**Author:** ![dsapala](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dsapala/32/35_2.png) [@dsapala](https://forums.suse.com/u/dsapala)\ **Post date:** [July 16, 2015, 3:18pm UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/5 "2015-07-16T15:18:08Z")
Rancher v0.25.0 Cattle v0.58.0 User Interface v0.29.0 Rancher Compose latest ---
**Author:** ![cjellick](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cjellick/32/2876_2.png) [@cjellick](https://forums.suse.com/u/cjellick)\ **Post date:** [July 16, 2015, 7:19pm UTC](https://forums.suse.com/t/rancher-host-proxy-always-has-starting-status/80/6 "2015-07-16T19:19:17Z")
@dsapala it seems like maybe the websocket-proxy is not running in your setup. When you restart the rancher agent, do you see anything in the logs that looks similar to this: ``` time="2015-07-16T18:53:00Z" level="info" msg="Host not registered yet. Sleeping 1 second and trying again." Attempt=1 reportedUuid="" time="2015-07-16T18:53:01Z" level="info" msg="Connecting to proxy." url="ws://10.0.2.2:8080/v1/connectbackend?token= time="2015-07-16T19:17:21Z" level="fatal" msg="Failed to connect to proxy." ```