FAQS

Home Sweet Home

FAQS

Welcome

News

Services/Prices

FAQs

Sample Admin

Resellers

Open Account

About Us

If you have a question that is not here, please send it to info@flic.net.

Q- What are your system specs?
A-	Due to our growth, our current system specs have recently been updated to accomodate more customers and heavier traffic: Our system comprises of scalable Pentium 200 MMX boxes. Each box has at least 128 Megs of RAM, powered by Linux 2.0.32 OS and Apache 1.2.4 web server. Important system files are being backed up once a day. The system is directly hooked up to a T3 network. We guarantee speedy connection and reserve the right to remove any account that causes an overall system slowdown.
Q- How do I change my password?
A-	By telneting to www.flic.net, log in as yourself, choose option one of the telnet menu, and follow the directions.
Q- Where is sendmail located on your system?
A-	/usr/sbin/sendmail
Q- How do I set up my POP3 information?
A-	The following information must be stored in the configuration area of your current email software program (e.g. Netscape Mail, Eudora, Microsoft Mail, etc.) POP Server = "mail.mydomain" SMTP Server = "mail.mydomain" User = "myid@mydomain" Password = "mypasswd"
Q- How Do I Upload Files Using FTP?
A-	Free ftp programs for Windows 95 and MacIntosh can be obtained by clicking on ws_ftp and Fetch, respectively. For ws_ftp, enter the following information after launching the application: Profile Name = "my name" Host Name = "ftp.mydomain" Host Type = "Automatic detect" User Id = "myid" Password = "mypasswd" Account = "" For Fetch, enter the following information after launching the application: Host = "ftp.mydomain" User Id = "myid" Password = "mypasswd" Directory = ""
Q- Do You Have a News Server?
A-	No.
Q- How do I control my email aliases (forward mechanism)?
A-	In your root html directory, there is the file ALIASES that contains pairs like <myid@mydomain myid@myISP> and <info@mydomain myid@myISP>. They tell the system to forward all emails destined for myid@mydomain and info@mydomain to myid@myISP. If you want emails destined for myid@mydomain to stay on mydomain, you need to remove the pair <myid@mydomain myid@myISP>. You can change, add, and delete the ALIASES file to your liking. Every night, our system gathers all the clients' ALIASES files and incorporate them into the system aliases.
Q- How do I keep emails on www.mydomain?
A-	Please read the answer to How do I control my email aliases? carefully.
Q- Where is perl located on your system?
A-	/usr/bin/perl
Q- Why doesn't Flicnet provide full telnet access?
A-	To prevent users from poking around the system's and other clients' resources (security, proprietary, and privacy reasons). We do provide partial telnet access to allow clients the ability to perform useful functions that cannot be done through FTP alone. These functions include change password, change protection mode, convert from DOS to Unix format, compile/run C/Java programs, and others. We might dedicate a telnet server for development purpose in the future.
Q- How do I use "form"?
A-	The script "FormMail.pl", provided in your cgi-bin directory, is designed to send all the <variable value> pairs inside your HTML form to an email address. You need to provide three hidden variables, 'recipient', 'subject', 'redirect', that corresponds to the email address, the subject of the message, and the URL of the response page returned to the user after having submitted the form. You should specify the method as "POST" and ACTION as "http://www.mydomain/cgi-bin/FormMail.pl" inside the FORM tag. Be sure to put the full path for the 'redirect' field since the cgi-bin is executed in your cgi directory path and not your html. Example: <FORM METHOD="POST" ACTION="http://www.mydomain.com/cgi-bin/FormMail.pl"> <INPUT TYPE="hidden" NAME="recipient" VALUE="info@mydomain.com"> <INPUT TYPE="hidden" NAME="subject" VALUE="This Appears in the email Subject"> <INPUT TYPE="hidden" NAME="redirect" VALUE="http://www.mydomain.com/FormResponse.html">
Q- How do I use text-based "counter.pl"?
A-	Counter is a method of displaying the number of times a page has been visited. The file "count.txt" in the root HTML directory contains the counter's current value and should be reset to zero. To display the counter in you index.html file, rename index.html to index.shtml and place the entry <!--#exec cgi="/cgi-bin/counter.pl"--> at the location where you want the counter to appear. The postfix .shtml will cause the server to run "counter.pl" before parsing the file again as an HTML file. This is also known as the Server Side Include (SSI) feature.
Q- How do I use graphics-based "Count.cgi"?
A-	Simply place <img src="/cgi-adm/Count.cgi?df=uid-cntn.dat" align=absmiddle> where you want the counter uid-cntn to be displayed. Click on digital counters for some examples.
Q- How do I use "guestbook.pl"?
A-	Guestbook is a form interface that allow visitors to leave comments about the page. There are two conventions of calling guestbook.pl. Open up the URL http://www.mydomain/cgi-bin/guestbook.pl?add will display a form for visitors to enter their thoughts. Open up URL http://www.mydomain/cgi-bin/guestbook.pl will display the content of the guestbook.
Q- How do I execute index.cgi when opening up http:/www.mydomain?
A-	To do this, utilize our web server's Server Side Include (SSI) feature. First, rename your index.html file to index.shtml. Next, place your index.cgi file inside your cgi-bin directory. Then, put the line <!--#exec cgi="/cgi-bin/index.cgi"--> inside the file index.shtml. This will cause the server to run the cgi and replace the line by the output that script generates before parsing everything as an HTML file. Our server is setup to look for "index.html", "index.htm", and "index.shtml" in that order as the default home page.
Q- How to make a page secure?
A-	Remember that it costs $5 per month to use our secure server. There are two ways of securing your page. Pay Thawte $125 per year to be your Certifying Authority. After Thawte had granted your request, replace the URL http://www.mydomain/securepage with https://www.mydomain/securepage. Pay us $10 to place a secure script in the directory https://www.flic.net/secure/myid, then reference it as https://www.flic.net/secure/myid/securescript. Our secure server only works smoothly with Netscape 3.0, IE 3.0, and the newer versions. These cover 95% of all the browsers in the market.
Q- What is so secure about using https?
A-	The https is subtle but very powerful. It redirects the page from port 80 (normal insucure server) to port 443 (secure server). By agreeing on the same SSL encryption protocol, Netscape, IE, and others (browser side) can send/receive encrypted data to/from our secure server. The secure server has a key (long sequence of random number) that must match the browser's. Now here is the tricky part. The browser obtains this key from Thawte. This key is also encrypted at Thawte. Because Netscape and IE understand Thawte, they know how to decrypt the key after they receive our encrypted key from Thawte. We also pay Thawte a yearly fee for this service.
Q- How do I read my traffic statistics?
A-	Our traffic statistics is graphics-based, written in java, and can only work with Netscape 3.0, IE 4.0 and newer versions. The traffic information is being updated on a nightly basis. The normal traffic report contains statistics graphs of the daily hits, daily volume, country hits, and html hits. The extended traffic report contains statistics of the daily volume, country volume, html volume, multimedia volume, domain volume, hourly volume, monthly volume, monthly hits, and daily hits. Open up the URL http://www.mydomain/Traffic to access your traffic statistics page.
Q- How do I set up additional password protected directories?
A-	By default, your /Admin page is password protected. We charge $10 for each additional password protected directory. Just send a request to info@flic.net with the subject "Add password protected directory /dir", where /dir is the name of the directory relative to the root /html directory. To control who can gain access into /dir and its subdirectories, create a file ".htpasswd" inside /dir that contains the list of allowable uid:passwd entries. Only those who enter a correct uid and password are allowed to enter. The list uid:passwd can be generated by telneting to www.mydomain, choose option 4, and follow the instructions.

Home Sweet Home