Hostek.com Wiki - User contributions [en]

LiteSpeed Cache (LSCache)

2017-09-26T21:00:47Z

DanielleM: /* Installation on a Shared cPanel/Linux Server */

==Summary==

LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages, LSCache works hand-in-hand with LiteSpeed to create an even more efficient and fast environment for your website.

==LiteSpeed Cache for WordPress (LSCWP)==

LiteSpeed Cache for WordPress is a highly customizable web server-level caching plugin that utilizes LiteSpeed Cache. It is designed to dramatically increase WordPress site speed with little to no configuration necessary. As mentioned earlier, by caching at the web server layer, overhead is cut drastically allowing caching to be done more quickly and efficiently than in any other caching solution.

===Installation on a Shared cPanel/Linux Server===

If you are on a shared cPanel/Linux server and have been directed to this page via e-mail, you are part of our beta LSCWP program! We strongly encourage you to take advantage of this free speed-boosting plugin. To do so, please perform the following steps:

#Log into your WordPress website.
#Click 'Plugins' on the left. [[File:LSCache1r.png]]
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only WordPress caching plugin enabled. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that. [[File:LSCache2.png]]
#Click the 'DB Optimizer' tab on the new page. [[File:LSCache3.png]]
#Click the 'Clean All' button. After that, click 'Optimize Tables' button. [[File:LSCache4.png]]
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

===Installation on a VPS===

''Note: This section is for clients whom have purchased their own private server. If your website is on a Hostek.com shared server, please read the section above.''

