Bind failed: ([any]:80): java.net.SocketException: Permission denied

[Erik_Luyten]

When I try to activate port 80 I get a “Permission denied” warning.

I’m logged into the Mac OSX 10.6.6 as the only user on the system and have admin rights. I configured the /Library/WowzaMediaServer-2.2.3/conf/VHost.xml file as requested.

When I startup the server with the Wowza Startup app all requested ports are bound except port 80 with the Permission denied warning. The same happens if I use command line and startup.sh in the bin directory. When i use sudo ./startup.sh port 80 will bind.

Where do I set permissions so port 80 will bind without have to use sudo ?

INFO server comment - defaultVHost threads[h/t]:120/80 home:/Library/WowzaMediaServer

INFO vhost comment defaultVHost Bind attempt ([any]:1935:4)

INFO vhost comment defaultVHost Bind successful ([any]:1935)

INFO vhost comment defaultVHost Bind attempt ([any]:80:4)

WARN vhost comment defaultVHost Bind failed: ([any]:80): java.net.SocketException: Permission denied

INFO vhost comment defaultVHost Bind attempt ([any]:8086:1)

INFO vhost comment defaultVHost Bind successful ([any]:8086)

INFO server comment - Wowza Media Server is started!

<<

[Andrew_Kennedy]

I believe any port below 1024 requires the process to be running as root/admin.

Shamrock

[Richard_Lanham]

This indicates that there is a web server on that machine. If you can’t use 1935, 80 or 443, you might try 8080. You will have to use that port (or other alt port you determine will work) on every playback and publish url that you use with Wowza

Richard

[ming_tsai]

use sudo to start wowza to avoid permission problem:

sudo sh startup.sh

[Ramadhian_Moestafa]

I have the same problem on my Fedora 17 …

running wowza service using root user , produce the same error

INFO server comment - Server runmode: standalone

INFO server comment - Server native.platform: linux

INFO server comment - Server threads[h/t]: 10/10

INFO server comment - CMDInterface now listening: [any]:8083

INFO vhost vhost-start defaultVHost -

INFO server comment - defaultVHost threads[h/t]:120/80 home:/usr/local/WowzaMediaServer

INFO vhost comment defaultVHost Bind attempt ([any]:80:4)

WARN vhost comment defaultVHost Bind failed: ([any]:80): java.net.SocketException: Permission denied

INFO vhost comment defaultVHost Bind attempt ([any]:554:4)

WARN vhost comment defaultVHost Bind failed: ([any]:554): java.net.SocketException: Permission denied

INFO vhost comment defaultVHost Bind attempt ([any]:1935:4)

INFO vhost comment defaultVHost Bind successful ([any]:1935)

INFO vhost comment defaultVHost Bind attempt ([any]:8086:1)

INFO vhost comment defaultVHost Bind successful ([any]:8086)

INFO server comment - Server.startShutdownHook: Start server shutdown hook

INFO server comment - Wowza Media Server is started!

80,554,1935 --> vi VHost.xml

[Roger_Littin1]

Hi,

It looks like it is not actually the root user which is starting wowza. As Shamrock has mentioned, any port below 1024 requires root user to bind to it.

It could also be an seLinux permission problem.

What does the getenforce command return?

Try setenforce 0 before starting Wowza.

Roger.

[Damien_Pascoe]

hey all im having the same problem here…

I have opened ports 80 and 443 through the vhost.xml and upon start up it comes back with the same error message…??

Can someone please give me some clear explanations on how to run these extra scripts to solve the permissions problem…?

Ps. I cant stream through 1935 my ISP wont give me port forwarding permissions… (it works fine but users cant see the stream.)