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 443"<br><br>Here is the reason why :<br><br>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 <a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
port forwarding</a> so connections can reach their Tor server. If you are
using ports 80 and 443 already but still want to help out, other useful
ports are 22, 110, and 143.<br><br>Here are the commands to run in a terminal to enable the right port forwarding :using sudo<br><br><span style="font-weight: bold; text-decoration: underline;">Forward port 443 to 9090</span>
<br>iptables -A PREROUTING -t nat -p tcp -i eth0 --dport 443 -j DNAT --to $IP:9090<br>iptables -A OUTPUT -t nat -p tcp --dport 443 -j DNAT --to $IP:9090<br><br><span style="font-weight: bold; text-decoration: underline;">
Forward port 80 to 9091</span><br>iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j DNAT --to $IP:9091<br>iptables -A INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j ACCEPT<br><br>After issuing these commands, start you tor server, and it should work.
<br><br>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 !<br><br>Yan<br><div><span class="gmail_quote">
On 4/27/06, <b class="gmail_sendername">Michael Holstein</b> <<a href="mailto:michael.holstein@csuohio.edu">michael.holstein@csuohio.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Bridged will work if you have an extra IP for the VM. NAT will also<br>work, but you need to modify the config to make it aware of it's<br>external address (and configure vmware-natd to forward 80/443).<br><br>~Mike.<br><br>
Landorin wrote:<br>> Okay, I'll try that out, thanks.<br>> I just ran into another problem: the orport appears to be unreachable.<br>> I really don't know how the connection works in VMWare environments.<br>> Do I have to forward the orport to the VMWare IP or to my Windows IP?
<br>> Also, does it need "bridged", "NAT" or "host-only" mode in VMWare?<br>><br>> Michael Holstein schrieb:<br>><br>>>>>Okay, I just tried out a different orport and now the server
<br>>>>>starts up. So somehow either port 443 is blocked already by<br>>>>>something else or it's because the permission is denied (since<br>>>>>it's a blank Ubuntu I guess it's the permission thing). Anything
<br>>>>>I can do about it?<br>>>><br>>>>"netstat -apn |grep 443" (as root) "lsof |grep 443" (as root)<br>>>><br>>>>either one will tell you what process is binding to 443. My guess
<br>>>>is Apache. Try "killall httpd" (as root) and then try again. Also<br>>>>try (path might vary) "/etc/rc.d/rc.httpd stop"<br>>>><br>>>>~Mike.<br>>>><br>
>>><br>><br>><br>><br>> --<br>> Accelerate cancer research with your PC:<br>> <a href="http://www.chem.ox.ac.uk/curecancer.html">http://www.chem.ox.ac.uk/curecancer.html</a><br>><br>> GPG key ID: 4096R/E9FD5518
<br></blockquote></div><br>