Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Still have been unable to resolve this issue of connecting to my domain i bought,through my webserver. everything appears okay...well dns settings appear fine.so i'm thinking it's a server error. the ip address for server is the same one the router has assigned as open for port 80, so looks okay 192.168.220-server (dhcp client/router hands out within range of 1-128 where this no. is the last figure on the ip address list of digits.)
i'm thinking my SElinux is configured too strongly as i did get an error message initially when i tried to start up apache previously for he 1st time where it said my ssl certificate was missing ( i.e server probably needed securing) . i don't get that problem now however-apache starts up fine now .(after i changed the ram)
however i'm thinking the way security on my webserver is configured may well be too tight. in particular SElinux configuration. hence why my domain shows 'timed out errror' message when i try to connnect. i've been working on this particularproblem for least 2 weeks, probably a month actually. ( i've posted the same topic/problem on cable/dsl home webserver forum under dns/domain section)
I need to fucking master that command line one of these days, at least the basics .
oh and i've got that xfce desktop/wm running on fc3 with, i'm pretty sure ,SElinux enabled ( when i went through install). troubleshooting the webserver,anyone ? ? (dns settings appears fine)
And i use zoneedit btw, my registrar end and zoneedit's dns appears fine-- i use my dynamic wan isp assigned ip as a static ip for zoneedit( manually updating myself - twice in past 3 weeks so far so plenty of timefor dns propagation i would have thought-. the router is open. they all appear to add up-- the dns settings.
so given my dns appears fine i want to try trou8bleshooting the server, as i've spent too long on this problem ,unresolved.
There are 2 stages in this;
1. The registrar that you bought the name through has a place holder for the name (an IP address). They will either have the facility for you to change the address or you will have to request them to change this address to your address if it is a static address. If it's a dynamic address then you will have to use a 3rd party like www.dyndns.org to do this for you.
2. On the router side of your modem router you need to configure it to forward requests for port 80 to the server address on the lan that you are hosting the site.
Make sure that if you have a router with a built-in firewall that you use it (they are generally very good. Well mine is). Also setup a firewall on the server as well, as a precaution. This latter step is important!!. I also suggest preventing access via other ports unless you intend running a ftp or sftp server using the router. I personally have port 22 (sftp) closed except if I know I want to acess my server from outside the lan. This saves a lot of problems with "script kiddies" continually trying to access the server.
Same issue here. I have suse 10.0 with apache installed and started, listening to port 80. Set the linksys router to forward port 80 both TCP and UDP to local address of server, and I have dyndns set to the IP address of the router. If I change the port to something other than 80 typing the URL will lead to my router itself and prompt for a password. But I cannot get anything from the server when its set up properly. I get page cannot be displayed on windows and timeout from server on linux. The //localhost/ works though. Anyone with any information to help fix this I would greatly appreciate it =)
The netmonitor reports the port to not be open though ...
Are you sure port 80 is not blocked by your ISP. My ISP blocks port 80 (HTTP), 25 (SMTP), and 110 (POP3). Port 8080 will also work if your ISP blocks port 80. After you sort out what your ISP blocks, setup the router to forward only the port that you want. Also you will need to enable both UDP and TCP if you are setting up a DNS server. Do not use DMZ because your server will not be able handle all the attacks well.
To access the web server from outside your LAN, use your IP address. A site like ipchicken.com can help you get your IP address. Next type that IP address in the URL text box. It should bring up your web server. If it does, then you need to fix your DNS records. If it does not, check your logs in /var/log.
Any computer that is setup to serve resources like web pages should not be running GUI. The reason for this is GUI takes too much computer resources.
I recommend turning off remote management for the router because if you do not have a lengthy password then your router settings can be changed by anybody. Also your router can be hacked and a torjan can be installed that creates a back door to gain access to your computers and any network devices.
I don't know how to access routers firewall settings, don't see options for it. The IP address I get from any of those sites, when I type it in, it goes to my router where I need to type in the password for the router. If I change the port forwarding to say 5946 or whatever random number, chance apaches listening port, and type in my ip (220.127.116.11) or whatever in web browser with specific port 18.104.22.168:5946 It sits there for a bit like its looking for something, then I get the error messages. Netmonitor says the port does not look open no matter what port I forward... DMZ won't even open the computer to browzing, but //localhost/ does work..
1. Go to www.whatismyip.com. It will tell you what your WAN IP address is. Put that in a browser and see if it sees your website. If it does, you do not have your domain name service set up right. That is the IP that the DNS place (zoneedit) needs to have to let others find you by name.
2. Next, get the IP address of your webserver on YOUR LAN; use "ifconfig" in a shell and copy the IP address for your server ON YOUR LAN. Open up your router and be sure that this is the IP that has port 80 open. If it is not, correct it, and try #1 again.
3. Then, on another computer ON YOUR LAN, put the IP from #2 above into the browser and see if you can see your website. If Apache is running this almost has to work, so if it does not you have to work on Apache. If it works, try #1 again.
4. If #3 works, try your domain name in a browser. If it does not work with the domain name, but it does work with the WAN IP address then your DNS service is not set up correctly. If it does not work with the WAN IP but it does work with the LAN IP, then you either have port 80 blocked or the router has a configuration problem.
Come back here if you are still stuck. I have had a system like this running for years, and it is really cool when you get it working.
Damn I spent a while making that last reply and it didnt take =(
Linksys BEFSR81v3 is router make/model
Port forwarding is set up Correctly.
Apache I think is the culprit
It recieves a few signals to shut down every now and then and then says its ready again.
*Edit* I have to computers sitting side by side and #3 does not work.
**edit again** Actually #3 does work, now I need an outside line hehe.
*Edit third time* It works!!! lol I think the final change that made it work was that I had username and group set up both as daemon. Now username is set up to a username that is actually on the X GUI thingi (KDE) =) and the group is still daemon, but it works.
........Now to install PHP .........