Welcome to WebmasterWorld Guest from 184.108.40.206
It's a "can do" but it is going to be too slow if you have a medium to large site, fat pages and/or images.
this isn't really an adsense issue, more of a hosting issue, however in answer to your question i would host at home rather than free host, see how you get on, if it works then you can always pay for hosting.
be sure to try to access your site from an internet cafe or a friends house to see how it is and how quick, i'd focus strongly on having as much text and as little graphics as possible.
there are several threads here at WebmasterWorld with very good advice about the home hosting method.
You might as well just give up right now. There is a reason why no one else does this, and everyone tells you it's the wrong way to go. "
Don't listen to these people. I hosted my site with ADSL for over 3 years, along with an email server, without any problems whatsoever. You're not going to be banned for being unstable. If you're a network admin, I'm sure you hve no problems securing the server. And in my opinion, hosting things at home if possible is a lot more convenient than managing a 3rd party server elsewhere via ssh.
The only "problem" I had was that eventually the site grew so big that my ADSL upstream couldn't handle the traffic, so I moved to a dedicated server.
" I don't think Adsense would approve you if you don't have a domain or using free hosting."
Many people have AS on free hosts.
[edited by: Thez at 9:40 am (utc) on Mar. 7, 2006]
Because it's entirely mine, I can run ASP, ISAPI extensions, filters and database experiments whenever I like. I evn run an AdSense site on it.
I have no problems with speed, DNS or anything else for that matter.
The only possible liitation is the number of concurrent users is limited under PWS (but I can upgrade to IIS if I want to)
ADSL commonly has 256k upload speeds, in reality if you keep your pages sizes down (10k -) then you can handle 2-3 concurrent users - that probably is not going to be a problem.
To cut down the throughput on your upload you can host images, js, on free webspace and call them from there.
If you get any more commercial than Adsense, meaning for example products with prices, your ISP will probably kick you off. Look at your agreement.
I joined Adsense in mid 2003, at the time Google may have let anybody in, OR, they may have been quite stringent who knows?
Make absolutely sure you keep your site basic and use GZIP compression, all free with the APACHE.ORG webserver. Unless you've purchased Windows IIS Server you will not be able to use GZIP on IIS in XP.
Use FREE dynamic DNS to map IP addresses to your domain. If you look hard enough you can buy domains for less than $5.00 a year in single quantities. Point the domain's DNS server table at your free dynamic DNS provider. You will then have an IP address that may change occaisionally which is actually fabulous for security. You probably won't be able to run a mail server, but you certainly will have no trouble with email, all FREE.
Get a real domain, without it Adsense may reject you without thinking. There's little tracking for a ~tilde domain. The Google crawl and Google Adsense may both rely on stable "whois" information these days.
Regarding Google's crawl, remember Google doesn't read image files nor CSS files for it's index, just your web pages text content, so serving GZIP compressed content over a phone line is not that big of a deal. And Google now finally is crawling GZIP compressed content. Again you may beat the big guys, you have a dedicated server! Just the pipe is a little small.
What do you suggest doing in cases when port 80 is blocked by the ISP.
I want to start experimenting with home hosting, Iím connected via ADSL (fastest upload/download plan), via a router (no problem to configure the router for port forwarding) and have all the necessary components already installed and running on my XP machine (like PHP, Perl, Mysql, Apache). Have a couple of domain names that I can use too.
Port 80 is blocked by ISP and they change the ip every couple of weeks.
Thanks in advance.
All the domain names are mapped, DNS servers are simply names ones. Advantages are:
No hosting fees.
Easier to administrate.
No bandwidth limits!
No space limits! (6x 250gb drives!)
I KNOW its working!
No electricity bill because its on 24/7 anyway, for various reasons.
The only downtime is if
a) cable goes down. (so far this is less often than my proper hosting! About twice in 4 years.
b) My computer fails. (No prob I have a clone in the next room!
c) I have to reboot for sdome reason, like updates or software instalation. But that takes a minute. Most surfers wouldnt even notice!
As far as speed is concerned - not a problem. Web pages are but a few Kb - images are small.
Most people are reading not loading stuff. The diversity factor means that the upload speeds seldom ever max out for more than a couple of secs. According to DU Meter.
If you want say HUGE database stuff, or large files to download (limit to 128kb) then its a sensible and cheaper way.
My real hosting account has a single one of my adsense accounts on it. Only about 25 pages. It regularly goes over the 20gb monthly allowance and gets shut off! At least you can control that sort of thing!
And run a web server software of course!
Then the new domain will (in 24 hours) point to your computer. Thats it!
Edit. Didnt see bumpskis post!
I run 15 adsense site with 7000 daily page views on a free service, without a domain name! Google accept anything that responds properly, has real content, and isnt against their rules.
A little off topic, but, first make sure it's really blocked and against the rules, try to find it in writing. Or try another ISP!
I don't know what Google Adsense would think seeing a Port Number in the URL. Do a Google search on "inurl:8080 Adsense". I do see sites at port 8080 serving Adsense ads, but they may have other sites that they used to open their account.
You can see though that the port number being displayed will be very distracting.
Another port is cumbersome, one technique is to just tack a port number onto you domain name:
mydsldomain.com:8080 and set up your server to listen on this port. I'd think your ISP might look for this if they block port 80. As you can see from above Google will index your site and Adsense does display on these sites.
I actually have an old copy of a website running under Win XP IIS 5.1 at Port 8080, and (whoops) still showing targetted Adsense Ads, (I should pull them I guess). I have a current version of the same site running on the same PC using APACHE.ORG's free 2.0 webserver on Port 80. Of course port 80 is the default so you don't have to have a mydsldomain:80 in every URL(I), you can drop the :80
You can see though that the port number being displayed will be very distracting. Alternatives beyond this get complicated, probably unreliable, and probably cost more than a web host.
LINE CONNECTION(two cases)
1) cable modem(DL/UL: 3Mbps/700Kbps), port block on 80, dynamic IP
2) FTTH (DL/UL: 100Mbps/100Mbps), serving most high rise apartments here in korea, around us$30-40/month, port block on 80, dynamic IP
- Redhat Ent Server 3
- APF (Advanced Policy Firewall)
- use zoneedit free dns service to point my ip(my ip ever hardly changes, once a few month) and to forward port number to my designated port(first check to see if your port is open other than 80 - eg 81, 8080, etc)
- use ddclient to monitor change of ip and to syn with zoneedit server automatically when it happens
for both severs as a production level, i never had any major issue compare to my current colo server as far as running adsense. In this case, the url your visitors will see is (arbitrary_choice_of_your_own_words).mydomain.com:(port_number).
one problem you will face when you use port forwarding is that above noted url will be indexed by google, say 100,000 pages. Once you move on to hosting, dedicated, colocation server, your apache conf should be factored to accomodate those extraterrestrial port number that is indexed by search engines. Make sure your apache is listening both port 80 and the other port as well and your use your favorate rewrite to redirect permanantly to www.mydomain.com by issuing 301. Then again, there will be a whole new chapter of 301 related issues. And again, if you are moving on to shared hosting option, they probably won't do above setting customization only for you.
running server next to your bed, you can almost feel the heartbeat of your server. Especially when a bad and ill-scripted bot hits your server, you know it by heart. Then you can just iptable it to ban it permantly. One downside is the heat coming from the machine during the summer.
here in korea, download/upload speed 100Mbps/100Mbps is common place now for high-rise apartments and 10Mbps/500Kbps for single resident house. Most of websites tailed to local audiences are quite opposite to U.S. counterpart in terms of page load optimization. These are packed with image, flash, movie files. Quite annoying indeed. For production env, I have been using opera for years with disabled plugins and java. According to my experience with comcast cable in U.S., i don't see an issue of page load time as long as you get upload speed 200-500kbps for an average page.
my next project is to build a system in my basement comprising L4 switching, loadbalancing, raid5 on NAS network storage to run my 10+ sites. In this case, i'll get a dedicated line for sure..
- get your own domain a must
- if you can get fix ip, your required work reduces in half
- if you can have the port 80 open, your headache will be reduced tremendously for the long run
One downside is the heat coming from the machine during the summer: :)) : This is no probblem for me.