OK, then add this line to /etc/hosts and end it with a hard carriage return

192.168.0.3 smsfrancis.homeftp.net

That will fix your problem of seeing your website. Of course you won't be going out thru the Net to see it, but you don't need to. :-)

Cheers.

Well, what a day!

Thanks for the webalizer info, I installed that but then apache decided to be a complete ***** and nothing worked at all. So I installed apache again and this didnt work, then finally i found the slackware package manager and uninstalled apache. Oddly enough, it uninstalled the problem but apache was still there in the same place!

Ah well, as long as it works. I also setup a forwarding page with my domain host (their own forwarding options DONT work, so I had to create my own forwarding index.html with a meta tag). Finally, I changed the dyndns name so that it isnt solely homeftp as this is a bit misnamed now that its not going to be ftp.

So! This should finally work how I wanted it!!

http://www.smsfrancis.co.uk ---- 3 seconds ----> http://smsfrancis.is-a-geek.com

You can also still use the old homeftp link.. I'm also assuming that the stats thing will still count them no matter what link you use because at the end of the day its the same index.html file in my /root/smsfrancis/ folder?

So thank you for all your help, guys!

Just a couple more questions:

1. How do I create an icon on the desktop that, when double clicked, will run the command:

cd /root/smsfrancis/stats/
webalizer /usr/local/apache2/logs/access_logs

2. I saw at some point today a version of webalizer that shows geographical data on a map or plot of some sort, but now I cant find the link again. Anyone know what it is? This would provide some interesting information!

3. What can the budding trainee web administrator put on his website/server next?!

Hello, I'm interested in this thread because I've got a netgear dg834 and also can't access my webpage. Anyway, I was wondering why you had to install apache as it comes with slackware. Also, although you don't seem to have any trouble with it, is your IP static or dynamic? My dyndns domain requires extra updating software. (ddclient).

Now you mention it.. I cant actually remember if I installed apache or not.. perhaps I merely updated it or, more likely, i never installed it in the first place as I tried to keep the install size of Slackware down to a minimum - with the idea that I'd only install what I needed as I needed it.

The problem of not being able to see a 'live' net version of my website is a slight pain, and no one has offered a way to get around it other than to view it locally. Maybe its router specific.. tho there must be a way around it.

I *think* my ip is static, tho I dont pay much attention to it and only rarely restart the router and things like that. Either way, in the netgear router admin page, there is a section where you fill in the dyndns.org details and the router informs the dyndns service of my latest ip (even if it's the same) at set time intervals.

Perhaps, if youre using another dyndns service provider, then you have to use the extra software as the router setup only allows you to choose www.dyndns.org from the provider drop down menu.

So the router actually does the IP updating? OK. Anyway I thought I would point you in the direction of the apache docs. On my standard slackware install they're at /var/www/htdocs/manual/howto and there are some good ones in /manual/misc/tutorials.html.

The reason why I cant get to my webpage is unclear at the moment. I've tried altering hosts. I can see it through http://192.168.0.2 though. I'm finding having a firewall/router/modem device creates extra work when setting up a server. It might be easier to set up a router/firewall manually. I have to negotiate the netgear device as well as sorting out my system. If I want an iptables firewall here, I have to open ports on that and the modem. It's good for automating things, but not so good if you don't want that.

Well, youre obviously a bit more experienced than me

Though I've found no big difficulties yet, it updates the dyn, lets out the http port so that the world can see my webserver and I just set it up on samba and that worked without any hitches at all and I can navigate my root folder from Windows XP.

The *only* problem is not being able to see my own website, which isnt a major issue.

Thanks for the man links too, will check them out.

But as I'm just a fiddling, low-spec trainee type.. I'm still open to new things I can add and try out Was thinking of a mail server.. tho dunno what I'd use it for or how yet...

oh and name of that world-plotting webalizer pls!

I got a lot of info from shilo's guide at the top of the slackware forum. He gives a very basic webserver/email server setup amongst other things. If you follow his guide for using sendmail, I can send and receive mail using my dyndns domain. You can tick some settings via the netgear router, such as wildcards for email. Slackware has sendmail, a pop3 client and also IMAP ready installed, so it's really just a matter of activating them.

Also you mentioned you wanted some app for checking your web logs. There is one called 'analog', which will give you all sorts of info about who is visiting your page, from where, what they're clicking on etc. If you go to www.linuxpackages.net, they have a slackware compiled version of it. Unforetunately it is only for slackware 10. Alternatively go to the analog homepage and compile from source. www.analog.cx.

Yes, I've got analog running. 37.76% of my hits have come from Christmas Island! Amazing. I would definately recommend installing analog. If you need any help let me know. I've got a file full of stats, pye charts etc. (.cx?)

I would like to publish my webpage to let outside world take a look. The reason why I can not get to webpage is unclear at the moment. Any help would be greatly appreciated

I find several threads related to this topic. And I got similar problems, so I post my questions here. I have tried many different things and I just post what I have done here.

I forward 2 ports 80(http) and 53(DNS), let incoming requests on web server (192.168.1.107)

Also put the private IP (192.168.1.107) in DMZ which let all incoming ports open on only one machine. My dynamic IP account (xxxx.dyndns.org) details also set in the gateway router wrt54g which update the IP automatically.

If outside machines access my page(http://www.mysite.com), the registered domain points to my dynamic IP account (xxxx.dyndns.org). And account details also set in the gateway router.

My /etc/hosts
My configure in /etc/httpd/conf/httpd.conf should be fine.

I also have a look of xinetd.conf, hosts.allow,hosts.deny..............

While stop the iptables service, I use text browser lynx to test and I have the following errors:
503 Service unavailable

ERROR
The requested URL could not be retrieved
While trying to retrieve the URL http://xxxx.dyndns.org
The follow error was encountered:
connection failed
They system returned:
(111) connection refused

I can only see the page in local machine but not from outside, others machines in the LAN can only view the page without graphic.

Any help would be greatly appreciated

Contrary to my previous post I haven't got analog seeing my apache log file, so I'd appreciate some help with this if anyone can give it.

if you're going to forward ports, you should use static IPs.

not even from other machines on the network? you probably have a configuration error with the web server or your dyndns.org account.

I installed this analog program without problems, and changed the analog.cfg to have the lines

Logfile /usr/local/apache2/logs/access_log
output /root/smsfrancis/results.html

Unfortunately, it gives the error that the log file has a large number of corrupt lines. If youre having similar problems and solve them, simcox, pls tell me what to do!

That's exactly the problem. It seems to be quite a common one. I haven't found the answer yet though.

Hopefully one of us will find it.. bit frustrating. Also downloaded and installed www.reportmagic.org which gives a more graphical output for the analog-created files.