# Connection failed:Application folder (install-location/applications/live) is missing

**URL:** https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523
**Category:** Wowza Streaming Engine
**Created:** [October 17, 2013, 4:12pm UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523 "2013-10-17T16:12:18Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Lars-Goran\_Borjesson](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Lars-Goran\_Borjesson](https://community.wowza.com/u/Lars-Goran_Borjesson)
#### Post date: [October 17, 2013, 4:12pm UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/1 "2013-10-17T16:12:18Z")

</div>

Yes I can read…but before this new interface to woza we had no problem…of course we have the JW-player running on a web-page in S3 …directed to the servers public IP-adress

When testing we use this instance ID i-75fa113a

Using this security group Wowza Media Server 3-3-6-2-04-AutogenByAWSMP-

the instance created in eu-west-1a

---

<div class="post-metadata">

### Author: ![Tim\_Dougherty](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/tim_dougherty/32/596_2.png) [@Tim\_Dougherty](https://community.wowza.com/u/Tim_Dougherty)
#### Post date: [October 17, 2013, 8:18am UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/2 "2013-10-17T08:18:27Z")

</div>

You may be encountering a recent issue that has developed in EC2.

([From the Pre Built AMI’s launch page](https://www.wowza.com/docs/wowza-streaming-engine-for-amazon-ec2-amis)…)

An update to the EC2 Management Console prevents the Wowza Media Server AMIs from launching properly. The workaround is to specify the default startup package using the **User data** field as part of the AMI launch process. To do this:

In the **Configure Instance Details** step, open the **Advanced Details** section.

In the **User data** field, enter the following user data and then select the **As text** option.

```auto
WZA_startupPackageURL=http://s3.amazonaws.com/wowzamediasystems/com/wowza/startup/default_3.6.0.zip

```

You may replace your startup package (if applicable) using the same approach from your download source.

-Tim

---

<div class="post-metadata">

### Author: ![Lars-Goran\_Borjesson](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Lars-Goran\_Borjesson](https://community.wowza.com/u/Lars-Goran_Borjesson)
#### Post date: [October 17, 2013, 5:26pm UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/3 "2013-10-17T17:26:22Z")

</div>

Yes we alreayd noticed…started a new server using the “One-click” option and the server is functioning as expected.

But now I am trying to check the log for supported connections…but what should I be looking for is reading the System log right now.

instanceid = i-d8709b97

---

<div class="post-metadata">

### Author: ![Lars-Goran\_Borjesson](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Lars-Goran\_Borjesson](https://community.wowza.com/u/Lars-Goran_Borjesson)
#### Post date: [October 17, 2013, 5:43pm UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/4 "2013-10-17T17:43:27Z")

</div>

When using the “Oneclickl” option the allowed connections is only 10 connections allowed

---

<div class="post-metadata">

### Author: ![Lars-Goran\_Borjesson](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Lars-Goran\_Borjesson](https://community.wowza.com/u/Lars-Goran_Borjesson)
#### Post date: [October 17, 2013, 11:12pm UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/5 "2013-10-17T23:12:21Z")

</div>

Okay everything is working ok now.

---

<div class="post-metadata">

### Author: ![Tim\_Dougherty](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/tim_dougherty/32/596_2.png) [@Tim\_Dougherty](https://community.wowza.com/u/Tim_Dougherty)
#### Post date: [October 17, 2013, 9:28am UTC](https://community.wowza.com/t/connection-failed-application-folder-install-location-applications-live-is-missing/33523/6 "2013-10-17T09:28:44Z")

</div>

The 10 connection limit is because you selected a **_lickey_** AMI, which comes pre-configured with a limited license key. The **_lickey_** classification is a bring-your-own-license model. This means you will need to install a paid Wowza license in **[install-dir]/conf/Server.license** and restart Wowza.

We also provide a **_devpay_** license model which does not require a separate Wowza license because the billing is managed by Amazon Web Services. All of the current pre-built AMI’s are located here: [**Wowza Media Server 3.6 for Amazon EC2 AMIs**](https://www.wowza.com/docs/wowza-streaming-engine-for-amazon-ec2-amis). Lickey and devpay AMI options are listed in groups on this page.

-Tim
