Wheel of Fire Posted February 27, 2008 Report Share Posted February 27, 2008 It took 10 minutes to setup and the last two days have been trying to get it viewable from my ip address. I established that port 80 is not blocked by setting my router's wan interface to listen on port 80. Asked a friend in Atlanta to log in. He did. No problem with incoming port 80 traffic. I made sure the local address--192.168.254.200--was forwarding to localhost. No problem there. I followed U Central's instructions on dealing with the Apache conf file to open it to the world. No go. I attempted the "alternate port" process to establish that the problem is on my end. I tried 81, 82, 4321, 8050, 8080 and 8090 to the exact same result: views perfectly locally, can't connect remotely. I'm out of ideas, boys and girls. My brain is fried. Please offer suggestions on getting this to become a public site rather than a private site. Peace. Quote Link to comment Share on other sites More sharing options...
olajideolaolorun Posted February 28, 2008 Report Share Posted February 28, 2008 Check http://center.uniformserver.com ;-) Quote Best Regards Olajide Olaolorun The Uniform Server Development Team Link to comment Share on other sites More sharing options...
Wheel of Fire Posted February 28, 2008 Author Report Share Posted February 28, 2008 Check http://center.uniformserver.com ;-) Read the original post. Did that. Thanks anyway. Checking again... Ok, under "general problems", I ran the netstat command. Got 0.0.0.0:80. Taking the word "any" seriously, I'm moving to disable this.... LISTENING says 5976... when I run the tasklist command, I get an error saying that the search filter cannot be recognized. Moving on... tried to set an alternate port to 8080. I get to the administrative panel but whenever I type http://localhost:8080, I get a redirect to just localhost and no connection to my site. Back to 80. Quote Link to comment Share on other sites More sharing options...
Ric Posted February 28, 2008 Report Share Posted February 28, 2008 I have read this post several times. Take a step back! 1) Uniform server is working (port 80); you see the splash page and apanel. (No need to change any ports, with apanel displayed the server is working.)2) You indicate your router is accessible from outside (Asked a friend in Atlanta to log in.) The problem seems as if it’s the bits in-between 1 and 2 causing the problem. Note: 0.0.0.0:80 is not a problem local loop back. Uniform Server stops any external access using .htaccess in folder www Putting your server on-line make sure these lines have been commented out as shown: #Order Deny,Allow#Deny from all#Allow from 127.0.0.1 With the above you do not have a problem with the server. What concerns me is this IP 192.168.254.200 it strikes me as being a printer IP. I would be interested in a post when you do an ipconfig /all It looks like a network set-up problem. I am no expert in this area, but I think you are chasing the wrong dragons tail! All the bestRic Help any network experts. Quote Link to comment Share on other sites More sharing options...
Wheel of Fire Posted February 29, 2008 Author Report Share Posted February 29, 2008 I have read this post several times. Take a step back! 1) Uniform server is working (port 80); you see the splash page and apanel. (No need to change any ports, with apanel displayed the server is working.) I agree. 2) You indicate your router is accessible from outside (Asked a friend in Atlanta to log in.) Correct.The problem seems as if it’s the bits in-between 1 and 2 causing the problem. Note: 0.0.0.0:80 is not a problem local loop back. Uniform Server stops any external access using .htaccess in folder www Putting your server on-line make sure these lines have been commented out as shown: #Order Deny,Allow#Deny from all#Allow from 127.0.0.1 With the above you do not have a problem with the server. Theoretically. What concerns me is this IP 192.168.254.200 it strikes me as being a printer IP. I would be interested in a post when you do an ipconfig /all It looks like a network set-up problem. The .200 address is the location of my computer at the end of a double NAT. The setup is cable modem--> voip--> router--> PC. The linksys2102 has a pass-through which allows it to get the bandwidth it needs before passing data on to the router. In this setup, the voip adapter is the router and what would typically be the router is a dumb switch. To setup port forwarding properly for applications like bittorrent, the PC needs a static address above the dhcp assignment range. In my case, that was .200. When I set the PC to dynamically obtain an ip address, it now shows as the voip adapter address. Will tackle it again later today. If you have any ideas, please share. I appreciate your response.I am no expert in this area, but I think you are chasing the wrong dragons tail! All the bestRic Help any network experts. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.