# Can't stream - Connection refused by server

**URL:** https://community.wowza.com/t/cant-stream-connection-refused-by-server/35259
**Category:** Wowza Developer Dojo
**Tags:** wowza-streaming-server-java-api
**Created:** [August 20, 2010, 1:50pm UTC](https://community.wowza.com/t/cant-stream-connection-refused-by-server/35259 "2010-08-20T13:50:48Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Cesar\_Aracena](https://avatars.discourse-cdn.com/v4/letter/c/ecc23a/32.png) [@Cesar\_Aracena](https://community.wowza.com/u/Cesar_Aracena)
#### Post date: [August 20, 2010, 1:50pm UTC](https://community.wowza.com/t/cant-stream-connection-refused-by-server/35259/1 "2010-08-20T13:50:48Z")

</div>

Hi guys,

I wanna kill myself. My WMS on EC2 was working perfectly yesterday (using secure upstream and playback) and I turned it off to save money (I’m just deploying for now) and today I can’t stream. It says that the connection was refused by the server from both Wirecast and the Live client in the examples.

I restarted the server in standalone mode and here’s the output when I try to stream (I’ve changed my IP address becouse it’s a static one):

```auto
INFO server comment - ModuleMediaWriterFileMover.onAppStart: live/_definst_
INFO server comment - SecureTokenTarget: create:true play:false publish:false
INFO server comment - ModuleRTMPAuthenticate.onAppStart: SecureToken is on
INFO server comment - ModuleRTMPAuthenticate.onAppStart: Authorization password file: /usr/local/WowzaMediaServer/conf/publish.password
INFO application app-start _definst_ live/_definst_
INFO session connect-pending my.ip.address.here -
INFO session comment 107355500 ModuleSecureToken.onConnect: rejectConnection: clientId:107355500
INFO session connect my.ip.address.here -
INFO session disconnect 107355500 -
INFO session connect-pending my.ip.address.here -
INFO session comment 1184126606 ModuleSecureToken.onConnect: rejectConnection: clientId:1184126606
INFO session connect my.ip.address.here -
INFO session disconnect 1184126606 -
INFO session connect-pending my.ip.address.here -
INFO session comment 650229549 ModuleSecureToken.onConnect: rejectConnection: clientId:650229549
INFO session connect my.ip.address.here -
INFO session disconnect 650229549 -
INFO session connect-pending my.ip.address.here -
INFO session comment 1851976026 ModuleSecureToken.onConnect: rejectConnection: clientId:1851976026
INFO session connect my.ip.address.here -
INFO session disconnect 1851976026 -
INFO session connect-pending my.ip.address.here -
INFO session comment 1005427956 ModuleSecureToken.onConnect: rejectConnection: clientId:1005427956
INFO session connect my.ip.address.here -
INFO session disconnect 1005427956 -
INFO session connect-pending my.ip.address.here -
INFO session comment 1203976969 ModuleSecureToken.onConnect: rejectConnection: clientId:1203976969
INFO session connect my.ip.address.here -
INFO session disconnect 1203976969 -

```

Anyone has a clue on what’s going on? I’m using a startup zip file with my last (correct) settings so I know I start the AMI with the last good changes in it (but I might have missed something of course).

I’ll have some ppl coming over in a couple of hours for a test stream and I would love to make the test -.-

Thanks!!!

---

<div class="post-metadata">

### Author: ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)
#### Post date: [August 21, 2010, 12:34am UTC](https://community.wowza.com/t/cant-stream-connection-refused-by-server/35259/2 "2010-08-21T00:34:13Z")

</div>

If you terminate an EC2 instance you can’t turn it back on. You can start a new instance and use a startup package, and if you have the same elasticIP to assign to, it is possible to terminate an instance then quickly start a new one that is a functional clone. But that is something you had better test and perfect.

Richard
