Hi Chaps, hoping to find a resolution here. I also found a bit of a big in the Amazon Cloudstack script, I think.
But first, here's my problem: I've followed the step by step instruction to setup Wowza on EC2, as per the very helpful Amazon Developer guide. Problem is, now that I have this up and running, when I try to login I get this error:
Wowza Streaming Engine Manager could not connect to the Wowza Steaming Engine (
http://localhost:8087). Verify that the Wowza Streaming Engine service has started and is running.
So to confirm, I can get to the login page, and have the correct username and password as per the output from when the AIM package was setup. Perhaps the error is around the "localhost" setting? Maybe that should be pointing to my actual server instead?
So here's the BUG I found! Clearly, the older version of your product required port 8086 to be used to connect to the Streamengine. In version 4 though, it's 8088. Trouble is, as part of the AIM setup, it only opens up port ranges 8084-8086! Whoops... once you edit this to go up to 8088, viola! You can connect.
May need to let them know, being a "free" user, AMZ don't value my opinion enough to give me access to support / forums...
Anyway, help much appreciated please. I'm very green at this stuff.
EDIT1: managed to putty into the install, noticed that both the services were stopped. Ran the /.startup.sh script, "seeems" like it is running, however still won't allow me to login. Reviewing the execution, this is at the top of the script:
I have the same issue and am unable to login to the Streaming Engine Manager. I have ensured that port 8088 is added to the security group rules and that the service is running. Have also restarted the service but to no avail.