Knowledge Base - FAQ
If you have not done so already send a request to support for a temporary domain such as username.kattare.com to get your site up and going on.
Transfer the content of your site over and get everything up and going on the username.kattare.com domain.
Setup the email addresses in the members section for all the addresses you need to receive email at. To be extra careful, in the members section under domain management setup you can set the default email for each domain. The default email is the 'catchall' email address. All email that does not already have an alias setup will be delivered this account. This will catch a lot more spam as well, as it's grabbing everything, but once your sure everything is going well you can set the default email back to devnull@kattare.com.
To prevent mail loss there are a few options:
a) Setup forwards on your old host (if available) to send the mail to your Kattare pop3 box. ie. pop3boxname@kattare.com
b) Leave everything as is and receive email at both hosts during the transition.
Once everything is setup you'll need to contact the registrar and change the name servers over to ours. Once this change has been initiated it can take up to 72 hours for it to take affect world wide. During this time email and site visitors could be sent to either web host so it's important not to cancel the old hosting service until this time has passed.
We recommend that you register your web site with the major search engines beginning with Yahoo, Google, WebCrawler, Lycos, and AltaVista. Look for an "add URL" option at each of these sites as well as links to other search engines. Currently, there is no charge to register with the aforementioned search engines. If desired, you can register with a site called, Submit-it!. This site allows you to enter your information one time and then submit to the many of the major search engines; however, a fee may be required.
To simulate a sub-web site, you have to create a new directory (or folder to MAC users) and then upload the main loading page (index.htm). You can setup as many sub-web sites as you wish. Kattare only charges additional fees if you register additional domains, have an account Level 3 or lower, and have us point them to your sub-directory. Corporate accounts can add as many sub-domains and full domains as they like.
We recommend using the "make directory" feature in our recommended FTP client software, WS_FTP. Click here for more...
You can use 'du' to get a disk usage report in great detail.
Use the following to get a basic breakdown in human readable format.
You can adjust the depth (how many directories it goes down) to whatever you like.
du --max-depth=1 -h
You can literally create and maintain your web pages, images, and scripts locally (IE, on your own PC at home.) and upload them to the web server at your leisure via FTP or Microsoft Frontpage. You can overwrite existing files or transfer a new file.
To init: (for user jim, please adjust accordingly)
cvs -d /home1/j/jim/cvs init
For more help on CVS:
man cvs
Remote access from another unix machine with cvs installed: (will require the login and password for user jim, and you will need to use your webserver hostname accordingly.)
export CVS_RSH=ssh
export CVSROOT=:ext:jim@webserver.kattare.com:/home1/j/jim/cvs
Then you can run cvs commands normally from your remote system like so:
cvs checkout blah
So it's pronounced something like Cat-tar
- Make sure your home directory is mode 711. This will allow you access, but pretty much keep everyone else out unless they specifically know of a file or directory inside your home directory they can poke at. EXCEPTION: If you have requested we turn on ASP.NET... Windows (over Samba) requires that your directory be mode 755 in order to operate. It sucks, but you can still go through your files and restrict things effectively.
- Our scripts will force the document root of any of your domains to be world readable and executable. If we didn't do that, apache wouldn't start. Apache needs to be able to see the document root of the virtual hosts it is serving.
- Generally, within your account the following files should be set to mode 600; *.xml, *.conf, *.php, *.inc, *.jsp, *.jar, *.class.
- And, generally, within your account you want the following files to be mode 700; *.pl, *.cgi. EXCEPTION: users that have requested mod_perl will want their PERL files to be world readable and executable.
- Specifically, any files containing database access details or other sensitive information need to be paid special attention. Mode 600 on such files is HIGHLY recommended.
As always, we're here for you. Don't hesitate to email us with specific questions and/or suggestions for improvement. Keeping your site secure is of extreme importance!
Once the InterNIC announces that your domain name has been registered (or transferred, if applicable), it usually takes about 72-hours before it is active. All internet providers must update their records (DNS tables) to reflect new site locations. This is called propagation.
- Main Headings
Hits represent the total number of requests made to the server during the given time period (month, day, hour etc..).
Files represent the total number of hits (requests) that actually resulted in something being sent back to the user. Not all hits will send data, such as 404-Not Found requests and requests for pages that are already in the browsers cache.
Tip: By looking at the difference between hits and files, you can get a rough indication of repeat visitors, as the greater the difference between the two, the more people are requesting pages they already have cached (have viewed already).
Sites is the number of unique IP addresses/hostnames that made requests to the server. Care should be taken when using this metric for anything other than that. Many users can appear to come from a single site, and they can also appear to come from many ip addresses so it should be used simply as a rough guage as to the number of visitors to your server.
Visits occur when some remote site makes a request for a page on your server for the first time. As long as the same site keeps making requests within a given timeout period, they will all be considered part of the same Visit. If the site makes a request to your server, and the length of time since the last request is greater than the specified timeout period (default is 30 minutes), a new Visit is started and counted, and the sequence repeats. Since only pages will trigger a visit, remotes sites that link to graphic and other non- page URLs will not be counted in the visit totals, reducing the number of false visits.
Pages are those URLs that would be considered the actual page being requested, and not all of the individual items that make it up (such as graphics and audio clips). Some people call this metric page views or page impressions, and defaults to any URL that has an extension of .htm, .html or .cgi.
A KByte (KB) is 1024 bytes (1 Kilobyte). Used to show the amount of data that was transfered between the server and the remote machine, based on the data found in the server log.
- Common Definitions
A Site is a remote machine that makes requests to your server, and is based on the remote machines IP Address/Hostname.
URL - Uniform Resource Locator. All requests made to a web server need to request something. A URL is that something, and represents an object somewhere on your server, that is accessable to the remote user, or results in an error (ie: 404 - Not found). URLs can be of any type (HTML, Audio, Graphics, etc...).
Referrers are those URLs that lead a user to your site or caused the browser to request something from your server. The vast majority of requests are made from your own URLs, since most HTML pages contain links to other objects such as graphics files. If one of your HTML pages contains links to 10 graphic images, then each request for the HTML page will produce 10 more hits with the referrer specified as the URL of your own HTML page.
Search Strings are obtained from examining the referrer string and looking for known patterns from various search engines. The search engines and the patterns to look for can be specified by the user within a configuration file. The default will catch most of the major ones.
Note: Only available if that information is contained in the server logs.
User Agents are a fancy name for browsers. Netscape, Opera, Konqueror, etc.. are all User Agents, and each reports itself in a unique way to your server. Keep in mind however, that many browsers allow the user to change it's reported name, so you might see some obvious fake names in the listing.
Note: Only available if that information is contained in the server logs.
Entry/Exit pages are those pages that were the first requested in a visit (Entry), and the last requested (Exit). These pages are calculated using the Visits logic above. When a visit is first triggered, the requested page is counted as an Entry page, and whatever the last requested URL was, is counted as an Exit page.
Countries are determined based on the top level domain of the requesting site. This is somewhat questionable however, as there is no longer strong enforcement of domains as there was in the past. A .COM domain may reside in the US, or somewhere else. An .IL domain may actually be in Isreal, however it may also be located in the US or elsewhere. The most common domains seen are .COM (US Commercial), .NET (Network), .ORG (Non-profit Organization) and .EDU (Educational). A large percentage may also be shown as Unresolved/Unknown, as a fairly large percentage of dialup and other customer access points do not resolve to a name and are left as an IP address.
Response Codes are defined as part of the HTTP/1.1 protocol (RFC 2068; See Chapter 10). These codes are generated by the web server and indicate the completion status of each request made to it.
- Common Definitions
<IfModule mod_gzip.c>
mod_gzip_on Off
</IfModule>Primary Nameserver: ns1.kattare.com
Primary Nameserver IP: 65.212.180.60
Secondary Nameserver: ns2.kattare.com
Secondary Nameserver IP: 204.13.11.60
FTP:
Supported via:
- FTP Proxy to backend ProFTPd installed on our file servers.
- Protocol is Passive or PASV FTP.
Hosts:
- ftp.kattare.com
Accounts:
- All Shell and FTP-Only accounts.
SFTP & SCP:
Supported via:
- OpenSSH installed on our web servers.
- Protocol is SSH File Transfer Protocol.
Hosts:
- www.yourdomain.com
- yourwebserver.kattare.com
Accounts:
- All Shell accounts.
FTPS aka FTPES:
Supported via:
- Direct connection to ProFTPd installed on our file servers.
- Protocol is FTP over EXPLICIT TLS or SSL.
Hosts:
- home1.kattare.com
- home2.kattare.com
- home3.kattare.com
- home4.kattare.com
- ... etc, etc... based on the path of your home directory.
Accounts:
- All Shell and FTP-Only accounts.-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
mQGiBEV0qrgRBACBYR2XCdlbyFfYDOYz+nI41JVaarDTSzbgW9JmBqm5AtS36IKh
hh2g/xHCTF44HUwCJEoTuJXLsFUU+tf8DnkZe3naXWZ/qt3Rst44tcIZsbkhTDYx
EjfLz2To09bWpqGKYvcy58JIfclWEVN3lck9iUwTyqkEpIePHnlzzZAGQwCglUOd
twKcqXvfli9quhp+ABxSkQ0D/2GzdKe7MsuDk/UJlEZzdh3tZWro3Fa85fMEiHOL
orAm15+iRbvH66HEByJJKAIhoh890IeHc9mvDN0JsepF2s5nkoMUIdovh0/unhJd
SfliYsTw9AlZQuWi2KvrsvtYRPa+GZpHXOiwKDY8PMmDsiYU/gtIYMyUXB9ZYhQ/
aTv8A/96SYL2FU698gWGR7sWW6EpZJc7r6LSxHJ29vLboS4aKCy49hOEZZzZZ9x2
5uaEAQJPWIJ3N65na9M4NttvTEyvUbaUf2ueyvH6s8FBz4MV+clPKb6p5Ox+2hCA
xUCnNN3B/tmA8U4pKh+qmzMXIFCFujJzv8iM2HZusBEyLnAJebQlRXRoYW4gQnVy
bnNpZGUgPGJ1cm5zaWRlQGthdHRhcmUuY29tPohgBBMRAgAgBQJFdKq4AhsDBgsJ
CAcDAgQVAggDBBYCAwECHgECF4AACgkQiJtBeUIXJjx4DQCfdJa7VkC+2wi6rsID
SNpCHuzOVyYAnj7qjzLYlJxN4EX2G0rGA9catvCRuQINBEV0qr0QCADPqOJGvOLV
dWdlcMe+zX4NVm8mtbNQhiop70t3jvhzEJhQbFjUXhKt4iC1Lwu0j+LPmW/0Ykha
jyZSEWr4qEClZahQjJkICFIllucuMKAcQtce4CyBrySxfKOvlGY2suq0qB3oEuzy
a6Zrl2ZiSvc4QFxfwUehKTdFbs0yBkircSlAY7iP4xOHF5iK3xwbBK14y2MlbAZj
FVvHqSHKLd8VpYBQrV6McN9/IMNs2SKYiTnCheTxpaB8xlmIsy0XzgJbNNlSuXZS
p4o936RR8YPUwCsFjGkgsXm3EoEGzFSmMOR13KF+/e1Sqm7vVjCxwbkAEwuE5Sw4
8gX89rhMGE0zAAMFCADBPdOW5PKD2oloW2VS0dbag+V9/Mo9tyBhf7pGWp/cV8O0
i0qTl7k0fD95jRmMzjbpQGtrYnhGKELQJNRwLvwNN5ZahrzYa2NnJUzF64r645LM
qv03OIlUHEeg48riEGsHQCZdC7D7650CC08KxpmkKvLFW8xEZ+NUnrofdzHYUF+5
HU5R9bTm/QLDAyAcQP7wXadovQ8qgcmg+pDHghq0NGzDYxLt7N8H1CQjKlMvbqRk
0p292hTrGXl9j+XHLMlH6nbQkmcUqVtlQaLb1Es9GQ+kAdg64LWvcIElaEh6wNHW
SWmFOzzZcdIi79syhvTlMiGaU7CFHXkuMUaxMNmPiEkEGBECAAkFAkV0qr0CGwwA
CgkQiJtBeUIXJjwT/ACZAcAeQbW1zfB8RtTeghH9/4A3ixAAnA1RjWM9fZtPVMqt
ac82ZQUa2pEZ
=oJNw
-----END PGP PUBLIC KEY BLOCK-----If you would like your site to NOT be gzipped by default, please let us know. We can turn it off on a per-virtualhost basis.
The following is left here for historical purposes only:
Three reasons:
1) Zipping everything before it goes out increases the load on the server. This is significant especially when the server is getting lots of hits.
2) Just about all you can safely zip is text, html, and xml, most of which is small already and/or is generated by scripting languages (PHP/PERL/JSP/etc) that have compression capabilities built in. Everything else (mp3, mpeg, wmv, jpg, gif, png, etc...) is already compressed and will actually be larger and slower if you try to zip them.
3) A zipped website has to be completely transferred before the browser can decompress it and render it. Uncompressed html on the other hand gets rendered by the browser as it is downloaded. Thus uncompressed html will often appear to download and display faster, even if the complete download takes a second or two longer.
[Submit a Question]
Indicates a question that only Kattare members can view. (For security reasons, sorry.)
Comments or feedback? Email: support@kattare.com
Legal: Terms of Service | Privacy Policy | DMCA Procedure | Trademarks