<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title><![CDATA[Bitstop Inc.]]></title>
<link><![CDATA[http://support.bitstop.ph/]]></link>
<description />
<generator><![CDATA[Kayako Fusion v4.53.2633]]></generator>
<item>
<title><![CDATA[Admin access blocked in Plesk because of IP restrictions]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/631]]></link>
<guid isPermaLink="false"><![CDATA[b7bb35b9c6ca2aee2df08cf09d7016c2]]></guid>
<pubDate><![CDATA[Sat, 05 Jan 2008 09:52:00 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA["Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied." 

Plesk IP access policy was configured in such a way that  Plesk cannot be accessed from the current IP. 

Login to m...]]></description>
<content:encoded><![CDATA["Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied." <br />
<br />
Plesk IP access policy was configured in such a way that  Plesk cannot be accessed from the current IP. <br />
<br />
Login to mysql using ssh:<br />
<br />
mysql> select * from cp_access;<br />
mysql> select * from misc where param='access_policy'; <br />
To clear the access policy settings remove all the records from the "cp_access" table and set policy to "allow": <br />
<br />
mysql> delete from cp_access where ID=1;<br />
mysql> update misc set val="allow" where param='access_policy'; After that, access to Plesk should be available.<br />
<br />
\q<br />
<br />
Source:  http://kb.swsoft.com/en/1024]]></content:encoded>
</item>
<item>
<title><![CDATA[DB WebAdmin for Plesk for Linux (202.91.163.60) cannot be accessed after upgrade...]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/580]]></link>
<guid isPermaLink="false"><![CDATA[069d3bb002acd8d7dd095917f9efe4cb]]></guid>
<pubDate><![CDATA[Sat, 17 Feb 2007 08:06:32 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[After upgrading from Plesk 7.5.4 to 8.0 version,  all the domains cannot get into their database using DB WebAdmin in the Plesk control panel. Whenever they click the DB WebAdmin icon, it says, 

#1045 - Access denied for user 'pma_dx349rmSH4Ji'@'localh...]]></description>
<content:encoded><![CDATA[After upgrading from Plesk 7.5.4 to 8.0 version,  all the domains cannot get into their database using DB WebAdmin in the Plesk control panel. Whenever they click the DB WebAdmin icon, it says, <br />
<br />
#1045 - Access denied for user 'pma_dx349rmSH4Ji'@'localhost' (using password: YES) <br />
<br />
# cd /usr/local/psa/admin/htdocs/domains/databases/phpMyAdmin/<br />
# vi config.inc.php<br />
<br />
<br />
I set the following settings:<br />
<br />
---------------------------------------------------------<br />
$cfg['Servers'][$i]['controluser'] = '';<br />
if ($db_host != 'localhost') $cfg['Servers'][1]['controluser'] = ''; <br />
<br />
$cfg['Servers'][$i]['controlpass'] = '';<br />
if ($db_host != 'localhost') $cfg['Servers'][1]['controluser'] = ''; <br />
<br />
$cfg['Servers'][$i]['auth_type'] = 'config'; <br />
$cfg['Servers'][$i]['user'] = "$db_user";<br />
$cfg['Servers'][$i]['password'] = "$db_pass"; <br />
$cfg['Servers'][$i]['only_db'] = "$db_name"; <br />
$cfg['Servers'][$i]['verbose'] = ''; <br />
$cfg['Servers'][$i]['pmadb'] = ''; <br />
---------------------------------------------------------<br />
<br />
Originally, i have the following values for the following:<br />
<br />
controluser       pma_dx349rmSH4Ji<br />
controlpass       dx349rmSH4Ji7<br />
pmadb             phpmyadmin_dx349rmSH4Ji <br />
<br />
I just set the values to nothing.<br />
<br />
http://forum.swsoft.com/showthread.php?s=&postid=167179#post167179<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[DNS problem with PLDT DSL]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/593]]></link>
<guid isPermaLink="false"><![CDATA[acc3e0404646c57502b480dc052c4fe1]]></guid>
<pubDate><![CDATA[Fri, 14 Dec 2007 07:35:27 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[If you are getting weird problems connecting to the web, and are using PLDT’s DSL service, we have a recommendation for you! Lately, we have been receiving reports from our hosted clients using PLDT internet connection that they cannot view websites.  Upo...]]></description>
<content:encoded><![CDATA[If you are getting weird problems connecting to the web, and are using PLDT’s DSL service, we have a recommendation for you! Lately, we have been receiving reports from our hosted clients using PLDT internet connection that they cannot view websites.  Upon investigation of the problem, we found out that there is a temporary problem with PLDT’s DNS servers.<br />
<br />
The details of our test show the following:<br />
<br />
1. When the client is using PLDT’s DNS server (from DSL),  the DNS query will fail.<br />
<br />
>www.m*********.com<br />
Server:  ns2.i-gate.net<br />
Address:  58.69.254.136<br />
<br />
*** ns2.i-gate.net can’t find www.m**********.com: Server failed<br />
2. When the client is using OPen DNS server, the DNS query returns a proper answer and succeed.<br />
<br />
> server 208.67.222.222<br />
>www.m*********.com<br />
<br />
Non-authoritative answer:<br />
Name:    www.m*********.com<br />
Address:  202.91.163.2<br />
<br />
We therefore recommend that you use OPENDNS when you are encountering problems that are related to PLDT DNS server. Here are the instructions on how to change DNS settings to OpenDNS (https://www.opendns.com/start).<br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Failed NT backup:]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/666]]></link>
<guid isPermaLink="false"><![CDATA[fae0b27c451c728867a567e8c1bb4e53]]></guid>
<pubDate><![CDATA[Wed, 15 Oct 2008 05:19:31 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[I failed running NT backup; it gave me the details on the backup.log:

------------------------------------------------------------------------------------
Backup Status
Operation: Backup
Active backup destination: File
Media name: "backupfilename.b...]]></description>
<content:encoded><![CDATA[I failed running NT backup; it gave me the details on the backup.log:<br />
<br />
------------------------------------------------------------------------------------<br />
Backup Status<br />
Operation: Backup<br />
Active backup destination: File<br />
Media name: "backupfilename.bkf created 10/15/2008 at 1:00 PM"<br />
<br />
Volume shadow copy creation: Attempt 1.<br />
<br />
Error returned while creating the volume shadow copy:0x8004230f.<br />
<br />
Error returned while creating the volume shadow copy:8004230f<br />
Aborting Backup.<br />
<br />
----------------------<br />
<br />
The operation did not successfully complete.<br />
<br />
----------------------<br />
------------------------------------------------------------------------------------------------<br />
<br />
This issue occurs because the VSS system files are not registered.<br />
<br />
<br />
SOLUTION:<br />
<br />
1. Type the following command at a command prompt. Press ENTER after you type the command. <br />
         regsvr32 /u swprv.dll <br />
<br />
2. Try to perform a backup operation. <br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Farm out agent can't log in to live2support]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/791]]></link>
<guid isPermaLink="false"><![CDATA[df7f28ac89ca37bf1abd2f6c184fe1cf]]></guid>
<pubDate><![CDATA[Tue, 13 Aug 2013 22:53:12 +0800]]></pubDate>
<dc:creator />
<description><![CDATA[Sir Wilson, asked us to do a tracert to&nbsp;199.59.163.142, from both Farmout and Bonuan NOC.
&nbsp;
If ever this happens again, please do an immediate tracert to the said IP, and forward the results to Sir Wilson.]]></description>
<content:encoded><![CDATA[<p>Sir Wilson, asked us to do a tracert to&nbsp;199.59.163.142, from both Farmout and Bonuan NOC.</p>
<p>&nbsp;</p>
<p>If ever this happens again, please do an immediate tracert to the said IP, and forward the results to Sir Wilson.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Flush emails in the mail queue ( qmail )]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/694]]></link>
<guid isPermaLink="false"><![CDATA[5487315b1286f907165907aa8fc96619]]></guid>
<pubDate><![CDATA[Tue, 14 Apr 2009 19:12:32 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[For those running their server as an email server, this can help. 

This will set the number of qmail-remote processes which can run 
at any given time. 

Qmail by default has no given setting but this will fix that. 
This will set the limit. You ca...]]></description>
<content:encoded><![CDATA[For those running their server as an email server, this can help. <br />
<br />
This will set the number of qmail-remote processes which can run <br />
at any given time. <br />
<br />
Qmail by default has no given setting but this will fix that. <br />
This will set the limit. You can modify this at any time later on <br />
if you wish to do so by running these commands again. <br />
<br />
Command line. <br />
su - <br />
<br />
For Plesk 6 & Earlier Plesk Versions. <br />
pico -w /var/qmail/control/concurrencyremote <br />
& Press <br />
<br />
For Plesk 7 <br />
nano /var/qmail/control/concurrencyremote <br />
<br />
At this point you should not see any number in this config. <br />
<br />
The higher the number you place here the more connections qmail <br />
will attempt at a given time. <br />
<br />
I suggest entering a value of 20 unless you send a lot of email. <br />
We run ours at 180 or better but we send 118,000 emails daily. <br />
At 180 , it will send these in about 3 hours or so. <br />
Note: it does take a lot of the system resources when set <br />
to a high number. <br />
<br />
Once you type in the number value , <br />
hold down Crtl and press o < this is a o - Not A Zero. <br />
<br />
Then press enter to write the config. line. <br />
<br />
Hold down Ctrl and press x to exit. <br />
<br />
Now restart qmail with the following comman. <br />
<br />
/sbin/service qmail restart <br />
<br />
That's all you do..]]></content:encoded>
</item>
<item>
<title><![CDATA[Getting EPP Code / Transfering Domain Ownership]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/577]]></link>
<guid isPermaLink="false"><![CDATA[fde9264cf376fffe2ee4ddf4a988880d]]></guid>
<pubDate><![CDATA[Fri, 22 Dec 2006 02:29:10 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[To transfer domain to another registrar, we must provide the new registrar, the EPP code.

To get the EPP code, (Extensible Provisioning Protocol), login to your account (i.e. in namecheap.com) and from your "Members Home" page, middle right, there will...]]></description>
<content:encoded><![CDATA[To transfer domain to another registrar, we must provide the new registrar, the EPP code.<br />
<br />
To get the EPP code, (Extensible Provisioning Protocol), login to your account (i.e. in namecheap.com) and from your "Members Home" page, middle right, there will be a "Get your EPP code" here link, go ahead and click on it and you will then be able to retrieve your code.<br />
<br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Horde Error in adding contacts]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/583]]></link>
<guid isPermaLink="false"><![CDATA[9ad6aaed513b73148b7d49f70afcfb32]]></guid>
<pubDate><![CDATA[Thu, 26 Apr 2007 02:55:16 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[Hosting accounts in Plesk for Linux (202.91.163.60) has been experiencing an error while adding new contacts in their Horde Webmail.  The error shows below:

      A fatal error has occurred
      You must configure a VFS backend.
      Details have b...]]></description>
<content:encoded><![CDATA[Hosting accounts in Plesk for Linux (202.91.163.60) has been experiencing an error while adding new contacts in their Horde Webmail.  The error shows below:<br />
<br />
      A fatal error has occurred<br />
      You must configure a VFS backend.<br />
      Details have been logged for the administrator.<br />
<br />
<br />
It has been fixed by adding the following line into the server's conf.php file (/usr/share/psa-horde/config/conf.php):<br />
<br />
                  $conf['documents']['type'] = 'horde';<br />
<br />
---------------------------------------------------------------------------------------------------------------------------------------<br />
Please note that conf.php is set to read-only so I  chmoded the file to 777, apply the fix and chmoded back to 644.<br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Host Headers]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/570]]></link>
<guid isPermaLink="false"><![CDATA[a86c450b76fb8c371afead6410d55534]]></guid>
<pubDate><![CDATA[Wed, 23 Aug 2006 01:59:02 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[We have a client with an existing website hosted in another location. He has uploaded the files to our webserver. He now wants to test the domain. However, since the domain is still pointed to the old location, we decided to create a dns to point to the h...]]></description>
<content:encoded><![CDATA[We have a client with an existing website hosted in another location. He has uploaded the files to our webserver. He now wants to test the domain. However, since the domain is still pointed to the old location, we decided to create a dns to point to the hosted materials.<br />
<br />
For example:<br />
<br />
Actual domain is www.company.com (resolves to 202.91.163.60) <br />
Test dns is test.abccompany.com (resolves to 202.91.163.60)<br />
<br />
How do we map host headers so that OUR webserver will accept request for test.abccompany.com as well?<br />
<br />
As per source, http://forums.digitalpoint.com/showthread.php?p=211071<br />
<br />
I've taken the following steps: <br />
<br />
On Master.dagupan.com<br />
<br />
I created an A record to point domain.bitstop.ph to the IP address of the webserver (for example: funchain.bitstop.ph resolves to<br />
202.91.163.60)<br />
 <br />
Log in via SSH to 202.91.163.60 and create a file at /home/httpd/vhosts/mydomain.com/conf/vhost.conf<br />
(using vi vhost.conf)<br />
and it contains the following text, nothing more: <br />
ServerAlias  www.funchain.com<br />
ServerAlias funchain.bitstop.ph<br />
<br />
[esc] :x (to save)<br />
<br />
On the command prompt:<br />
 /usr/local/psa/admin/bin/websrvmng -a -v<br />
<br />
I rebooted the machine via the command:<br />
Shutdown -r now<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[How do I access the control panel for my domain?]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/55]]></link>
<guid isPermaLink="false"><![CDATA[b53b3a3d6ab90ce0268229151c9bde11]]></guid>
<pubDate><![CDATA[Tue, 21 Mar 2006 07:35:54 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[The URL for your control panel can be reached at https://your-domain.com:8443. ]]></description>
<content:encoded><![CDATA[The URL for your control panel can be reached at https://your-domain.com:8443. ]]></content:encoded>
</item>
<item>
<title><![CDATA[How to install Native Adapters in Linux VPS in HyperV]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/787]]></link>
<guid isPermaLink="false"><![CDATA[3621f1454cacf995530ea53652ddf8fb]]></guid>
<pubDate><![CDATA[Fri, 28 Jun 2013 11:00:21 +0800]]></pubDate>
<dc:creator />
<description><![CDATA[Using Native Adapters with LINUX VPS in HyperV environments. This is the steps how to install right the centos6.3 or latest OS and how to up it in the internet. because di na sia gaya ng dati na basta install na lang.&nbsp;Create new VHD w/ Legacy Network...]]></description>
<content:encoded><![CDATA[<p>Using Native Adapters with LINUX VPS in HyperV environments.<br /> <br />This is the steps how to install right the centos6.3 or latest OS and how to up it in the internet. because di na sia gaya ng dati na basta install na lang.&nbsp;<br />Create new VHD w/ Legacy Network Adapter for CentOS 6.3 (make sure that yor provisioned it in a legacy because the default is native network)<br />Download CentOS 6.3-minimal.iso (insert disk &amp; install)</p>
<p><br />Download LinuxICv34.iso (insert disk) (you can do this by ALT+F1, for you to access it to the console)</p>
<p>mkdir -p /mnt/cdrom</p>
<p>mount /dev/cdrom /mnt/cdrom</p>
<p>cp -rp /mnt/cdrom /opt/linux_ic</p>
<p>umount /mnt/cdrom</p>
<p>cd /opt/linux_ic/RHEL63</p>
<p>./install.sh</p>
<p>&nbsp;</p>
<p>Once the install is done, shutdown the VPS, note the mac address and then remove the legacy adapter.<br />Add a standard network adapter with static mac that you've previously noted. Apply and start the VPS</p>
<p>Update your network settings via interface.</p>
<p>Then restart via command the network service:/etc/init.d/network restart</p>
<p>--cristina</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[How to show filename extensions in sharepoint]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/579]]></link>
<guid isPermaLink="false"><![CDATA[258be18e31c8188555c2ff05b4d542c3]]></guid>
<pubDate><![CDATA[Sat, 10 Feb 2007 03:57:25 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[How to show filename extensions in sharepoint:
 
from:
http://groups.google.com.ph/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/3b076f9acfbbb629/028e5ab66e8fccf5?lnk=st&q=how+to+show+file+extensions+in+sharepoint+document+library...]]></description>
<content:encoded><![CDATA[How to show filename extensions in sharepoint:<br />
 <br />
from:<br />
http://groups.google.com.ph/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/3b076f9acfbbb629/028e5ab66e8fccf5?lnk=st&q=how+to+show+file+extensions+in+sharepoint+document+library&rnum=2&hl=tl#028e5ab66e8fccf5<br />
 <br />
<br />
<HTML><![CDATA[.]]></HTML><Field HTMLEncode="FALSE" Name="File_x0020_Type"/><br />
 <br />
<br />
There are 2 ways to show file extensions in a SharePoint document <br />
library: <br />
 <br />
Convert the document library ListViewWebPart to a XSLT dataview - Open <br />
the document library with FrontPage, right click and convert to <br />
DataView. Modify the XSLT to add <xsl:value-of <br />
select="@File_x0020_Type"/> <br />
 <br />
<br />
Modify the display pattern in ONET.XML - add <br />
<HTML><![CDATA[.]]></HTML><Field HTMLEncode="FALSE" <br />
Name="File_x0020_Type"/> before <HTML><![CDATA[</A>]]></HTML><IfNew <br />
Name="Created_x0020_Date"> . After making a change to ONET.XML you have <br />
to do IISRESET. <br />
 <br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[I can't view the control panel, all I get is a blank page with nothing on it!?]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/65]]></link>
<guid isPermaLink="false"><![CDATA[fc490ca45c00b1249bbe3554a4fdf6fb]]></guid>
<pubDate><![CDATA[Tue, 21 Mar 2006 07:43:13 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[There are two possible causes for this problem. First is if you are using a firewall on your computer that has port 8443 blocked. You will need to adjust your firewall to open port 8443. Second is if you are using a Mac computer with OS9 and running Micro...]]></description>
<content:encoded><![CDATA[There are two possible causes for this problem. First is if you are using a firewall on your computer that has port 8443 blocked. You will need to adjust your firewall to open port 8443. Second is if you are using a Mac computer with OS9 and running Microsoft's Internet Explorer. There is a glitch in the combination of OS9 and IE that it simply will not work. You will need to upgrade your OS or change web browsers.]]></content:encoded>
</item>
<item>
<title><![CDATA[Problem on Accessing Database]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/645]]></link>
<guid isPermaLink="false"><![CDATA[5e9f92a01c986bafcabbafd145520b13]]></guid>
<pubDate><![CDATA[Wed, 28 May 2008 03:19:51 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[Problem :  cant access database of bobbysy from reina's database.

Possible Cause: Problem on permission 

Escalation: Sir wilson ask for the code of the connection string and found out that its not a problem on permission but 
            a problem ...]]></description>
<content:encoded><![CDATA[Problem :  cant access database of bobbysy from reina's database.<br />
<br />
Possible Cause: Problem on permission <br />
<br />
Escalation: Sir wilson ask for the code of the connection string and found out that its not a problem on permission but <br />
            a problem on the code. The code has a wrong username.]]></content:encoded>
</item>
<item>
<title><![CDATA[Transfering SSL Certificate from one server to another]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/649]]></link>
<guid isPermaLink="false"><![CDATA[55b37c5c270e5d84c793e486d798c01d]]></guid>
<pubDate><![CDATA[Fri, 04 Jul 2008 05:13:01 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[To transfer an existing SSL certificate from one server to another (same domain name), follow these steps.

A. Backup the SSL Certificate
    1. Go to IIS and right click the domain which has the SSL certificate. 
    2. Click Properties and go to Dir...]]></description>
<content:encoded><![CDATA[To transfer an existing SSL certificate from one server to another (same domain name), follow these steps.<br />
<br />
A. Backup the SSL Certificate<br />
    1. Go to IIS and right click the domain which has the SSL certificate. <br />
    2. Click Properties and go to Directory Security tab. Under Server Communications, click Server Certificate button.<br />
    3. The Webserver Certificate wizard appears. Click next.<br />
    4. Choose Export the current certificate to a .pfx file. Click next.<br />
    5. Enter the path and filename to export the certificate to. Click next.<br />
    6. Type a password to encrypt the exported .pfx file. Click next.<br />
    7. You should see a summary of screen showing what the wizard is about to do. If this information is correct, click Finish.<br />
    <br />
Copy the .pfx file somewhere in the new server.<br />
<br />
B. Restoring the SSL Certificate<br />
    1. Open IIS and navigate to same domain you want to restore the SSL to. <br />
    2. Click Properties and go to Directory Security tab. Under Server Communications, click Server Certificate button.<br />
    3. The Webserver Certificate wizard appears. Click next.<br />
    4. Choose Import a certificate from a .pfx file. Click next. <br />
    5. Browse in the location of your SSL certificate that you copied from the old server. Click next.<br />
    6. Type the password you use to encrypt the .pfx file. Click next.<br />
    7. You will now see a summary screen showing you the same details about the certificate you are installing from the old server.<br />
    9. Click Next, and then click OK to exit the wizard. <br />
<br />
Note: Be sure to enable Secure Webserver (HTTPS) in the LAN settings under services.<br />
<br />
For a complete guide, you can refer to: http://support.microsoft.com/?id=232137 ]]></content:encoded>
</item>
<item>
<title><![CDATA[URL not found error]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/698]]></link>
<guid isPermaLink="false"><![CDATA[99bcfcd754a98ce89cb86f73acc04645]]></guid>
<pubDate><![CDATA[Mon, 06 Jul 2009 18:11:30 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[URL was not found when a picture in the gallery is clicked. This is a wordpress blog.

Since the blog is using custom permalinks, we need to create .htaccess file with the following contents:


RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_F...]]></description>
<content:encoded><![CDATA[URL was not found when a picture in the gallery is clicked. This is a wordpress blog.<br />
<br />
Since the blog is using custom permalinks, we need to create .htaccess file with the following contents:<br />
<br />
<IfModule mod_rewrite.c><br />
RewriteEngine On<br />
RewriteBase /<br />
RewriteCond %{REQUEST_FILENAME} !-f<br />
RewriteCond %{REQUEST_FILENAME} !-d<br />
RewriteRule . /index.php [L]<br />
</IfModule><br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Web Statistics Guide]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/573]]></link>
<guid isPermaLink="false"><![CDATA[e5f6ad6ce374177eef023bf5d0c018b6]]></guid>
<pubDate><![CDATA[Fri, 01 Sep 2006 04:02:50 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[Webalizer Quick Help

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...]]></description>
<content:encoded><![CDATA[Webalizer Quick Help<br />
<br />
Main Headings<br />
<br />
Hits represent the total number of requests made to the server during the given time period (month, day, hour etc..).<br />
<br />
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.<br />
<br />
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).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
Common Definitions<br />
A Site is a remote machine that makes requests to your server, and is based on the remote machines IP Address/Hostname.<br />
<br />
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...).<br />
<br />
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.<br />
<br />
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.<br />
<br />
Note: Only available if that information is contained in the server logs.<br />
<br />
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.<br />
<br />
Note: Only available if that information is contained in the server logs.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[What are the DNS servers my domain needs to point to?]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/35]]></link>
<guid isPermaLink="false"><![CDATA[1c383cd30b7c298ab50293adfecb7b18]]></guid>
<pubDate><![CDATA[Tue, 21 Mar 2006 07:00:36 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[There are two platforms BNSHosting offers:
For  Linux platform 
        - Primary DNS name : ns4.bnshosting.net
                        DNS IP      : 202.91.163.31
        - Secondary DNS name: ns2.bnshosting.net
                           DNS IP    ...]]></description>
<content:encoded><![CDATA[There are two platforms BNSHosting offers:<br />
For  Linux platform <br />
        - Primary DNS name : ns4.bnshosting.net<br />
                        DNS IP      : 202.91.163.31<br />
        - Secondary DNS name: ns2.bnshosting.net<br />
                           DNS IP     : 202.91.161.246<br />
<br />
OR <br />
       - Primary DNS name: ns1.yourdomain.tld<br />
                       DNS IP     : 202.91.163.60<br />
       -Secondary DNS name: ns2.bnshosting.net<br />
                          DNS IP     : 202.91.161.246<br />
<br />
For Windows Platform<br />
       - Primary DNS name : ns3.bnshosting.net<br />
                       DNS IP      : 202.91.163.2<br />
       - Secondary DNS name: ns2.bnshosting.net<br />
                           DNS IP : 202.91.161.246]]></content:encoded>
</item>
<item>
<title><![CDATA[When I transfer my domain (change the DNS records) pointing to your server how l...]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/37]]></link>
<guid isPermaLink="false"><![CDATA[a5bfc9e07964f8dddeb95fc584cd965d]]></guid>
<pubDate><![CDATA[Tue, 21 Mar 2006 07:12:21 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[It depends on how fast it is resolved. Usually about 12 hours, but sometimes up to 24.]]></description>
<content:encoded><![CDATA[It depends on how fast it is resolved. Usually about 12 hours, but sometimes up to 24.]]></content:encoded>
</item>
<item>
<title><![CDATA[Wordpress Error : #1062 - Duplicate entry '2182' for key 1]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/574]]></link>
<guid isPermaLink="false"><![CDATA[f0e52b27a7a5d6a1a87373dffa53dbe5]]></guid>
<pubDate><![CDATA[Thu, 14 Sep 2006 03:55:50 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[We have solved an error in Wordpress blog.  If we try to insert or post a comment, i.e. infochat.com.ph's blogsite, we got this error:

#1062 - Duplicate entry '2182' for key 1 


Google search produces:

http://wordpress.org/support/topic/72981
...]]></description>
<content:encoded><![CDATA[We have solved an error in Wordpress blog.  If we try to insert or post a comment, i.e. infochat.com.ph's blogsite, we got this error:<br />
<br />
#1062 - Duplicate entry '2182' for key 1 <br />
<br />
<br />
Google search produces:<br />
<br />
http://wordpress.org/support/topic/72981<br />
<br />
<br />
Solution: Edit the wp_comments table, delete the zero in the default field.<br />
<br />
"Only variation was that I had a 0 (zero) in each "default" field.<br />
Be sure to remove the 0 (zero) before saving or you will get a MySQL error message."<br />
<br />
Wordpress blog. Mysql 4.0.20<br />
]]></content:encoded>
</item>
<item>
<title><![CDATA[Wordpress Problem regarding Plugins]]></title>
<link><![CDATA[http://support.bitstop.ph/index.php?/Knowledgebase/Article/View/670]]></link>
<guid isPermaLink="false"><![CDATA[17c276c8e723eb46aef576537e9d56d0]]></guid>
<pubDate><![CDATA[Mon, 10 Nov 2008 02:59:55 +0800]]></pubDate>
<dc:creator><![CDATA[- NA -]]></dc:creator>
<description><![CDATA[The error is:
Fatal error: Cannot redeclare get_the_terms() (previously declared in /home/www/design/wp-includes/category-template.php:489) in /home/www/design/wp-content/plugins/sem-extract-terms/sem-extract-terms.php on line 237

Here is what we did:...]]></description>
<content:encoded><![CDATA[The error is:<br />
Fatal error: Cannot redeclare get_the_terms() (previously declared in /home/www/design/wp-includes/category-template.php:489) in /home/www/design/wp-content/plugins/sem-extract-terms/sem-extract-terms.php on line 237<br />
<br />
Here is what we did:<br />
Upon analyzing the problem, which has something to do with plugins, and since we can no longer login to wordpress panel, we SSH to the server, <br />
<br />
202.91.163.26 and looked at the contents of the lines of the following files:<br />
<br />
----------------------------------------------------------------------------------------<br />
/home/www/design/wp-includes/category-template.php:489<br />
/home/www/design/wp-content/plugins/sem-extract-terms/sem-extract-terms.php on line 237<br />
----------------------------------------------------------------------------------------<br />
<br />
Both of these files has the same "get_the_terms()" function which is believed to conflict the system. Since the error includes: "(previously declared in <br />
<br />
/home/www/design/wp-includes/category-template.php", we commented out the get_the_terms function defined in the file, <br />
<br />
/home/www/design/wp-content/plugins/sem-extract-terms/sem-extract-terms.php on line 237.<br />
<br />
Upon saving the changes, the site went back to its running state and we can also login to the wordpress control panel. There we noticed that the plugin, <br />
<br />
Semiologin CMS was enabled, which explained that the "get_the_terms" function was redeclared, thus the error.]]></content:encoded>
</item>
</channel>
</rss>