Weird behavior of my server

Yanick McDonald ymcdonald at
Thu Apr 27 17:15:30 UTC 2006

I was able to install a tor server in a Ubuntu VMWare player, and
experienced the same problem you're having with the "Cannot bind to port

Here is the reason why :

10. If your computer isn't running a webserver, please consider changing
your ORPort to 443 and your DirPort to 80. Many Tor users are stuck behind
firewalls that only let them browse the web, and this change will let them
reach your Tor server. Win32 servers can simply change their ORPort and
DirPort directly in their torrc and restart Tor. OS X or Unix servers can't
bind directly to these ports (since they don't run as root), so they will
need to set up some sort of port
connections can reach their Tor server. If you are using ports 80 and
already but still want to help out, other useful ports are 22, 110, and 143.

Here are the commands to run in a terminal to enable the right port
forwarding :using sudo

Forward port 443 to 9090
iptables -A PREROUTING -t nat -p tcp -i eth0 --dport 443 -j DNAT --to
iptables -A OUTPUT -t nat -p tcp --dport 443 -j DNAT --to $IP:9090

Forward port 80 to 9091
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j DNAT --to
iptables -A INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j ACCEPT

After issuing these commands, start you tor server, and it should work.

I am a beginner with linux as well, i found out these commands by
experiencing all sort of things, they work for me, except that my dirport is
not visible, and i don't know why !

On 4/27/06, Michael Holstein <michael.holstein at> wrote:
> Bridged will work if you have an extra IP for the VM. NAT will also
> work, but you need to modify the config to make it aware of it's
> external address (and configure vmware-natd to forward 80/443).
> ~Mike.
> Landorin wrote:
> > Okay, I'll try that out, thanks.
> > I just ran into another problem: the orport appears to be unreachable.
> > I really don't know how the connection works in VMWare environments.
> > Do I have to forward the orport to the VMWare IP or to my Windows IP?
> > Also, does it need "bridged", "NAT" or "host-only" mode in VMWare?
> >
> > Michael Holstein schrieb:
> >
> >>>>Okay, I just tried out a different orport and now the server
> >>>>starts up. So somehow either port 443 is blocked already by
> >>>>something else or it's because the permission is denied (since
> >>>>it's a blank Ubuntu I guess it's the permission thing). Anything
> >>>>I can do about it?
> >>>
> >>>"netstat -apn |grep 443" (as root) "lsof |grep 443" (as root)
> >>>
> >>>either one will tell you what process is binding to 443. My guess
> >>>is Apache. Try "killall httpd" (as root) and then try again. Also
> >>>try (path might vary) "/etc/rc.d/rc.httpd stop"
> >>>
> >>>~Mike.
> >>>
> >>>
> >
> >
> >
> > --
> > Accelerate cancer research with your PC:
> >
> >
> > GPG key ID: 4096R/E9FD5518
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the tor-talk mailing list