Results 1 to 3 of 3

Thread: EC2 instance on a different port other than 1935

  1. #1

    Default EC2 instance on a different port other than 1935

    Hi there ... I'm trying to set up a Wowza instance on Amazon using a different port, not 1935
    That works perfectly on my local Wowza (port 8888) but when I configure same thin on EC2, it doesn't work (I do have the port 8888 enabled on the security group

    Is there a restriction on Amazon to use port 1935 only? Any debug I can turn on?
    Last edited by tavius; 04-23-2012 at 03:31 PM.

  2. #2

    Default

    Quote Originally Posted by tavius View Post
    Hi there ... I'm trying to set up a Wowza instance on Amazon using a different port, not 1935
    That works perfectly on my local Wowza (port 8888) but when I configure same thin on EC2, it doesn't work (I do have the port 8888 enabled on the security group

    Is there a restriction on Amazon to use port 1935 only? Any debug I can turn on?
    JEEZZ ... you guys should cancel my account!! I deserve it
    I apologize for the stupid question (which didn't make sense to me at the beginning to ask, but after hours of failing ....)
    A fresh air walk and some coffee let me find the problem ... it's actually me!!!

    Sorry for wasting your time!!!

    cheers

  3. #3
    Join Date
    May 2011
    Posts
    455

    Default

    Glad you figured it out.

    -Lisa

Similar Threads

  1. Replies: 1
    Last Post: 10-08-2014, 12:30 AM
  2. port 1936 vs port 1935
    By vision in forum Server Administration Discussion
    Replies: 1
    Last Post: 03-07-2012, 06:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •