JWPlayer cannot connect to server after there's roughly 20 users online
I am using Wowza on Amazon EC2. Streaming works great using JWPlayer as my web client, Wowza as my server and our hosts are using Wirecast. Today, after we had around 20-25 users connect, new users would get the Error loading stream message from JWPlayer. There aren't any firewall limitations on the wowza server. It's not in a load balanced environment and RTMP is completely unfiltered. My JWPlayer is a Pro license and my Wowza license is the one that's bundled with Amazon EC2. Is there a connection limitation somewhere that I'm overlooking that's on by default? The existing 20 users who were connected and did not have issues didn't experience latency or anything odd like that. CPU on the server was essentially 80% idle and there was plenty of resources on the instance to spread the wealth around. I didn't enable any additional modules to limit the number of users who can connect.
Perhaps someone here with more experience can point me in the right direction of where to further debug. I've checked wowza error logs - nothing. I've checked access logs and there's nothing obvious there that looks incorrect. Any steps to further debug would be fantastic - I'll post anything asked of me.
From your description, it sounds like you may have launched a Lickey Wowza instance but not provided your own Wowza License.
Wowza has 2 instance types on EC2.
DevPay which uses a built in license which is billed as part of the EC2 hourly rate. You cannot use premium addons with DevPay.
Lickey which uses your own Wowza license and is billed at the normal EC2 rate. The Wowza License is billed separately from Wowza. You can use the premium addons with this instance type.
The Lickey instances have a developer license installed so that the server will configure and start up correctly. This license is limited to 10 concurrent connections. You need to replace this license with your own and restart Wowza.