As a prerequisite, your server must have LiteSpeed with LSCache. To get this speed-boosting upgrade, [https://support.hostek.com/ please contact Hostek.com support by clicking here] and mention this wiki page.

#Login into WHM for your server (http://<Your Server's IP>:2086/).
#At the top-left, type in 'LiteSpeed'. There should be one result (LiteSpeed Web Server), click it.
#Under 'LiteSpeed Cache for WordPress Management', click 'Manage Cache Installations'.
#In this section, click 'scan'. LiteSpeed will now scan for all of the WordPress sites on the server.
#Once the scan is finished, go back to the 'Manage Cache Installations' page.
#Simply check the box on the left for the websites(s) you want to enable LiteSpeed Cache for, then scroll back up and click 'Enable Selected'. This will install the LiteSpeed WordPress plugin and connect configs on the LiteSpeed back-end for the sites you chose.
#Next, log into the site's WordPress admin, then go to Plugins.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

=== Frequently Asked Questions ===

'''"Why is LSCWP faster than other caching plugins?"'''

Unlike most other caching plugins, LSCache works by caching pages on a server-level. It can do this because it has access to LiteSpeed, and through that the server as a whole. The first time a page loads it may load at normal rates, for that's the time it is getting placed into the server cache. After that, it will load almost instantly for everyone, as it is pulled from the server cache instead of the web server. Normal caching plugins work by caching pages on a client/browser level, which is much less efficient, as every person browsing the site will have to load the pages themselves before they are cached on their local machine instead of the server.

'''"If a page is changed, will the changed be cached again automatically?"'''

LSCache comes with what is called a '''crawler''' that checks each page of your website for changes. When it detects that a cached page is changed, it will re-cache the page automatically. It does this every 400 seconds, so changes you make will indeed quickly be cached once more. You can modify this 400-second value as well as a plethora of other technical features by going to Plugins -> LiteSpeed Cache -> Settings. There are many tabs of configuration variables you and your developers can modify at that location. This is not to say you need to-- LSCWP comes out-of-the-box with all settings configured at optimal values for most websites.

'''"Is there a way to force a page to re-cache?"'''

To 'force-reload' a page into the cache, all it will take is simply loading the page once through the browser. LSCache will detect that it hasn't been cached before (or if a different version of it was cached) and it will automatically update. The aforementioned crawler will also do this every 400 seconds.

If you have a question that is not listed here, [https://support.hostek.com/ please feel free to contact Hostek.com support by clicking here.]

LiteSpeed Cache (LSCache)

2017-09-26T20:59:21Z

DanielleM: /* Installation on a Shared cPanel/Linux Server */

==Summary==

LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages, LSCache works hand-in-hand with LiteSpeed to create an even more efficient and fast environment for your website.

==LiteSpeed Cache for WordPress (LSCWP)==

LiteSpeed Cache for WordPress is a highly customizable web server-level caching plugin that utilizes LiteSpeed Cache. It is designed to dramatically increase WordPress site speed with little to no configuration necessary. As mentioned earlier, by caching at the web server layer, overhead is cut drastically allowing caching to be done more quickly and efficiently than in any other caching solution.

===Installation on a Shared cPanel/Linux Server===

If you are on a shared cPanel/Linux server and have been directed to this page via e-mail, you are part of our beta LSCWP program! We strongly encourage you to take advantage of this free speed-boosting plugin. To do so, please perform the following steps:

#Log into your WordPress website.
#Click 'Plugins' on the left.
#*[[File:LSCache1r.png]]
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only WordPress caching plugin enabled. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#*[[File:LSCache2.png]]
#Click the 'DB Optimizer' tab on the new page.
#*[[File:LSCache3.png]]
#Click the 'Clean All' button. After that, click 'Optimize Tables' button.
#*[[File:LSCache4.png]]
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

===Installation on a VPS===

''Note: This section is for clients whom have purchased their own private server. If your website is on a Hostek.com shared server, please read the section above.''

As a prerequisite, your server must have LiteSpeed with LSCache. To get this speed-boosting upgrade, [https://support.hostek.com/ please contact Hostek.com support by clicking here] and mention this wiki page.

#Login into WHM for your server (http://<Your Server's IP>:2086/).
#At the top-left, type in 'LiteSpeed'. There should be one result (LiteSpeed Web Server), click it.
#Under 'LiteSpeed Cache for WordPress Management', click 'Manage Cache Installations'.
#In this section, click 'scan'. LiteSpeed will now scan for all of the WordPress sites on the server.
#Once the scan is finished, go back to the 'Manage Cache Installations' page.
#Simply check the box on the left for the websites(s) you want to enable LiteSpeed Cache for, then scroll back up and click 'Enable Selected'. This will install the LiteSpeed WordPress plugin and connect configs on the LiteSpeed back-end for the sites you chose.
#Next, log into the site's WordPress admin, then go to Plugins.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

=== Frequently Asked Questions ===

'''"Why is LSCWP faster than other caching plugins?"'''

Unlike most other caching plugins, LSCache works by caching pages on a server-level. It can do this because it has access to LiteSpeed, and through that the server as a whole. The first time a page loads it may load at normal rates, for that's the time it is getting placed into the server cache. After that, it will load almost instantly for everyone, as it is pulled from the server cache instead of the web server. Normal caching plugins work by caching pages on a client/browser level, which is much less efficient, as every person browsing the site will have to load the pages themselves before they are cached on their local machine instead of the server.

'''"If a page is changed, will the changed be cached again automatically?"'''

LSCache comes with what is called a '''crawler''' that checks each page of your website for changes. When it detects that a cached page is changed, it will re-cache the page automatically. It does this every 400 seconds, so changes you make will indeed quickly be cached once more. You can modify this 400-second value as well as a plethora of other technical features by going to Plugins -> LiteSpeed Cache -> Settings. There are many tabs of configuration variables you and your developers can modify at that location. This is not to say you need to-- LSCWP comes out-of-the-box with all settings configured at optimal values for most websites.

'''"Is there a way to force a page to re-cache?"'''

To 'force-reload' a page into the cache, all it will take is simply loading the page once through the browser. LSCache will detect that it hasn't been cached before (or if a different version of it was cached) and it will automatically update. The aforementioned crawler will also do this every 400 seconds.

If you have a question that is not listed here, [https://support.hostek.com/ please feel free to contact Hostek.com support by clicking here.]

File:LSCache1r.png

2017-09-26T20:57:39Z

DanielleM:

File:LSCache4.png

2017-09-26T20:55:18Z

DanielleM:

File:LSCache3.png

2017-09-26T20:55:08Z

DanielleM:

File:LSCache2.png

2017-09-26T20:54:58Z

DanielleM:

File:LSCache1.png

2017-09-26T20:54:40Z

DanielleM:

LiteSpeed Cache (LSCache)

2017-09-26T20:47:47Z

DanielleM: /* Installation on a Shared cPanel/Linux Server */

==Summary==

LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages, LSCache works hand-in-hand with LiteSpeed to create an even more efficient and fast environment for your website.

==LiteSpeed Cache for WordPress (LSCWP)==

LiteSpeed Cache for WordPress is a highly customizable web server-level caching plugin that utilizes LiteSpeed Cache. It is designed to dramatically increase WordPress site speed with little to no configuration necessary. As mentioned earlier, by caching at the web server layer, overhead is cut drastically allowing caching to be done more quickly and efficiently than in any other caching solution.

===Installation on a Shared cPanel/Linux Server===

If you are on a shared cPanel/Linux server and have been directed to this page via e-mail, you are part of our beta LSCWP program! We strongly encourage you to take advantage of this free speed-boosting plugin. To do so, please perform the following steps:

#Log into your WordPress website.
#Click 'Plugins' on the left.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only WordPress caching plugin enabled. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

===Installation on a VPS===

''Note: This section is for clients whom have purchased their own private server. If your website is on a Hostek.com shared server, please read the section above.''

As a prerequisite, your server must have LiteSpeed with LSCache. To get this speed-boosting upgrade, [https://support.hostek.com/ please contact Hostek.com support by clicking here] and mention this wiki page.

#Login into WHM for your server (http://<Your Server's IP>:2086/).
#At the top-left, type in 'LiteSpeed'. There should be one result (LiteSpeed Web Server), click it.
#Under 'LiteSpeed Cache for WordPress Management', click 'Manage Cache Installations'.
#In this section, click 'scan'. LiteSpeed will now scan for all of the WordPress sites on the server.
#Once the scan is finished, go back to the 'Manage Cache Installations' page.
#Simply check the box on the left for the websites(s) you want to enable LiteSpeed Cache for, then scroll back up and click 'Enable Selected'. This will install the LiteSpeed WordPress plugin and connect configs on the LiteSpeed back-end for the sites you chose.
#Next, log into the site's WordPress admin, then go to Plugins.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

=== Frequently Asked Questions ===

'''"Why is LSCWP faster than other caching plugins?"'''

Unlike most other caching plugins, LSCache works by caching pages on a server-level. It can do this because it has access to LiteSpeed, and through that the server as a whole. The first time a page loads it may load at normal rates, for that's the time it is getting placed into the server cache. After that, it will load almost instantly for everyone, as it is pulled from the server cache instead of the web server. Normal caching plugins work by caching pages on a client/browser level, which is much less efficient, as every person browsing the site will have to load the pages themselves before they are cached on their local machine instead of the server.

'''"If a page is changed, will the changed be cached again automatically?"'''

LSCache comes with what is called a '''crawler''' that checks each page of your website for changes. When it detects that a cached page is changed, it will re-cache the page automatically. It does this every 400 seconds, so changes you make will indeed quickly be cached once more. You can modify this 400-second value as well as a plethora of other technical features by going to Plugins -> LiteSpeed Cache -> Settings. There are many tabs of configuration variables you and your developers can modify at that location. This is not to say you need to-- LSCWP comes out-of-the-box with all settings configured at optimal values for most websites.

'''"Is there a way to force a page to re-cache?"'''

To 'force-reload' a page into the cache, all it will take is simply loading the page once through the browser. LSCache will detect that it hasn't been cached before (or if a different version of it was cached) and it will automatically update. The aforementioned crawler will also do this every 400 seconds.

If you have a question that is not listed here, [https://support.hostek.com/ please feel free to contact Hostek.com support by clicking here.]

LiteSpeed Cache (LSCache)

2017-09-15T17:18:26Z

DanielleM: /* Installation on a VPS */

==Summary==

LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages, LSCache works hand-in-hand with LiteSpeed to create an even more efficient and fast environment for your website.

==LiteSpeed Cache for WordPress (LSCWP)==

LiteSpeed Cache for WordPress is a highly customizable web server-level caching plugin that utilizes LiteSpeed Cache. It is designed to dramatically increase WordPress site speed with little to no configuration necessary. As mentioned earlier, by caching at the web server layer, overhead is cut drastically allowing caching to be done more quickly and efficiently than in any other caching solution.

===Installation on a Shared cPanel/Linux Server===

If you are on a shared cPanel/Linux server and have been directed to this page via e-mail, you are part of our beta LSCWP program! We strongly encourage you to take advantage of this free speed-boosting plugin. To do so, please perform the following steps:

#Log into your WordPress website.
#Click 'Plugins' on the left.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

===Installation on a VPS===

''Note: This section is for clients whom have purchased their own private server. If your website is on a Hostek.com shared server, please read the section above.''

As a prerequisite, your server must have LiteSpeed with LSCache. To get this speed-boosting upgrade, [https://support.hostek.com/ please contact Hostek.com support by clicking here] and mention this wiki page.

#Login into WHM for your server (http://<Your Server's IP>:2086/).
#At the top-left, type in 'LiteSpeed'. There should be one result (LiteSpeed Web Server), click it.
#Under 'LiteSpeed Cache for WordPress Management', click 'Manage Cache Installations'.
#In this section, click 'scan'. LiteSpeed will now scan for all of the WordPress sites on the server.
#Once the scan is finished, go back to the 'Manage Cache Installations' page.
#Simply check the box on the left for the websites(s) you want to enable LiteSpeed Cache for, then scroll back up and click 'Enable Selected'. This will install the LiteSpeed WordPress plugin and connect configs on the LiteSpeed back-end for the sites you chose.
#Next, log into the site's WordPress admin, then go to Plugins.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

=== Frequently Asked Questions ===

'''"Why is LSCWP faster than other caching plugins?"'''

Unlike most other caching plugins, LSCache works by caching pages on a server-level. It can do this because it has access to LiteSpeed, and through that the server as a whole. The first time a page loads it may load at normal rates, for that's the time it is getting placed into the server cache. After that, it will load almost instantly for everyone, as it is pulled from the server cache instead of the web server. Normal caching plugins work by caching pages on a client/browser level, which is much less efficient, as every person browsing the site will have to load the pages themselves before they are cached on their local machine instead of the server.

'''"If a page is changed, will the changed be cached again automatically?"'''

LSCache comes with what is called a '''crawler''' that checks each page of your website for changes. When it detects that a cached page is changed, it will re-cache the page automatically. It does this every 400 seconds, so changes you make will indeed quickly be cached once more. You can modify this 400-second value as well as a plethora of other technical features by going to Plugins -> LiteSpeed Cache -> Settings. There are many tabs of configuration variables you and your developers can modify at that location. This is not to say you need to-- LSCWP comes out-of-the-box with all settings configured at optimal values for most websites.

'''"Is there a way to force a page to re-cache?"'''

To 'force-reload' a page into the cache, all it will take is simply loading the page once through the browser. LSCache will detect that it hasn't been cached before (or if a different version of it was cached) and it will automatically update. The aforementioned crawler will also do this every 400 seconds.

If you have a question that is not listed here, [https://support.hostek.com/ please feel free to contact Hostek.com support by clicking here.]

LiteSpeed Cache (LSCache)

2017-09-15T16:36:21Z

DanielleM: Created page with "==Summary== LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages,..."

==Summary==

LiteSpeed Cache (LSCache) is a server-level caching solution offered by an alternative to Apache called LiteSpeed. While LiteSpeed itself offers many advantages, LSCache works hand-in-hand with LiteSpeed to create an even more efficient and fast environment for your website.

==LiteSpeed Cache for WordPress (LSCWP)==

LiteSpeed Cache for WordPress is a highly customizable web server-level caching plugin that utilizes LiteSpeed Cache. It is designed to dramatically increase WordPress site speed with little to no configuration necessary. As mentioned earlier, by caching at the web server layer, overhead is cut drastically allowing caching to be done more quickly and efficiently than in any other caching solution.

===Installation on a Shared cPanel/Linux Server===

If you are on a shared cPanel/Linux server and have been directed to this page via e-mail, you are part of our beta LSCWP program! We strongly encourage you to take advantage of this free speed-boosting plugin. To do so, please perform the following steps:

#Log into your WordPress website.
#Click 'Plugins' on the left.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

===Installation on a VPS===

As a prerequisite, your server must have LiteSpeed with LSCache. To get this speed-boosting upgrade, [https://support.hostek.com/ please contact Hostek.com support by clicking here] and mention this wiki page.

#Login into WHM for your server (http://<Your Server's IP>:2086/).
#At the top-left, type in 'LiteSpeed'. There should be one result (LiteSpeed Web Server), click it.
#Under 'LiteSpeed Cache for WordPress Management', click 'Manage Cache Installations'.
#In this section, click 'scan'. LiteSpeed will now scan for all of the WordPress sites on the server.
#Once the scan is finished, go back to the 'Manage Cache Installations' page.
#Simply check the box on the left for the websites(s) you want to enable LiteSpeed Cache for, then scroll back up and click 'Enable Selected'. This will install the LiteSpeed WordPress plugin and connect configs on the LiteSpeed back-end for the sites you chose.
#Next, log into the site's WordPress admin, then go to Plugins.
#'''Very Important:''' Deactivate any other caching plugins like W3 Total Cache on your website, so that LiteSpeed Cache is the only one. If you skip this step, LiteSpeed Cache will not work.
#Still within the WordPress admin, scroll down on the left until you see LiteSpeed Cache. Click that.
#Click the 'DB Optimizer' tab on this new page, then click the 'Clean All' button. After that, click 'Optimize Tables' button at the bottom-right.
#That's it! You have activated LiteSpeed Cache and optimized your WordPress database at the same time. You can either go through all the pages on your site so that they get cached, or you can let the automated crawler do so (see FAQ).

----

=== Frequently Asked Questions ===

'''"Why is LSCWP faster than other caching plugins?"'''

Unlike most other caching plugins, LSCache works by caching pages on a server-level. It can do this because it has access to LiteSpeed, and through that the server as a whole. The first time a page loads it may load at normal rates, for that's the time it is getting placed into the server cache. After that, it will load almost instantly for everyone, as it is pulled from the server cache instead of the web server. Normal caching plugins work by caching pages on a client/browser level, which is much less efficient, as every person browsing the site will have to load the pages themselves before they are cached on their local machine instead of the server.

'''"If a page is changed, will the changed be cached again automatically?"'''

LSCache comes with what is called a '''crawler''' that checks each page of your website for changes. When it detects that a cached page is changed, it will re-cache the page automatically. It does this every 400 seconds, so changes you make will indeed quickly be cached once more. You can modify this 400-second value as well as a plethora of other technical features by going to Plugins -> LiteSpeed Cache -> Settings. There are many tabs of configuration variables you and your developers can modify at that location. This is not to say you need to-- LSCWP comes out-of-the-box with all settings configured at optimal values for most websites.

'''"Is there a way to force a page to re-cache?"'''

To 'force-reload' a page into the cache, all it will take is simply loading the page once through the browser. LSCache will detect that it hasn't been cached before (or if a different version of it was cached) and it will automatically update. The aforementioned crawler will also do this every 400 seconds.

If you have a question that is not listed here, [https://support.hostek.com/ please feel free to contact Hostek.com support by clicking here.]

Cron Jobs

2017-07-13T18:34:21Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php</nowiki>

*If your HTTP URL cron has special characters such as '&' or ':' in the URL, you can include those normally, as below. Note that using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:example&example=example</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:34:04Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally (as below). Using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php</nowiki>

*If your HTTP URL cron has special characters such as '&' or ':' in the URL, you can include those normally, as below. Note that using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:example&example=example</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:32:33Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally (as below). Using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:example&example=example</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:32:09Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally. Using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:example&example=example</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:31:14Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally. Using URL encoding like %26 and %3a will not work with curl.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:request&action=activate</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:30:59Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally. Using URL encoding like %26 and %3a will not work.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:request&action=activate</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:29:23Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP request requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:request&action=activate</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

Cron Jobs

2017-07-13T18:28:57Z

DanielleM: /* cPanel/Linux - Setting up Cron Jobs */

__FORCETOC__

==cPanel/Linux - Setting up Cron Jobs==
*[http://hostek.com/tutorials/cpanel-x3-cronjob.html How to setup a cron job]

*Please keep in mind that you may require a specific service for a cron job to get properly executed. For example, a PHP requires /usr/bin/php to run-- like the cron below: 

/usr/bin/php -q /home/user/public_html/cron.php

*If you do not want email confirmation for each successful cron, you will need to add the following to the end of your cron job:

/usr/bin/php -q /home/user/public_html/cron.php > /dev/null

*If you want to use a HTTP URL in your cron, it would look like the following. Note that if your URL has special characters such as '&' or ':', you can include those normally.

/usr/bin/curl --silent --output /dev/null <nowiki>http://yourdomain.com/cron.php:request&action=activate</nowiki>

==WCP/Windows - Setting up Cron Jobs==
#With a recent update to Windows Control Panel (WCP) we've added Windows cron jobs. To make use of these, login to WCP and find the Cron Jobs tool (clock icon). It'll be on the bottom of the panel. To set up a cron on Windows:
##Click Add
##Choose a name for the Cron
##Place a URL to be executed
##If this is a simple cron, keep the Easy mode selected. Advanced gives you complete control over when your cron runs.
##Choose the interval at which the cron runs
##Click Save

==Common Cron Failures==
*Not Firing: When You Specified Make sure your time format is correct. Sometimes extra zeroes or an extra asterisk (*) makes their way into the mix. This will cause the cron to fire at the wrong time, or a complete failure.

*Long Wait Times: If your script has long processes it handles and you've manually changed the timeout time in the configurations, this may not be passed to the cron. See if you can shorten the processing time. If you need to try and lengthen the timeout time on the cron, send an email to support@hostek.com with the details of your cron job.

*Multiple Firings: Most time when you see multiple firings it's actually that the cron is executing an initial part of the script, failing somewhere after that, and trying again. Try setting up a flag, most usually a simple email, at the very end of the code to determine if this is what's causing the double firings.

*No Firings: If your cron is not failing at all, you may need to look at the logs as to why. To do this, send an email to support@hostek.com. However, the most common reasons for why a cron wouldn't fire at all are below.

**Missing/invalid script path: If you need the script at D:\home\domain.com\wwwroot\myscript.php to fire, but you say it's at D:\home\domain.com\myscript.php then nothing will fire.
**Bad URL: Most crons need to have HTTP:// in front of the URL path. Make sure to check the URL you're using.

.htaccess

2017-05-24T16:11:00Z

DanielleM:

==Can I use a .htaccess file to password protect a directory?==
Yes, on our LINUX servers you can use a .htaccess file to password protect a directory.

The code to perform this is:
<pre>
AuthUserFile /usr/local/you/safedir/.htpasswd
AuthGroupFile /dev/null
AuthName EnterPassword
AuthType Basic

require user wsabstract
</pre>

Change the File directory to the directory listed in your File Manager.

==Enabling Case Insensitive URLs for my Linux site==
Add the following to your .htaccess file:
<pre>CheckSpelling on</pre>

==Rewriting all URL requests to WWW.==
Add the following to your .htaccess code:
<pre>
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
</pre>

==Rewriting HTTP requests to HTTPS==
Add the following to your .htaccess code:
<pre>
RewriteEngine On
RewriteCond %{HTTPS} !^on$
RewriteRule (.*) https://yourdomain/$1 [R,L]
</pre>

==Create a Wildcard Subdomain Redirect==
Add the following to your .htaccess code:
<pre>
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.mydomain\.dk$ [NC]
RewriteCond %{HTTP_HOST} ^(.*)\.mydomain.dk$ [NC]
RewriteRule ^(.*)$ http://mydomain.dk/ [P,L,QSA]
</pre>

==Create an IP-based Whitelist to a WordPress login page==
Create a file called '.htaccess' in the same directory as the 'wp-login.php' page. Add the following code:
<pre>
Order Allow,Deny
Allow from 111.222.333.444
</pre>
Replace 111.222.333.444 with your IP (you can find your IP at http://hostek.com/IP. Note that you can add multiple IP addresses like so:
<pre>
Order Allow,Deny
Allow from 111.222.333.444
Allow from 111.222.333.444
Allow from 111.222.333.444
Allow from 111.222.333.444
</pre>

==Create a password to access the WordPress login page==
Go to the directory outside of your website's public_html folder and create a file called .htpasswd. Within it, add the following:
<pre>
wp-user:$apr1$6DKxmMhU$liMLjMbLcQ1JmgLZix5l1/
</pre>
'''Note:''' The above file makes any login prompt that uses it have the username 'wp-user' and the password 'wp-password'. You can create your own login info to enter into the above file by [http://www.htaccesstools.com/htpasswd-generator/ clicking here and generating it.] 
 Next, create a file called '.htaccess' in the same directory as the 'wp-login.php' page (usually /public_html). Add the following code:
<pre>
<FilesMatch "wp-login.php">
AuthType Basic
AuthName "Please Enter the WordPress Access Password:"
AuthUserFile /home/username/.htpasswd
Require valid-user
</FilesMatch>
</pre>
The above info will now cause any request to the WordPress login page refer to the password file we just created. Replace 'username' with your cPanel username, usually found on the left side of your cPanel control panel home page.
[[Category:Linux]]

.htaccess

2017-05-24T15:59:14Z

DanielleM:

SFTP

2016-07-08T18:02:05Z

DanielleM: Created page with "==Summary== '''Secure File Transfer Protocol''' (SFTP) is a secure version of File Transfer Protocol (FTP), which sends data access and data transfer over a Secure Shell (SSH)..."

==Summary==
'''Secure File Transfer Protocol''' (SFTP) is a secure version of File Transfer Protocol (FTP), which sends data access and data transfer over a Secure Shell (SSH) connection. This term is also known as SSH File Transfer Protocol. Some WordPress plugins and other software request the use of SFTP.
 
===Benefits of SFTP===
Whenever a user opens up a regular ftp session, the entire transmission made between the host and the user is sent in plain text, which violates a number of key security fundamentals. When using SFTP, however, the entire login session -- including any files transferred during the session -- is completely encrypted.
 
===SFTP on cPanel Shared Server Environment===
Allowing SFTP by default on a shared webserver is a moderate security risk, since SFTP uses an SSH connection to function. In order to use an SSH connection, shell access must be given to a user account. Enabling SSH access globally on the server so SFTP works by default removes a layer of security for all clients on the server, since anyone may access SSH in a jailed session at any time.

However, there is an alternative to SFTP that we employ on Hostek.com shared servers which is much more secure in the terms of the above. This method is called TLS, and is enabled by default on all of our shared environments:

[https://wiki.hostek.com/Enabling_TLS_on_Common_FTP_Software| Please click here for a guide to connect to Hostek.com cPanel/Linux servers via FTP over TLS.]

If you have an application that requires SFTP to function, however, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and mention this guide. We'd be glad to enable SSH for just your account. Once we confirm SSH is enabled, you may [https://wiki.hostek.com/SFTP_-_How_to_Enable_sFTP_on_your_VPS| click here to follow Hostek.com's guide and set up SFTP.]
 
===SFTP on a VPS Environment===
Enabling SFTP on a private server is perfectly acceptable, as the risks described for a shared server do not apply. [https://wiki.hostek.com/SFTP_-_How_to_Enable_sFTP_on_your_VPS| For a guide to enable SFTP on your VPS, please click here.]

Easy steps on how to migrate WordPress blog

2016-07-08T17:12:39Z

DanielleM:

==Summary==
 
Moving/migrating a WordPress site from one host to another can be troublesome at times, but with this guide you can do it quickly with no downtime to your website!
 
===To migrate your WordPress site, follow the steps below:===
#Back up your database.
#*If you are unfamiliar with database backups, [https://wiki.hostek.com/Mysql_backup| please click here for Hostek.com's guide to creating a backup, or ''exporting'', your database.]
#Connect to your website via FTP on the old server (the web host you are moving ''from'').
#Download your website files to a location on your computer. These should include everything in the '''public_html''' folder (on a Linux server) or '''wwwroot''' folder (on a Windows server) directories.
#Once all files have been downloaded to your computer, connect to your website via FTP on the ''new'' server (the web host you are moving ''to'').
#Upload the same files you just downloaded to the new location, making sure to place your website files into the '''public_html''' folder (on a Linux/cPanel server) or the '''wwwroot''' folder (on a Windows server).
#Now that you have your WordPress files uploaded to the new hosting location, it's time to upload, or ''import'', your database backup.
#*If you are unfamiliar with database importing, [https://wiki.hostek.com/PhpMyAdmin_Importing_Database#How_to_import_your_MySQL_database_using_phpMyAdmin| please click here and follow the steps appropriate for your hosting package to import your database backup.]
#Once your database is imported, go back to your FTP software with the connection to your new server/web host. Find the file you uploaded called '''wp-config.php''' with your FTP software and edit it.
#Look for the following lines in the '''wp-config.php''':
#:define('DB_NAME', '<your old database name>');
#:/** MySQL database username */
#:define('DB_USER', '<your old database username>');
#:/** MySQL database password */
#:define('DB_PASSWORD', '<your old database password>');
#Change the text in the position of <your old database name> above to the name of the database [https://wiki.hostek.com/PhpMyAdmin_Importing_Database#How_to_import_your_MySQL_database_using_phpMyAdmin| you set up using our guide.]. Do the same for the database username, then the database password.
#Congratulations! You are done transferring your WordPress over to its new location. All that remains is that you update your domain's nameservers:
#*[https://wiki.hostek.com/DNS_-_Name_Servers#Updating_Name_Servers_for_Domain_registered_with_Hostek.com| If you purchased your domain with Hostek.com, click here for a tutorial to update your nameservers.]
#*[https://wiki.hostek.com/DNS_-_Name_Servers#Updating_Name_Servers_at_other_registrars_-_Video_Tutorials| If you purchased your domain with another registrar, click here to find the right tutorial for you.]

Easy steps on how to migrate WordPress blog

2016-07-08T17:12:04Z

DanielleM: Created page with "==Summary== Moving/migrating a WordPress site from one host to another can be troublesome at times, but with this guide you can do it quickly with no downtime to your website..."

==Summary==

Moving/migrating a WordPress site from one host to another can be troublesome at times, but with this guide you can do it quickly with no downtime to your website!
 
===To migrate your WordPress site, follow the steps below:===
#Back up your database.
#*If you are unfamiliar with database backups, [https://wiki.hostek.com/Mysql_backup| please click here for Hostek.com's guide to creating a backup, or ''exporting'', your database.]
#Connect to your website via FTP on the old server (the web host you are moving ''from'').
#Download your website files to a location on your computer. These should include everything in the '''public_html''' folder (on a Linux server) or '''wwwroot''' folder (on a Windows server) directories.
#Once all files have been downloaded to your computer, connect to your website via FTP on the ''new'' server (the web host you are moving ''to'').
#Upload the same files you just downloaded to the new location, making sure to place your website files into the '''public_html''' folder (on a Linux/cPanel server) or the '''wwwroot''' folder (on a Windows server).
#Now that you have your WordPress files uploaded to the new hosting location, it's time to upload, or ''import'', your database backup.
#*If you are unfamiliar with database importing, [https://wiki.hostek.com/PhpMyAdmin_Importing_Database#How_to_import_your_MySQL_database_using_phpMyAdmin| please click here and follow the steps appropriate for your hosting package to import your database backup.]
#Once your database is imported, go back to your FTP software with the connection to your new server/web host. Find the file you uploaded called '''wp-config.php''' with your FTP software and edit it.
#Look for the following lines in the '''wp-config.php''':
#:define('DB_NAME', '<your old database name>');
#:/** MySQL database username */
#:define('DB_USER', '<your old database username>');
#:/** MySQL database password */
#:define('DB_PASSWORD', '<your old database password>');
#Change the text in the position of <your old database name> above to the name of the database [https://wiki.hostek.com/PhpMyAdmin_Importing_Database#How_to_import_your_MySQL_database_using_phpMyAdmin| you set up using our guide.]. Do the same for the database username, then the database password.
#Congratulations! You are done transferring your WordPress over to its new location. All that remains is that you update your domain's nameservers:
#*[https://wiki.hostek.com/DNS_-_Name_Servers#Updating_Name_Servers_for_Domain_registered_with_Hostek.com| If you purchased your domain with Hostek.com, click here for a tutorial to update your nameservers.]
#*[https://wiki.hostek.com/DNS_-_Name_Servers#Updating_Name_Servers_at_other_registrars_-_Video_Tutorials| If you purchased your domain with another registrar, click here to find the right tutorial for you.]

PhpMyAdmin Importing Database

2016-07-08T16:50:50Z

DanielleM: /* How to import your MySQL database using phpMyAdmin */

==How to import your MySQL database using phpMyAdmin==
[[File:Phpmyadmin_300.png‎]]
===For Windows VPSs or Windows Shared Servers:===
# Access your [https://wcp.hostek.com|'''Windows Control Panel (WCP.hostek.com)''']
# You will first need to create a MySQL database by clicking on the MySQL Icon in the Database Section.
## NOTE: If you just created the database, you will need to refresh the page in order to complete the next step.
# Click on the phpMyAdmin icon in the Database section
## If you have multiple databases/users, choose which database your want to access
# In phpMyAdmin, click on the database
# In the tab section look for and then select Import
# Under the File to Import: section, select Browse... to locate the SQL or .zip file on your computer
# Hit Go at the bottom of the page to begin the import.
===For Linux/cPanel VPSs or Linux/cPanel Shared Servers:===
# Access your cPanel account by using the information in your Hostek Welcome Email. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.
# You will first need to create a MySQL database and user by clicking on the 'MySQL Database Wizard' icon in cPanel.
# Follow the steps in the Wizard, creating a username, password, and database name as directed. Note that the username and database name will always be prefixed with your account name (example: hostek_database and hostek_user)
# When you reach the step in the Wizard where you see '''ALL PRIVILEGES''', make sure to click the checkbox next to '''ALL PRIVILEGES''', then hit Next Step.
# Once you've completed creating a MySQL database, go back to your main cPanel interface and click 'Phpmyadmin'.
# In phpMyAdmin, click on the database on the left.
# In the tab section at the top, look for Import and select it.
# Under the File to Import: section, select Browse... to locate the SQL or .zip file on your computer [https://wiki.hostek.com/Mysql_backup| you created with Hostek.com's database backup wiki.] or via another method.
# Hit Go at the bottom of the page to begin the import.
===Import Video Tutorial===
To view a video tutorial of this process on an example Windows environment:
[http://hostek.com/tutorials/phpma-import.html Importing databases and tables with phpMyAdmin]

==Troubleshooting==

===#1007 - Can't create database===

#1007 - Can't create database '%dbname%'; database exists

This indicates that you have a query in your SQL file that is trying to create a database, and since it already exist, it will not 
work. Someone must edit the file and remove the CREATE DATABASE query.

===#1044 - Access denied for user===

#1044 - Access denied for user 'username'@'host' to database '%dbname%'

The issue here indicates there is a query that is attempting to create a database with the wrong username. If the database was created with a different user name than what is in the SQL file, it will need to be updated.

===#1064 - You have an error in your SQL syntax===

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax

This issue indicated that there is a error in your syntax. It could be because you are trying to import an older version of sql with outdated syntax, or the file is corrupted in some way and the sql file is not readable. You can try exporting the file from the other location, but this error will generally give a location of the syntax error, and if it is only a few things, you can update the file then try to import it again.

===Timing Out During Import===

If your database is timing out during the import process this could mean that your database is too large. You will need to contact support by creating a support ticket at [https://support.hostek.com support.hostek.com] Please upload your SQL or .zip database file to your root folder of your site. Windows (wwwroot) Linux (public_html). We will need to import your database for you.

[[File:mysql-logo.jpg]]

[[Category:Databases-MySQL]]
[[Category:MySQL]]
[[Category:Tutorials]]

Enabling TLS on Common FTP Software

2016-03-04T19:47:38Z

DanielleM: /* CuteFTP */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Change the 'Logon Type' to 'Normal'.
# Enter your FTP account's 'Username' and 'Password'.
# Click 'OK' to save this connection.
# To connect, open 'Site Manager', or click the drop-down arrow next to the 'Site Manager' icon.
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.
 
[[File:fz_tls_b.png]]

===WinSCP===

# Open the WinSCP client
# Create a new site or edit an existing site
# Change the File protocol to "FTP"
# Change the Encryption to "TLS Explicit encryption"
# Change the Host name to your domain (Example: yourdomain.com)
# Change the Port number to 21
# Change the User name to your FTP username
# Change the Password to the password that corresponds with your FTP username
# Click the Save button
# Click the Login button to connect

Below is an image of the WinSCP Session window for reference:

[[File:Winscp-ftp-tls-setup.png]]

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]

===FireFTP===

# Open up Firefox and click on Tools > Web Developer > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS with TLS/SSL (AUTH TLS - Explicit) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

New Connections:

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.

Existing Connections:

#Click 'Connections' > 'Site Manager'.
#Click 'Edit' next to the site you would like to modify.
#Click 'Advanced', then change the 'Server Type' dropdown to 'FTP/SSL (AUTH SSL)'.
#Click OK.

 

===Core FTP LE===

#Click File->Connect.
#Enter the following:
#*'''Site Name:''' Choose a name for the connection.
#*'''Host / IP / URL:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection:''' AUTH TLS.
#Click Connect.

 
===FTPSurfer===

FTPSurfer does not support FTP over explicit SSL at this time. Please use an alternate FTP client.
 

===Expression Web 4===
Expression Web 4 does not support FTP over TLS, however it will support FTPS requests using port 990.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.

Enabling TLS on Common FTP Software

2015-10-28T21:51:46Z

DanielleM: /* FireFTP */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Change the 'Logon Type' to 'Normal'.
# Enter your FTP account's 'Username' and 'Password'.
# Click 'OK' to save this connection.
# To connect, open 'Site Manager', or click the drop-down arrow next to the 'Site Manager' icon.
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.
 
[[File:fz_tls_b.png]]

===WinSCP===

# Open the WinSCP client
# Create a new site or edit an existing site
# Change the File protocol to "FTP"
# Change the Encryption to "TLS Explicit encryption"
# Change the Host name to your domain (Example: yourdomain.com)
# Change the Port number to 21
# Change the User name to your FTP username
# Change the Password to the password that corresponds with your FTP username
# Click the Save button
# Click the Login button to connect

Below is an image of the WinSCP Session window for reference:

[[File:Winscp-ftp-tls-setup.png]]

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]

===FireFTP===

# Open up Firefox and click on Tools > Web Developer > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

New Connections:

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.

Existing Connections:

#Click 'Connections' > 'Site Manager'.
#Click 'Edit' next to the site you would like to modify.
#Click 'Advanced', then change the 'Server Type' dropdown to 'FTP/SSL (AUTH SSL)'.
#Click OK.

 

===Core FTP LE===

#Click File->Connect.
#Enter the following:
#*'''Site Name:''' Choose a name for the connection.
#*'''Host / IP / URL:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection:''' AUTH TLS.
#Click Connect.

 
===FTPSurfer===

FTPSurfer does not support FTP over explicit SSL at this time. Please use an alternate FTP client.
 

===Expression Web 4===
Expression Web 4 does not support FTP over TLS, however it will support FTPS requests using port 990.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.

CloudLinux

2015-10-22T21:17:17Z

DanielleM: /* Cloudlinux PHP Selector */

__FORCETOC__

== What is CloudLinux ==
* More stable - Less downtime
* More secure

CloudLinux is a Kernel-level technology that helps provide for a more stable hosting environment. This is accomplished by protecting your site against the bad neighbor effect. What this means is that CloudLinux will prevent a single site from crashing a server, making your site unresponsive. When a single customer's site starts consuming too much of the generous amount of server resources, CloudLinux will throttle just that site to allow it to continue operating up to a safe server level, while at the same time fully protecting your site from 'bad neighbor'.

==Cloudlinux PHP Selector==

Hostek.com uses CloudLinux on all of our shared servers, but a license to add it to a VPS is completely optional. One of the benefits (among the others outlined above) is access to something called 'cl.selector', AKA CloudLinux PHP selector. This allows us to change PHP versions on a per-site basis (for example, you might require PHP version 5.5 on one website, and 5.6 on another. Without cl.selector, this would not be possible) as well as change the PHP modules per-site.

CloudLinux offers a very simple to install and use PHP selector. The first step in the install process is to set up a CloudLinux license. At current, these are $13.95 a month for our VPS customers. CloudLinux boasts not only accessibility via the various reliable plugins it offers (like the PHP selector) but increases server security, and allows you to limit resource usage across all accounts on your VPS with an in-WHM menu.

To access the PHP selector, simply click the 'Select PHP Version' button in the control panel for any site. Once done, use the drop-down to select the PHP version you need and then click 'set as current'.

Get with our support team today if you would like the CloudLinux PHP Selector to your VPS, or any of the other software included in the CloudLinux Suite.

== What to do if your site is being throttled by CloudLinux ==
This would be a very rare situation. However, if your site is the one potentially causing server problems (ie, the 'bad neighbor), which means your site is being throttled and seems to work sometimes and not others, or maybe just not working for the most part, this means your site is consuming too many server resources. We have these throttle limits so high that if your site is hitting these limits, generally it should not be on any shared hosting environment.

The one exception to that would be if your site has hundreds or thousands of pages and a bot is heavily crawling your site. If that is the case, we suggest you add a Crawl-Delay setting to your robots.txt file to slow down the bots. Generally setting the Crawl-Delay to 10 will suffice.

In the rare case that your site does get throttled by CloudLinux, we suggest looking at your log files to see what may be causing the problem. If you just have a ton of traffic (ie, way beyound normal shared hosting) then you really need to get a VPS asap. If you have a run-away script, then you should review the code for that to see if you can find/fix the problem.

[[Category:Linux]]

CloudLinux

2015-10-21T17:12:42Z

DanielleM: /* Cloudlinux PHP Selector */

__FORCETOC__

== What is CloudLinux ==
* More stable - Less downtime
* More secure

CloudLinux is a Kernel-level technology that helps provide for a more stable hosting environment. This is accomplished by protecting your site against the bad neighbor effect. What this means is that CloudLinux will prevent a single site from crashing a server, making your site unresponsive. When a single customer's site starts consuming too much of the generous amount of server resources, CloudLinux will throttle just that site to allow it to continue operating up to a safe server level, while at the same time fully protecting your site from 'bad neighbor'.

==Cloudlinux PHP Selector==

Hostek.com uses CloudLinux on all of our shared servers, but a license to add it to a VPS is completely optional. One of the benefits (among the others outlined above) is access to something called 'cl.selector', AKA CloudLinux PHP selector. This allows us to change PHP versions on a per-site basis (for example, you might require PHP version 5.5 on one website, and 5.6 on another. Without cl.selector, this would not be possible) as well as change the PHP modules per-site.

CloudLinux offers a very simple to install and use PHP selector. The first step in the install process is to set upa CloudLinux license. At current, these are $13.95 a month for our VPS customers. CloudLinux boasts not only accessibility via the various reliable plugins it offers (like the PHP selector) but increases server security, and allows you to limit resource usage across all accounts on your VPS with an in-WHM menu.

To access the PHP selector, simply click the 'Select PHP Version' button in the control panel for any site. Once done, use the drop-down to select the PHP version you need and then click 'set as current'.

Get with our support team today if you would like the CloudLinux PHP Selector to your VPS, or any of the other software included in the CloudLinux Suite.

== What to do if your site is being throttled by CloudLinux ==
This would be a very rare situation. However, if your site is the one potentially causing server problems (ie, the 'bad neighbor), which means your site is being throttled and seems to work sometimes and not others, or maybe just not working for the most part, this means your site is consuming too many server resources. We have these throttle limits so high that if your site is hitting these limits, generally it should not be on any shared hosting environment.

The one exception to that would be if your site has hundreds or thousands of pages and a bot is heavily crawling your site. If that is the case, we suggest you add a Crawl-Delay setting to your robots.txt file to slow down the bots. Generally setting the Crawl-Delay to 10 will suffice.

In the rare case that your site does get throttled by CloudLinux, we suggest looking at your log files to see what may be causing the problem. If you just have a ton of traffic (ie, way beyound normal shared hosting) then you really need to get a VPS asap. If you have a run-away script, then you should review the code for that to see if you can find/fix the problem.

[[Category:Linux]]

CloudLinux

2015-10-21T17:12:16Z

DanielleM:

__FORCETOC__

== What is CloudLinux ==
* More stable - Less downtime
* More secure

CloudLinux is a Kernel-level technology that helps provide for a more stable hosting environment. This is accomplished by protecting your site against the bad neighbor effect. What this means is that CloudLinux will prevent a single site from crashing a server, making your site unresponsive. When a single customer's site starts consuming too much of the generous amount of server resources, CloudLinux will throttle just that site to allow it to continue operating up to a safe server level, while at the same time fully protecting your site from 'bad neighbor'.

==Cloudlinux PHP Selector==

Hostek.com uses CloudLinux on all of our shared servers, but a license to add it to a VPS is completely optional. One of the benefits (among the others outlined above) is access to something called 'cl.selector', AKA CloudLinux PHP selector. This allows us to change PHP versions on a per-site basis (for example, you might require PHP version 5.5 on one website, and 5.6 on another. Without cl.selector, this would not be possible) as well as change the PHP modules per-site.

CloudLinux offers a very simple to install and use PHP selector. The first step in the install process is to set upa CloudLinux license. At current, these are $13.95 a month for our VPS customers. CloudLinux boasts not only accessibility via the various reliable plugins it offers (like the PHP selector) but increases server security, and allows you to limit resource usage across all accounts on your VPS with an in-WHM menu.

To access the PHP selector, simply click the 'Select PHP Version' button in the control panel for any site. Once done, use the drop-down to select 5.5 and then click 'set as current'.

Get with our support team today if you would like the CloudLinux PHP Selector to your VPS, or any of the other software included in the CloudLinux Suite.

== What to do if your site is being throttled by CloudLinux ==
This would be a very rare situation. However, if your site is the one potentially causing server problems (ie, the 'bad neighbor), which means your site is being throttled and seems to work sometimes and not others, or maybe just not working for the most part, this means your site is consuming too many server resources. We have these throttle limits so high that if your site is hitting these limits, generally it should not be on any shared hosting environment.

The one exception to that would be if your site has hundreds or thousands of pages and a bot is heavily crawling your site. If that is the case, we suggest you add a Crawl-Delay setting to your robots.txt file to slow down the bots. Generally setting the Crawl-Delay to 10 will suffice.

In the rare case that your site does get throttled by CloudLinux, we suggest looking at your log files to see what may be causing the problem. If you just have a ton of traffic (ie, way beyound normal shared hosting) then you really need to get a VPS asap. If you have a run-away script, then you should review the code for that to see if you can find/fix the problem.

[[Category:Linux]]

Enabling TLS on Common FTP Software

2015-09-25T20:13:07Z

DanielleM:

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Change the 'Logon Type' to 'Normal'.
# Enter your FTP account's 'Username' and 'Password'.
# Click 'OK' to save this connection.
# To connect, open 'Site Manager', or click the drop-down arrow next to the 'Site Manager' icon.
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.
 
[[File:fz_tls_b.png]]

===WinSCP===

# Open the WinSCP client
# Create a new site or edit an existing site
# Change the File protocol to "FTP"
# Change the Encryption to "TLS Explicit encryption"
# Change the Host name to your domain (Example: yourdomain.com)
# Change the Port number to 21
# Change the User name to your FTP username
# Change the Password to the password that corresponds with your FTP username
# Click the Save button
# Click the Login button to connect

Below is an image of the WinSCP Session window for reference:

[[File:Winscp-ftp-tls-setup.png]]

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]

===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

New Connections:

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.

Existing Connections:

#Click 'Connections' > 'Site Manager'.
#Click 'Edit' next to the site you would like to modify.
#Click 'Advanced', then change the 'Server Type' dropdown to 'FTP/SSL (AUTH SSL)'.
#Click OK.

 

===Core FTP LE===

#Click File->Connect.
#Enter the following:
#*'''Site Name:''' Choose a name for the connection.
#*'''Host / IP / URL:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection:''' AUTH TLS.
#Click Connect.

 
===FTPSurfer===

FTPSurfer does not support FTP over explicit SSL at this time. Please use an alternate FTP client.
 

===Expression Web 4===
Expression Web 4 does not support FTP over TLS, however it will support FTPS requests using port 990.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.

Automated Apache Updates

2015-08-06T18:35:25Z

DanielleM: /* Summary */

==Summary==
 
By default, PHP and Apache updates are not automatic. This is mostly to prevent incompatibilities between major versions of these programs and your website's possibly outdated code. However, we can still enable automatic updates of ''minor'' versions in these two programs (i.e 5.4.'''21''' and 2.2.'''24'''). Benefits of this include patching up discovered exploits, allowing the latest PHP code to be compatible, and generally optimizing how these two programs handle PHP requests.

==Enabling Automatic Minor Version Updates==
 
Enabling updates is as simple as setting up a cron job in a SSH session. The steps to do this are below:

#Connect to your server via SSH. Lost? [https://wiki.hostek.com/SSH_Access_-_Private_Servers Read our guide on how to do this here.]
#Once in your server, we're going to make a simple script that will run the command we need. Type the following and hit enter: nano apacheupdate.sh
#This will bring you into a simple text editor. Here, we're going to type the following: /scripts/easyapache --build
#When you have this entered in, press control+O, then enter, to save. Then press control+X to close the editor.
#Now we're going to make this script executable. Type the following and hit enter: chmod +x apacheupdate.sh
#Once this is done, we'll do the last step; adding the cron. Type the following and hit enter: crontab -e
#Here you will be in another text editor with some lines already existing within. Hit enter to make a new line, then type the following exactly how it appears:
<pre>0 22 * * * /root/apacheupdate.sh</pre>

Once the above has been completed, press control+O, enter, then control+X to close just as before. That's it! Your Apache/PHP minor versions will update every night at 10pm server time.

==Alternate Cron Configurations==
 

If you'd like to set up a cron for different update schedules, follow the guide above but instead enter the following lines for their respective schedules:
 
'''Update every week on Sunday at 10pm:'''
<pre>0 10 * * 6 /root/apacheupdate.sh</pre>

'''Update every night at 1:05am:'''
<pre>5 1 * * * /root/apacheupdate.sh</pre>

Automated Apache Updates

2015-08-06T18:34:08Z

DanielleM: /* Enabling Automatic Minor Version Updates */

==Summary==
 
By default, PHP and Apache updates are not automatic. This is mostly to prevent incompatibilities between major versions of these programs and your website's possibly outdated code. However, we can still enable automatic updates of ''minor'' versions in these two programs (i.e 5.4.'''21''' and 2.2.'''24''').

==Enabling Automatic Minor Version Updates==
 
Enabling updates is as simple as setting up a cron job in a SSH session. The steps to do this are below:

#Connect to your server via SSH. Lost? [https://wiki.hostek.com/SSH_Access_-_Private_Servers Read our guide on how to do this here.]
#Once in your server, we're going to make a simple script that will run the command we need. Type the following and hit enter: nano apacheupdate.sh
#This will bring you into a simple text editor. Here, we're going to type the following: /scripts/easyapache --build
#When you have this entered in, press control+O, then enter, to save. Then press control+X to close the editor.
#Now we're going to make this script executable. Type the following and hit enter: chmod +x apacheupdate.sh
#Once this is done, we'll do the last step; adding the cron. Type the following and hit enter: crontab -e
#Here you will be in another text editor with some lines already existing within. Hit enter to make a new line, then type the following exactly how it appears:
<pre>0 22 * * * /root/apacheupdate.sh</pre>

Once the above has been completed, press control+O, enter, then control+X to close just as before. That's it! Your Apache/PHP minor versions will update every night at 10pm server time.

==Alternate Cron Configurations==
 

If you'd like to set up a cron for different update schedules, follow the guide above but instead enter the following lines for their respective schedules:
 
'''Update every week on Sunday at 10pm:'''
<pre>0 10 * * 6 /root/apacheupdate.sh</pre>

'''Update every night at 1:05am:'''
<pre>5 1 * * * /root/apacheupdate.sh</pre>

Automated Apache Updates

2015-08-06T18:33:20Z

DanielleM: Created page with "==Summary== By default, PHP and Apache updates are not automatic. This is mostly to prevent incompatibilities between major versions of these programs and your website'..."

==Summary==
 
By default, PHP and Apache updates are not automatic. This is mostly to prevent incompatibilities between major versions of these programs and your website's possibly outdated code. However, we can still enable automatic updates of ''minor'' versions in these two programs (i.e 5.4.'''21''' and 2.2.'''24''').

==Enabling Automatic Minor Version Updates==
 
Enabling updates is as simple as setting up a cron job in a SSH session. The steps to do this are below:

#Connect to your server via SSH. Lost? [https://wiki.hostek.com/SSH_Access_-_Private_Servers Read our guide on how to do this here.]
#Once in your server, we're going to make a simple script that will run the command we need. Type the following and hit enter: nano apacheupdate.sh
#This will bring you into a simple text editor. Here, we're going to type the following: /scripts/easyapache --build
#When you have this entered in, press control+O to save, then control+X to close the editor.
#Now we're going to make this script executable. Type the following and hit enter: chmod +x apacheupdate.sh
#Once this is done, we'll do the last step; adding the cron. Type the following and hit enter: crontab -e
#Here you will be in another text editor with some lines already existing within. Hit enter to make a new line, then type the following exactly how it appears:
<pre>0 22 * * * /root/apacheupdate.sh</pre>

Once the above has been completed, press control+O, enter, then control+X to close just as before. That's it! Your Apache/PHP minor versions will update every night at 10pm server time.

==Alternate Cron Configurations==
 

If you'd like to set up a cron for different update schedules, follow the guide above but instead enter the following lines for their respective schedules:
 
'''Update every week on Sunday at 10pm:'''
<pre>0 10 * * 6 /root/apacheupdate.sh</pre>

'''Update every night at 1:05am:'''
<pre>5 1 * * * /root/apacheupdate.sh</pre>

Improve WordPress Site Speed

2015-05-29T19:51:53Z

DanielleM: /* WordPress Version */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.
 
Generally, image optimization plugins require manual optimization of pictures that have already been uploaded. As such, these will not work automatically and will require you to visit the appropriate 'settings' page within your WordPress admin dashboard.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes. An outdated or badly-coded theme can dramatically slow down your WordPress website.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information regarding this new feature.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:51:17Z

DanielleM: /* Getting the Right Theme */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.
 
Generally, image optimization plugins require manual optimization of pictures that have already been uploaded. As such, these will not work automatically and will require you to visit the appropriate 'settings' page within your WordPress admin dashboard.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes. An outdated or badly-coded theme can dramatically slow down your WordPress website.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:50:26Z

DanielleM: /* Getting the Right Theme */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.
 
Generally, image optimization plugins require manual optimization of pictures that have already been uploaded. As such, these will not work automatically and will require you to visit the appropriate 'settings' page within your WordPress admin dashboard.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes. An outdated or badly-coded theme can dramatically slow down WordPress websites.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:49:43Z

DanielleM: /* Getting the Right Theme */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.
 
Generally, image optimization plugins require manual optimization of pictures that have already been uploaded. As such, these will not work automatically and will require you to visit the appropriate 'settings' page within your WordPress admin dashboard.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Generally choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes. An outdated or badly-coded theme can dramatically slow down WordPress websites.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:48:28Z

DanielleM: /* Image Optimization */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.
 
Generally, image optimization plugins require manual optimization of pictures that have already been uploaded. As such, these will not work automatically and will require you to visit the appropriate 'settings' page within your WordPress admin dashboard.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Generally choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:46:31Z

DanielleM: /* Web Content Caching */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Generally choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:45:23Z

DanielleM: /* Image Optimization */

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) images and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Generally choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Improve WordPress Site Speed

2015-05-29T19:44:07Z

DanielleM: Created page with "==Summary== Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your..."

==Summary==

Often we find that WordPress' out-of-the-box site speed is not the fastest it could be. In this guide we'll show you how you can improve load times and make your WordPress site faster!

==Web Content Caching==

Fetching something over the network is both slow and expensive: large responses require many roundtrips between the client and server, which delays when they are available and can be processed by the browser, and also incurs data costs for the visitor. As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance. 
 
There are several methods we can take advantage of to cache these resources via WordPress plugins. We recommend downloading and activating '''one''' of the following cache plugins onto your site:
 
#[https://wordpress.org/plugins/w3-total-cache/ W3 Total Cache] - This plugin is very highly-rated and offers more advanced customization than other caching plugins out there. It also provides the option for a paid upgrade to receive support and additional features. We recommend this caching plugin.
#[https://wordpress.org/plugins/wp-super-cache/ WP Super Cache] - While offering most of the same functionality as W3 Total Cache, this plugin has a more simple interface for less advanced users.
#[https://wordpress.org/plugins/wp-fastest-cache/ WP Fastest Cache] - A newcomer to the WordPress caching game, this extremely simple plugin is for users who need caching and do not want to configure anything.
 
Once installed and activated, images and static web pages will immediately begin caching. A speed boost should be noticed right away.

==Image Optimization==

If enabling caching does not speed your site up as much as you would like, or if your site is especially image-heavy, installing an image optimization plugin is recommended. These plugins take your already-uploaded (and in some cases those you upload in the future) and compress them so they are served to the visitor much more quickly.
 
Below are some WordPress plugins that do what we're looking for, as well as a small summary on each:
 
#[https://wordpress.org/plugins/ewww-image-optimizer-cloud/ EWWW Image Optimizer (Premium Cloud Version)] - Unlike its name suggests (it actually stands for Exactly WWW), EWWW does an incredible job of compressing images and offers a wide array of configuration options. This plugin is subscription-based and offers 5000 image compression operations for $10.00. [https://ewww.io/plans/ More information can be found here.]
#[https://wordpress.org/plugins/shortpixel-image-optimiser/ ShortPixel Image Optimizer] - This works in a similar way to EWWW but does not have as many features. It is a nice substitute if you would like a free image optimizing plugin.

==Getting the Right Theme==

One thing that often gets overlooked when it comes to site speed is your WordPress Theme itself. While themes are usually chosen for how they look, we suggest that special care is taken when choosing the right theme developer. Generally choosing a developer who has provided more themes for a long period of time is preferred. Keep this in mind while shopping for a theme, also looking for how often the developer releases updates for their themes.

==WordPress Version==

If all of the above has been completed, your site should be running as smoothly as possible. A final thing to consider is keeping your WordPress version as up to date as possible. This means always updating WordPress right when you see that one is available via your dashboard. As of WordPress version 3.7, you can set up automatic WordPress background updates via your wp-config.php file. [https://codex.wordpress.org/Configuring_Automatic_Background_Updates Click here for WordPress' information on this.]

If you are still encountering slow load times after trying everything mentioned here, please [http://support.hostek.com/ submit a ticket] and our support technicians will get to it right away.

Email in Scripts

2015-03-13T17:17:04Z

DanielleM: /* PHP Email Sample */

Sending Email via Scripts

To send email via code or scripts (ie web pages) you can use either the built in SMTP host '''smtpmailer.hostek.net''' which doesn't require a username/password (only from the server) or you can authenticate using your email account, which does require the username and password too.

__FORCETOC__
==ASP Email Sample==
Here is a sample using CDOSYS to send email from ASP pages. CDOSYS replaces CDONTS on Windows 2003 servers and after.

NOTE: We suggest using CDOSYS for all ASP email applications.

<pre>
<%
Dim objCDOConf
Set objCDOConf = Server.CreateObject ("CDO.Configuration")

' ** SET AND UPDATE FIELDS PROPERTIES **
With objCDOConf
' ** OUTGOING SMTP SERVER **

' ** SMTP SERVER **
.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "smtpmailer.hostek.net"

' ** SMTP PORT **
.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25

.Fields("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2

' ** TIMEOUT **
.Fields("http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout") = 60

.Fields.Update
End With

Dim iMsg
set iMsg = CreateObject("CDO.Message")

' ** UPDATE THE CDOSYS CONFIGURATION **
Set iMsg.Configuration = objCDOConf

' apply settings to the message
With iMsg
.To = "test@some_address.com"
.From = "test@your_domain.com"
.Subject = "This is a subject"
.TextBody = "This is the body of the email."
.Send
End With

' cleanup of variables
Set iMsg = Nothing
%>
</pre>

==.NET Email Sample==

=== In Code ===

MailMessage message = new MailMessage("from@email.address","to@email.address");
message.Subject = "subject";
message.Body = "body";
SmtpClient client = new SmtpClient();
client.Send(message);

=== In web.config ===
<system.net>
<mailSettings>
<smtp deliveryMethod="Network">
<network host="smtpmailer.hostek.net" port="25" />
</smtp>
</mailSettings>
</system.net>

==ColdFusion Email Sample==
==PHP Email Sample==

<pre>
<?php

$EmailBody = '';

if (isset($_POST['submit'])) {

foreach($_POST as $key => $value)
{
if ($key != 'submit'){
if($value != ""){
$EmailBody .= $key . ": " . $value . " ";
}
}

}
}

?>

<form action="" method="post">
First Name: 
<input type="text" name="First Name"> 
Last Name: 
<input type="text" name="Last Name"> 
Phone: 
<input type="text" name="Phone"> 
Email Address: 
<input type="text" name="Address"> 
 
<input type="submit" name="submit" value="Send">
 
 

<?php

if($EmailBody != "") {

$fromAddress = "example@example.com";
$toAddress = "example@example2.com";

$headers .= "MIME-Version: 1.0\r\n";
$headers .= "Content-type: text/html; charset=iso-8859-1\r\n";
$headers .= "From: " . $fromAddress ." < " . $fromAddress . ">\r\n";
$headers .= "To: " . $toAddress . " < " . $toAddress . ">\r\n";
$headers .= "Reply-To: " . $fromAddress . " < " . $fromAddress . ">\r\n";
$headers .= "X-Priority: 1\r\n";
$headers .= "X-MSMail-Priority: High\r\n";
$headers .= "X-Mailer: Example Server";

if (mail($toAddress, "Example Email Form", $EmailBody, $headers)) {
echo "Mail sent to ".$toAddress.". \n";
}
else {
echo "Error sending mail. \n";
}
}
?>
</pre>

[[Category:Email]]

Moodle

2014-08-28T21:05:12Z

DanielleM: /* Current Moodle Upgrade Documentation Pages */

__FORCETOC__

==Introduction==
Moodle is a Content Management System which is designed to be a VLE (Virtual Learning Environment). 
It is a free web application that is specifically designed to create effective online learning courses for educators. 
[http://moodle.org Official Site]

==Installation==

===Download, Upload, and Extraction===
#Navigate to http://download.moodle.org/ and download the latest .zip bundle of Moodle by clicking the 'Download' link under the 'zip' column on the very right.
#Once downloaded, upload the .zip file through a FTP program of your choice to the /public_html/ directory - we recommend uploading with a third-party FTP program like Filezilla which you may find [https://filezilla-project.org/download.php?type=client here].
#After the .zip file has been uploaded, navigate to the [http://docs.cpanel.net/twiki/bin/view/AllDocumentation/CpanelDocs/FileManager file manager within cPanel].
#Navigate to the /public_html/ folder within the cPanel file manager, right-click the .zip Moodle file you uploaded and click 'Extract'. Select 'Ok' on the prompt that appears.
#Your Moodle install has now been successfully extracted.

===Creating the Moodle MySQL Database===

#Log into your cPanel account and click 'MySQL Database Wizard' icon to begin the database creation process.
#On the screen that follows, choose a name for your Moodle database. Note that your cPanel username will always be appended to the title followed by an underscore (Ex: username_moodle). Click 'Next Step'.
#*NOTE: Make sure to write down or copy the database name for future use - we will need it for the Moodle Installation.
#Next, select a username and password for the Moodle database. Make sure to write down and store this username/password in a safe place. Once filled out, click 'Create User'.
#On the next screen, click the box labeled 'ALL PRIVLIGES'. This will grant the database user all privileges to access the database you're creating. Congratulations! The database has been created and a user assigned.

===Installing Moodle===

#Navigate to your site by typing your URL with /moodle/ appended to the URL. (Example: http://yoursite.com/moodle - where yoursite.com is your Moodle domain.)
#You should be redirected to http://noblews.net/moodle/install.php where you may select a language. Click 'Next >>' when ready to continue.
#The next page is a file path confirmation - because we uploaded all of the files already we can just select 'Next >>' to continue.
#As a database driver, 'Improved MySQL (native/mysqli)' should be the default option and the one we want to select. Click 'Next >>' to continue.
#The 'Database settings' page we've arrived on is where we will be using the DB info we wrote down in the previous chapter. Below is an example of information that fits the required format:
#*Database host: localhost (Default: localhost - Do not change.)
#*Database name: username_moodledb (Default: moodle - Change to the Database Name you created in Step 2 of 'Creating the Moodle MySQL Database'.)
#*Database user: username_moodleuser (Default: blank - Change to the Database Username you created in Step 3 of 'Creating the Moodle MySQL Database'.)
#*Database password: ********* (Default: blank - Change to the Password you created in Step 3 of 'Creating the Moodle MySQL Database'.)
#*Tables prefix: mdl_ (Default: mdl - You can change this to whatever you'd like your database tables to be prefixed with. If you're unsure, you may use the default 'mdl_'.)
#*Database Port: 3306 (Default: blank - Change to port 3306.)
#*Unix Socket: -- (Do not fill out this portion.)
#After Moodle unpacks into the database (this may take a while, expect a white screen for a few moments), you now see the Moodle license page. Click 'Continue'.
#Next, Moodle will perform a check on all minimum requirements needed for Moodle to function correctly. If you are on a shared cPanel server, most or all of these checks should be installed and enabled. If they are, you should be prompted 'Your server environment meets all minimum requirements' and you can click 'Continue'. If not, please create a support ticket at http://support.hostek.com/ and we'll be glad to help.
#Moodle will now enable and install all plugins needed for Moodle to function. There should be 'Success' under every module listed here. If there is, navigate to http://yoursite.com/moodle/admin/ where yoursite.com is your own domain. Let this page load fully. Once the page has loaded, scroll to the bottom and click 'Upgrade Moodle Database now'.
#Next, click continue to set up the admin profile for Moodle. We strongly recommend changing the username from 'admin' to something more custom so that brute force attacks are deterred.
#The next step involves setting up your Moodle front page. From here forward, things should be relatively simple and custom for your site. If you ever have any questions, please do let us know via our 24/7 Live Chat, phone support or ticket system at http://support.hostek.com/.

 

==Updating Moodle==
To find out what the most recent version of Moodle is available you can check [http://download.moodle.org here]. 
You will need to check the documentation for the moodle version you are going to upgrade to to make sure you can upgrade straight to that version. 
For Example, you can only upgrade to Moodle version 2.4 if you are currently using Moodle version 2.2 or later.

===Moodle's 3 Key Steps to Upgrade===
#Back up everything to your site. This includes all your Files and your Database.
#You will replace the Existing Files with the New Versions Files.
#You will just need to Browse to your Moodles Installation Admin directory to initiate the upgrade process. Then you will follow the remaining prompts you receive.

===Current Moodle Upgrade Documentation Pages===
*For upgrading to [http://docs.moodle.org/27/en/Upgrading Moodle 2.7]
*For upgrading to [http://docs.moodle.org/26/en/Upgrading Moodle 2.6]
*For upgrading to [http://docs.moodle.org/25/en/Upgrading Moodle 2.5]
*For upgrading to [http://docs.moodle.org/24/en/Upgrading Moodle 2.4]
*For upgrading to [http://docs.moodle.org/23/en/Upgrading Moodle 2.3]
*For upgrading to [http://docs.moodle.org/22/en/Upgrading Moodle 2.2]
*For upgrading to [http://docs.moodle.org/21/en/Upgrading Moodle 2.1]
*For upgrading to [http://docs.moodle.org/20/en/Upgrading Moodle 2.0]
 

==Moodle Performance Tweaks & Tips==

Moodle can be made to run faster and in a better environment with some simple tweaks to the server that it is hosted on.

Here are some techniques we have tested, and found to be beneficial to Moodle installs.

===Setting up the environment===

There are a few changes that will need to be set up for Moodle to run in the environment that it was made for.

#Moodle is made to be hosted on a Linux environment. The application can run on windows, but this article currently only supports the tweaking of Moodle installs on Linux.
#Moodle wants you to make sure that hide PHP errors on the site when it is in production. "Enabling the PHP setting display_errors is not recommended on production sites because some error messages may reveal sensitive information about your server." 
#*Note: This would be turned off in the "php.ini." Since you want and easy to edit php.ini, You will want to use the "php.ini Settings" tool in cPanel for the Moodle site. Access the tool, and enable the use of a custom php.ini. Once that is done, change "Display Errors" to "Off" and save.
#Newer versions of Moodle will need PHP to be built in version 5.4. If you are not sure what version you are on, contact support and we will be happy to let you know this information.
#Turn on mod_deflate. This can be done by making sure that the Apache build you are in has the "Deflate" module selected, and then adding the following rules to the site's .htaccess file:
<ifModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml
</ifmodule>
*Enable mod_expires for the site. If this is not turned on for the server (It should be by default) then you will need to add it to the Apache build. One thing that has been noticed, is that this kind of caching can create problems during upgrades, you need to remove the caching directives one week before any upgrade. Add this within the .htaccess file.
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 seconds"
ExpiresByType text/html "access plus 1 seconds"
ExpiresByType image/gif "access plus 1 week"
ExpiresByType image/jpeg "access plus 1 week"
ExpiresByType image/png "access plus 1 week"
ExpiresByType text/css "access plus 1 week"
ExpiresByType text/javascript "access plus 1 week"
ExpiresByType application/x-javascript "access plus 1 week"
ExpiresByType text/xml "access plus 1 seconds"
</IfModule>

===Caching===

;Xcache, eAccelerator, and memcache are available on Linux server and can easily be implemented with rebuilding the Apache instance using the "EasyApache" tool in WHM.
:From our experience, and from outside sources, it seems that the caching system "APC" another caching application that works well with the Moodle environment. It is not included in the EasyApache builder, but it can be added to the PHP instance manually. Please contact support if you wish to use this plugin.

;Moodle has some of it's own caching tools that are usable as well. They can be found on the Moodle site.
:http://docs.moodle.org/24/en/Caching

;Moodle also has some performance recommendations of their own. They can also be found on the Moodle site.
:http://docs.moodle.org/23/en/Performance_recommendations

[[Category:Linux]]
[[Category:Linux VPS]]
[[Category:Tutorials]]

Enabling TLS on Common FTP Software

2014-08-19T16:16:29Z

DanielleM: /* Enabling TLS on Popular FTP Software */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Change the 'Logon Type' to 'Normal'.
# Enter your FTP account's 'Username' and 'Password'.
# Click 'OK' to save this connection.
# To connect, open 'Site Manager', or click the drop-down arrow next to the 'Site Manager' icon.
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.
 
[[File:fz_tls_b.png]]

===WinSCP===

# Create a new site in WinSCP, or edit your current one.
# Within the WinSCP Login box, choose 'FTP' as the File Protocol.
# Under 'Encryption:' select 'TLS Explicit encryption'.
# If your site is already set up with WinSCP, click 'Save' to make your changes permanent. Otherwise, simply fill in the information as per your welcome e-mail and click login.

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]

===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

New Connections:

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.

Existing Connections:

#Click 'Connections' > 'Site Manager'.
#Click 'Edit' next to the site you would like to modify.
#Click 'Advanced', then change the 'Server Type' dropdown to 'FTP/SSL (AUTH SSL)'.
#Click OK.

 

===Core FTP LE===

#Click File->Connect.
#Enter the following:
#*'''Site Name:''' Choose a name for the connection.
#*'''Host / IP / URL:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection:''' AUTH TLS.
#Click Connect.

 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.

Enabling TLS on Common FTP Software

2014-08-18T18:05:02Z

DanielleM: /* WS_FTP PRO */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Click 'OK', then you're done!
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.

===WinSCP===

# Create a new site in WinSCP, or edit your current one.
# Within the WinSCP Login box, choose 'FTP' as the File Protocol.
# Under 'Encryption:' select 'TLS Explicit encryption'.
# If your site is already set up with WinSCP, click 'Save' to make your changes permanent. Otherwise, simply fill in the information as per your welcome e-mail and click login.

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]

===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

New Connections:

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.

Existing Connections:

#Click 'Connections' > 'Site Manager'.
#Click 'Edit' next to the site you would like to modify.
#Click 'Advanced', then change the 'Server Type' dropdown to 'FTP/SSL (AUTH SSL)'.
#Click OK.

 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please submit a ticket via [https://support.hostek.com https://support.hostek.com] and we'd be glad to send it once more.

Enabling TLS on Common FTP Software

2014-08-11T23:35:20Z

DanielleM: /* DreamWeaver */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Click 'OK', then you're done!
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.

===WinSCP===

# Create a new site in WinSCP, or edit your current one.
# Within the WinSCP Login box, choose 'FTP' as the File Protocol.
# Under 'Encryption:' select 'TLS Explicit encryption'.
# If your site is already set up with WinSCP, click 'Save' to make your changes permanent. Otherwise, simply fill in the information as per your welcome e-mail and click login.

===Adobe Dreamweaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]
 
 
 
 

==Enabling TLS on Other FTP Software==

Below are additional guides on setting up a TLS connection for less common FTP software.

 
===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please send a request to support@hostek.com and we'd be glad to send it once more.

Enabling TLS on Common FTP Software

2014-08-11T23:27:11Z

DanielleM: /* Transmit */

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Click 'OK', then you're done!
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.

===WinSCP===

# Create a new site in WinSCP, or edit your current one.
# Within the WinSCP Login box, choose 'FTP' as the File Protocol.
# Under 'Encryption:' select 'TLS Explicit encryption'.
# If your site is already set up with WinSCP, click 'Save' to make your changes permanent. Otherwise, simply fill in the information as per your welcome e-mail and click login.

===DreamWeaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]
 
 
 
 
==Enabling TLS on Other FTP Software==

Below are additional guides on setting up a TLS connection for less common FTP software.

 
===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please send a request to support@hostek.com and we'd be glad to send it once more.

Enabling TLS on Common FTP Software

2014-08-11T23:24:14Z

DanielleM: Created page with "==Summary== In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. ..."

==Summary==
 
In today's world with a high magnitude of scripts automatically set to sniff for password data, there is a high demand for always using https on web sites. In the same way, we believe FTPS should be enforced for all FTP transactions.

In this wiki we go through the steps to enable FTPS/TLS on popular and less common FTP clients.

==Enabling TLS on Popular FTP Software==
 

===FileZilla===

# Open your FileZilla client, then click 'File'->'Site Manager'.
# In the Site Manager window, click 'New Site'.
# Input the FTP server information from your service's welcome e-mail.
# Under 'Encryption', select the 'Require Explicit FTP over TLS' option from the drop-down.
# Click 'OK', then you're done!
 
'''Please note:''' FileZilla does not trust any SSL certificate as valid automatically, even when the SSL certificate was signed by a trusted source (as our certificate is). The developers of FileZilla believed that it is up to individual users to decide if they will accept the certificate.

You can safely accept the the certificate warning message you receive.

===WinSCP===

# Create a new site in WinSCP, or edit your current one.
# Within the WinSCP Login box, choose 'FTP' as the File Protocol.
# Under 'Encryption:' select 'TLS Explicit encryption'.
# If your site is already set up with WinSCP, click 'Save' to make your changes permanent. Otherwise, simply fill in the information as per your welcome e-mail and click login.

===DreamWeaver===
Below is an example FTP over SSL/TLS setup for Dreamweaver version 6.0 and above. Dreamweaver versions prior to CS5.5 do not allow for secure FTP. If you are in this situation, you will be required to use an external FTP program such as FileZilla. 
 
[[File:DreamWeaverTLS.png]]
 
 
 
 
==Enabling TLS on Other FTP Software==

Below are additional guides on setting up a TLS connection for less common FTP software.

 
===FireFTP===

# Open up Firefox and click on Tools > FireFTP
# Click on the "Main" tab. Set up your FTP connection as usual:
#*'''Account Name:''' Choose a name for the connection.
#*'''Host:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
# Next, click on the Connection tab. Select the "Security" drop-down and then click "Auth TLS".

===SmartFTP===

#Click File > "New Connection"
#Set the "Protocol" Field to "FTPS (Explicit)"
#Fill in the following fields:
#*'''Host:''' URL of your site or the IP of the server
#*'''User:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel Password.[[#Additional Notes| (?) ]]
#Click 'OK' to connect.

===CyberDuck===

On the “Open Connection” dialog, select the “FTP-SSL (Explicit AUTH TLS)” option. See the image below: 
 
[[File:Cyberduck.png]]
 
 
 

===CuteFTP===

#On the main menu, click File > New > FTPS (SSL) Site.
#Under the 'General' tab, enter the following:
#*'''Label:''' Choose a name for the connection.
#*'''Host Address:''' Your server IP.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Login method:''' Normal.
#Click the 'Type' tab at the top when the above information has been filled in.
#Select 'FTP with TLS/SSL (AUTH TLS - Explicit)' on the 'Protocol Type' drop-down. Leave the rest of the information as default.
#Click 'Connect'. When prompted, accept the SSL certificate.
 

===FlashFXP===

#Click 'Sites' > 'Site Manager'
#Click 'New Site' at the bottom left of the new window.
#Choose a name for your site and click 'OK'.
#Under 'Connection Type:' select 'FTP using Explicit SSL (Auth TLS)'.
#In the 'Address' box, type the URL of your site or the IP of the server (either will work).
#Enter the following:
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click 'Apply', then 'Connect'.

===WISE-FTP===

#Click File > Connect.
#Click 'New Site' at the top-left.
#*'''Profile Name:''' Choose a name for the connection.
#*'''Server Address:''' URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#*'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#*'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#*'''Connection type:''' FTPES (explicit TLS/SSL).
#Any other information is optional.
 

===WS_FTP PRO===

#Click 'Connections' > 'New Connection...'
#Choose a name for the connection.
#Under 'Connection Type:', select 'FTP/SSL (AUTH SSL)'.
#In the 'Server Address:' field, enter in the URL of your site or the IP of the server.[[#Additional Notes| (?) ]]
#'''Username:''' Your cPanel username.[[#Additional Notes| (?) ]]
#'''Password:''' Your cPanel password.[[#Additional Notes| (?) ]]
#Click Finish.
 

===Transmit===

On the “FTP” tab, enter in the following: 
 
[[File:TransmitFTP.png]]
 
 
 

==Additional Notes==

Server information can be found in your Hostek.com welcome e-mail that you receive upon purchasing a service with Hostek. If you are missing this e-mail or any log-in information, please send a request to support@hostek.com and we'd be glad to send it once more.

File:TransmitFTP.png

2014-08-11T23:14:21Z

DanielleM: Enter in the information displayed in the image.

Enter in the information displayed in the image.

File:Cyberduck.png

2014-08-11T21:30:30Z

DanielleM: Match your information in the same format as exemplified here. Ensure you select the “FTP-SSL (Explicit AUTH TLS)” option.

Match your information in the same format as exemplified here. Ensure you select the “FTP-SSL (Explicit AUTH TLS)” option.