|
RCP
4.0 Users Questions Menu
|
Installation
List
of Categories
-
How do i request free rcp 4.0 installation or
help?
Webcomposing.com is offering free rcp 4.0
installation for all clients. In order to
request free and fast (within 48 hrs)
professional rcp installation, send a email with
your domain name ftp address login and password
and your rcp license number to:
sales@webcomposing.com
We will delete your ftp details directly after
successful installation. Our installation
service is 100% save. No data gets stored!
Top
-
I think i can install RCP myself! Do you have
any Tips for me?
If you have successfully installed many perl
scripts before, then you should able to install
RCP yourself. How ever there are a few things
that require extra attention.
RCP is base don two folders one .htaccess file
and a few trap files. RCP also requires that the
apache module Mod_Rewrite is turned on.
First upload or create the two „robot‰
folders. Set the correct permissions on the
folders and all files. Then run the install.cgi
and continue with the settings in the
settings.cgi. Then prepare the RCP .htaccess
file and upload it to your website. Upload the
basic trap files to your main web folder and any
other folder you wish. Now run the robots.txt
file test and your nearly finished installing
RCP.
IMPORTANT: Make sure you read the installation
read me file step by step and do not miss one
step or install might fail. A short version of
the install read me can be received from the RCP
news page. Click the brown button in the admin
area scroll down and request the read me wish
also explains you how to test RCP to be sure all
works well.
If you chose to install RCP yourself. Then it is
recommended to request after your install a RCP
website check. This means one staff member from
Webcomposing.com will run few tests to make sure
RCP is installed correctly.
Top
-
RCP is giving me only 500 and International
Server Errors?
This is the result of wrong file, folder
permissions (chmod) on the RCP files. Double or
triple check all permissions. Permissions. The
robot themplate folder must be chmoded 777 all
html files inside 666 other themplates images no
chmod needed. The cgi robot folder it self must
be chmoded 755. All file names ending on .cgi
must be chmoded 755 and all other files in this
folder 666.
If you are still unable to solve this problem
then you must contact sales@webcomposing.com for
free support.
Top
-
The RCP .htaccess file is not working or
giving problems.
For answers and help related to the .htaccess
file see the faq section "htaccess" or contact
sales@webcomposing.com
Top
-
My cgi folder has a different name then
cgi-bin!
On some clients webservers the "cgi-bin" folder
has a different name. Different cgi folder names
used are often "cgi-local" or "cgi-scripts" or
anything else. This is not a problem at all. The
script installation process goes exactly the
same. Enter the correct url and path to your cgi
folder during the install script form.
IMPORTANT... There is one important thing you
must change manually. The rcp .htaccess file has
standard code lines that point to a "cgi-bin"
folder. All you have to do is rename all the
"cgi-bin" names in the rcp .htaccess file to
your own name for your cgi folder. If you forget
this then the .htaccess file can not find your
scripts and can not activate RCP when its
needed. Contact RCP support if you need help on
this topic.
Top
-
My site has a password protected members area
or folder.
RCP will automatically protect all password
protected folder on your site against brute
force attacks (including proxy attacks). Each
folder that is protected with a .htaccess /
.htpasswd file will be protected! IMPORTANT: In
order to allow RCP to protect the folder you
will have to add yourself one line that is
required by RCP to your members area .htaccess
file. The line you must add is: deny from
env=ban
This line is required by RCP it will make sure
that any banned IP has no access to your members
area.
Sample standard code:
< limit GET POST PUT >
require valid-user
< /limit >
Sample code with the required RCP line:
< limit GET POST PUT >
deny from env=ban
require valid-user
< /limit >
Top
-
I use Password Sentry is it compatable with
RCP?
Yes !!! RCP is fully compatible with Password
Sentry and any other perl, php, asp or billing
script on your server. How ever those who use
Password Sentry must edit two lines in the RCP
.htaccesss file.
You need to comment out the next two lines 1:
< Files ~ "^.*$" > and line 2:< / Files
>.
All you have to do is place a: # in front of
these 2 lines so they look like:
#< Files ~ "^.*$" >
and
#< / Files >.
Thats all what is needed.
Top
-
IMPORTANT: My cgi-bin folder is not inside
the public web folder!
For those who have the cgi-bin folder not
located inside the htdocs or html (public web
folder) its important to have the cgi-bin folder
moved inside the htdocs or html or public web
folder so RCP can ban abusers from access to the
cgi-bin folder as well. Second options is to
create a "symbolic link" from the RCP .htaccess
file to your cgi-bin folder. Once one of these
options are done, any one banned in the public
folder will then also no longer have access to
the cgi-bin folder. Both options require root
access. Clients with a virtual hosting account
should contact there hosting company and ask the
sys-admin to move the cgi-bin folder or to
create the symbolic link. For those with a
dedicated server. Here is info on how to create
a "symbolic link"
Description: A symbolic link is a pointer to
another file or directory. It can be used just
like the original file or directory. A "symbolic
link" appears in a long listing (ls -l) with a
reference to the original file/directory. A
symbolic link, as opposed to a hard link, is
required when linking from one file system to
another and can be used within a file system as
well. To create a symbolic link, the syntax of
the command is similar to a copy or move
command: existing file first, destination file
second.
To create a symbolic link, type:
ln -s < existing_file > < link_name
>
Using the above example would be:
ln -s ../html/.htaccess /var/www/cgi-bin
This will place a alias of the .htaccess file
inside your cgi-bin folder.
If you do not plan to move the cgi-bin folder or
your unable to make a symbolic link then RCP
will still work but abusers that are blocked
from your site will have access to your cgi-bin
folder wish is not recommended!
Top
-
Server Errors and Return Codes
Explained
You've all
seen them, the cryptic error messages you get
sometimes when trying to find a site or certain
files. The error message you see is an actual
HTML page that someone has set up to describe
the error encountered. More often than not, they
don't explain what the error means. Here's a
breakout of what they mean. Note that I have
typed in the generic title of the error after
the number. Error descriptions are HTML pages
created by the server administrator, so they can
be made to say anything. YMMV <-- This is an
acronym for Your Mileage May Vary (It means you
will probably see this, but not always).
Redirection Codes
300 - Permanent Relocation Not only has this
page/file moved, but it's never coming back.
301 - Moved Target has been moved. Most
likely permanently.
302 - Moved temporarily/Redirect You will
get this error if someone has moved the target
page for only a short amount of time, it will
usually forward you to the correct URL. This is
a temporary relocation.
303 - Another temporary relocation, can't
remember what this one is for.
304 - Not Modified You have performed a
conditional GET. The linked page will only be
returned to you if it has been modified since a
certain date. If it hasn't been modified, you
get this message.
Client Request Codes
400 - Bad Request Your request just
didn't quite make sense for some reason.
401 - Access denied/Unauthorized This
usually shows up when you have tried to access a
file or page that requires a login and password
and you typed it incorrectly.
402 - Payment Required To get to the
linked page, you were supposed to pay first. You
can get this if you authorized incorrectly for
payment.
403 - Forbidden You don't have access to
this area. Sometimes you will get these by
accident if the webmaster has incorrectly set
the permission levels for a file or page. Even
if you have a valid login and password for this
file/URL you can not get to it.
404 - Requested URL not found This is the
most common one you will see. There are
generally two causes. One is that you typed the
URL incorrectly (or the link you clicked on was
typed incorrectly), and the other is that the
HTML page you are trying to view does not exist
anymore. Usually it's the latter, and it happens
quite frequently. Believe it or not, there is an
actual name for these deleted pages... Are you
ready? They're called COBWEBS. Go figure.
Server Errors
500 - Internal server error This message is
generated when an unexpected (read undefined)
error occurs. It's not sure what happened, so it
can't tell you.
501 - Not Implemented Whatever you tried
to do, the server software is not designed to do
it, or is not configured to do it. Usually you
will see this because of the way you tried to
authorize with a login and password.
502 - Service Temporarily Overloaded
There is too much going on with the server. It
could be too many processes running or too many
users. It's temporary, so check it later.
503 - Timed Out The server timed out
after 30 seconds. It couldn't complete your
request in the allotted amount of time. Could be
a busy server, or your connection is very
slow.
666 - Server possessed by evil spirits!
This one was a joke error I ran across on some
guys page a while back. I thought it was funny
enough to include
here.
Top
|
..
|
|
