Miscellaneous How-To's
Return to
Main Index
Anonymous FTP Setup
Your anonymous ftp site is completely different
from your web site. When people ftp to your domain anonymously, they will
see the following directories:
bin/ dev/ etc/ incoming/ lib/ pub/
"pub" is where you should put all your anonymously
accessible files.
"incoming" is for the anonymous users to upload
files.
For security the following applies:
-
Only the incoming directory can be written to anonymously
-
Subdirectories are not creatable
-
The incoming directory is not readable by people dropping
files there
You are responsible for any "pirated" software
uploaded by the anonymous users. The anonymous ftp sites will be periodically
monitored for any abuses.
You may ignore the other directories.
Access Via The Web
To access the anonymous FTP site via the web, use
the following
address:
ftp://yourdomain.com/pub/
Your HTML to download a file called mirc511s.exe from
a webpage would look like this:
<A HREF="ftp://yourdomain.com/pub/mirc511s.exe">Download
Mirc Now</A>
You should tell your visitors that they may need
to right-click on the link if they are PC users, or if they use a Macintosh,
they need to hold down the mouse button on the link, then select the appropriate
option from the Pop-up menu.
Please note it's possible during peak hours to receive
a "too many anonymous users error", We must restrict the number of simultaneous
anonymous users to keep the webserver and normal FTP performance within
normal limits. If you receive this error often you may want to put you
downloadable files in your main web directory and link to them with an
http call
Example:
http://yourdomain.com/files.zip
This assumes the zip files are in the main web
directory.
Note - if your customer experiences slow
download performance, chances are it's a problem on the internet. We maintain
a large margin of available bandwidth so bottlenecks never occur within
our network. Please feel free to send an inquiry to be sure all the servers
are operating properly, if you include there ISP's IP# we will run traceroutes
to see where the delays are occurring.
Return to
Main Index
Go To Top of Page
Password
Protected Web Directory
NOTE: This feature is not installed on new
sites, password protecting a subdirectory can now be done with the PlusMail
control panel.
Virtual Publisher Security System (for
qualifying accounts).
To password protect different directories on your domain
you can use the Virtual Publisher Security System (for qualifying accounts).
If you have this on your account, the administrator's page with directions
and forms for entering new directories and users is found at:
http://www.yourdomain.com/password/admin.html
Netscape or Internet Explorer
Using Netscape or Internet Explorer, you can create
secure
directories and add users and passwords. The admin
page is very
simple to use. Just avoid adding groups or users
with spaces in their
names as this produces errors.
FrontPage
Note for Front Page users: The password administration
script works poorly on FrontPage for sites. You will still receive it installed
by default but we cannot provide any support if you choose to use it. Below
are some guidelines you should follow. It is very important that any directory
you are trying to protect be world readable and Writable.
This is done by the following Unix command: chmod 777 directory-name. The
main directory and any subdirectories will need to be changed in this way.
Also make the /password directory chmod -R 777.
Return
to Main Index
Go To Top of Page
Setting
up Your Own "404:File Not Found" Error Page
A file already exists in the www directory of your
server. It's called missing.html. You can edit it to your liking, or create
your own. As long as it's called missing.html and it's in your root www
directory, the server will display it whenever someone tries to access
a page on your domain that does not exist.
Long File Names
There is no limitation for the length of file names on
the server. However, only names containing from 3-16 letters are legal
for email accounts, FTP accounts, and Telnet accounts.
Zip/Unzip Files
This Unix program is compatible with the zip program
for DOS and Windows. To zip files, first have the files uploaded to your
server, then log into your account with Telnet. Navigate to the directory
where the files are that you want to zip.
(for instance by typing cd www then cd sounds).
Then type: zip myzip file1 file2 file3
This puts the files "file1", "file2", and "file3" into
a new zip archive called
"myzip.zip".
On the other hand, if you had the archive"myzip.zip"
and wanted to get back the files, you would type: unzip myzip
Typing zip or unzip by itself will give you a usage
summary, showing nearly all the options available.
Return to
Main Index
Go To Top of Page
Other Programs
Java Chat
We provide a selection of Java Chat programs for use
on your domain. Extra charges
apply for use of this feature. See our fee schedule for
pricing. If you have applied for
basic Java Chat, look on your website for a chat directory.
It will already be configured
for your server. To join the chat, with your browser,
go to:
http://www.yourdomain.com/chat
The page can be customized, but leave all the tags alone
that have to do with
<APPLET CODE>.
These rooms are capable of up to 20 users at one time.
Return to
Main Index
Go To Top of Page
Real Audio/Real
Video
Real Audio or Real Audio/Video is
available for an extra charge. See our fee schedule
for details. Real Audio is a real time audio
transmission/player system. A digital audio stream is transmitted from the
server over the Internet to the destination and played immediately, rather
than being stored to disk first and then played.
Each audio/video clip requires two files: a metafile with
extension .ram, and the digital audio clip itself, with extension
.ra or .rm.
The .ram file holds one or more lines of ASCII text, each
of which references the .ra file
to be played
when the .ram file is accessed by the browser. Entries in .ram files have
the form:
pnm://machinename.host4u.net/yourdomain/name-of-clip.ra
or
rtsp://machinename.host4u.net/yourdomain/name-of-clip.ra
The .ram file may be placed anywhere in your www directory.
The binary clips MUST be uploaded to the 'realaudio' subdirectory,
which is located in your www directory. When you access the .ram file through a web
browser (http://yourdomain.com/yourfile.ram)
it will tell the server where to look for the clip, and if you have RealPlayer
installed on your computer, the Realaudio/video clip should start playing right away.
Important: In order to use the G2 features such as multi-rate
SureStream and Slide Presentations (.smi), You must use rtsp:// in the .ram file.
The metafiles (.ram) must be uploaded in ASCII mode while
the clips (.ra or .rm) must be uploaded in BINARY mode.
Return to
Main Index
Go To Top of Page
Majordomo
If you wish to to have a Majordomo listserver activated,
email us and tell us the name you would like, be sure to check with sales
for pricing. Make sure it has a different name than the name of your domain.
For instance if your domain is fredhappy.com, you might want to
ask for fredhappydomo.
Once we have set up your Majordomo listserver, you
can get help by sending email to
majordomo@yourdomain.com.
On the first line of your email, just type the word HELP.
You
will be sent a general help file. If you want more detailed instructions
on using Majordomo, email to:
Domo@safe-order.net For full instructions
Another great resource for Majordomo information
is:
http://www.greatcircle.com/majordomo/majordomo.manual.txt
PHP3
PHP3 is a 3rd party scripting engine. Please
Note: We do not provide support for PHP3. We have added
it for users that our already familiar with it. To use PHP3 on your
domain just end the php pagewith .php3 rather than .html
Return to
Main Index
Go To Top of Page
Microsoft FrontPage
Microsoft FrontPage is a WYSIWYG (what you see is what
you get) web building program. If you use, or plan to use FrontPage to
build and manage your website you must be sure to indicate this when opening
your account. FrontPage requires special "extensions" installed on the
server. If you do not have a FrontPage Account, you will need to contact
us to have your account modified before your FrontPage Web will work.
Publishing
Your FrontPage Web
After you have built your web pages on your computer,
you will be ready to publish them. Basically, this just means that you
will upload them to our server. Once this is done, your pages will be viewable
from the web. However, you must do this in the following manner.
Warning:
FrontPage Account holders should never use FTP to transfer files
as it can damage the FrontPage extensions.
1. Launch FrontPage Explorer and open the
web you’ve created on your computer.
2. From the menu at the top of the window, select
File,
then Publish
3. A) If this is the first time you publish
to our server, select More Webs and enter the location you want
to publish your FrontPage web to. (www.yourdomain.com) Hit
Return (Enter) on your keyboard.
B) If you have published
to the server before, your "Destination Web Server" (www.yourdomain.com)
will appear in the Publish window.
IMPORTANT: Use www.yourdomain.com
as the Destination Web Server to publish to our server. Leave the
"Destination Web Name" blank.
4. You will be asked for your USERNAME and PASSWORD.
This is your domain's User ID and your FrontPage Password (which may be
different than your regular Telnet/FTP/POP password). If you're not sure
what it is or if you aren't allowed past this point, you'll need to contact
us for a new FrontPage password.
5. You can watch the progression of the upload
by looking at the bottom left corner of FrontPage Explorer.
Return
to Main Index
Go To Top of Page
Open
Your Published Web
Once your FrontPage Web is published and online, you
will need to access it to make updates and changes. Be sure that you are
connected to the internet before attempting to open your web on our server.
1. Open FrontPage Explorer and choose File
> Open FrontPage Web.
2. You can now choose to open a previously created
web on your PC or your web on our server.
3. Highlight the appropriate web or type in the
web address (www.yourdomain.com) and click OK.
4. Enter your Username and FrontPage Password if
required.
5. Make modifications and recalculate links if
needed. (See your FrontPage Manual for info on when it's necessary
to recalculate links.)
Return
to Main Index
Go To Top of Page
Troubleshooting
Common Problems with FP98
The following are common problems and solutions encountered
with using FrontPage and FrontPage98. If you are having a problem not listed
here, please feel free to contact support for help.
Getting error - "Root Web Busy"
FTP or Telnet to your site and remove the "service.lck"
file in /www/_vti_pvt. This usually happens when a FrontPage session
is interrupted before completion.
Server timing out when publishing large sites.
This difficulty arises when the uploading link
times out in the process of copying the web to our server. The only suggestion
Microsoft has offered so far is to break the main web into a group of sub
webs on
your PC, then upload these individually.
If this problem persists for you, please contact support.
Getting Error - "Front Page Extensions not Installed"
We often see this error being reported even when the
extensions have been installed. If you get this error, please contact
support and we'll make sure the extensions are installed and repair them
if necessary.
NOTE: The extensions are easily corrupted.
Please use only FrontPage Explorer to update your web site on the server.
Never use FTP.
I published but my web's not there!
This will happen when the "Destination Web Name"
is filled in when publishing to our server. This box should be left blank.
If you put any other name in this box it will create a subdirectory off
of your root web and copy all of your files into it. Your site will
exist under a subdirectory instead of at the top level /www where it should
be.
My counter, bbs, guestbook, etc isn't working.
These problems are generally due to incorrect permissions
on either the directory, file(s) or cgi script(s) that are associated with
them. Please don't change the permissions of your files or directories
unless you have a specific reason for doing so and you know what effect
it will have on your site.
My forms won't work through the Secure Server.
The call to a cgi script using the Secure Server
must not be within a webbot. Use a normal cgi call in your html script
for Secure Server calls.
My search bot doesn't return any results.
The /www directory must be world readable AND you need
to recalculate links BEFORE publishing (or after editing directly on the
server). If it still doesn't work: FTP to the server and go
to the /www/_vti_txt/default.wti directory. Delete any files
that begin with "ALL.". Don't delete any other files. Then
using Windows Explorer, do the same thing on your PC. Recalculate
links, test locally with your browser and publish.
FP starts the Web Publishing Wizard when I try
to publish.
Cancel the operation and contact support to have
the FP extensions installed/repaired.
Why is my page renamed on the server when I publish?
The "Default Document" of your web is automatically
renamed by the server to what is required by the configuration of the server.
For example, if you've named the main page "index.html", it may be renamed
"default.html". Just check the links to your
main page to make sure they refer to it the same way.
NOTE: If you are using FrontPage, you should
NEVER use regular FTP to upload your files. This will damage the extensions.
Stick with one or the other all the time.
Return
to Main Index
Go To Top of Page
|