sameersbn / docker-wowza

Dockerfile to containerize Wowza Streaming Engine
MIT License
64 stars 42 forks source link

Cannot connect to Wowza Streaming Enginer Service (http://localhost:8087) #23

Open ghost opened 7 years ago

ghost commented 7 years ago

I've installed the wowza docker images following the instruction. And run it by docker-compose. I can login to port 8088 webpage and enter the account and password, but it shown below message "Wowza Streaming Engine Manager could not connect to the Wowza Steaming Engine service(http://localhost:8087). Verify that the Wowza Streaming Engine service has started and is running."

I use `docker exec' to enter the wowza container and type 'netstat -lnp4' to check the listen port, however I didn't see any program listen and bind 8087 port. Could you please guide me how to solve this issue? Thank you very much.

barbaluc commented 7 years ago

I have the same issue and I had to run service WowzaStreamingEngine start inside the container to fix it.

sameersbn commented 7 years ago

Hi @jamie777 @barbaluc, Please note that Wowza Media Systems now packages and publishes an official docker image. Instructions for which are well documented in https://www.wowza.com/forums/content.php?867-How-to-set-up-Wowza-Streaming-Engine-using-Docker.

I suggest you to evaluate the wowzamedia/wowza-streaming-engine-linux docker image for your usage.

Please close this report if that fixes the issue for you.

quanghuy1288 commented 7 years ago

still see this error on https://hub.docker.com/r/wowzamedia/wowza-streaming-engine-linux/4.5.0

I run this command: docker run -it --name wowza --restart always --expose 1935/tcp --expose 8086/tcp --expose 8087/tcp --expose 8088/tcp --publish 1935:1935 --publish 8086:8086 --publish 8087:8087 --publish 8088:8088 --volume /home/vega --entrypoint /sbin/entrypoint.sh --env WSE_MGR_USER=root --env WSE_MGR_PASS=XXXX --env WSE_LIC=ET1E4-Y3wpX-Jr8xh-QW9Ua-W3M7M-W6mBM-8HYmJbcxbP3D wowzamedia/wowza-streaming-engine-linux:4.6.0

cmosguy commented 6 years ago

Has anyone else resolved this issue? I am seeing the same problem

dottgonzo commented 6 years ago

+1

victorelec14 commented 4 years ago

+1

osztrovszky commented 4 years ago

+1