Hostek.com Wiki - User contributions [en]

How to Enable Robust Exceptions on a per Site basis in ColdFusion

2018-03-26T19:21:49Z

Codyw: Remove incorrect information.

In circumstances when you need to enable robust exceptions for a site, here are the steps needed:

You can configure this at the site level within your Application.cfc using the "this.EnableRobustException" property:

https://helpx.adobe.com/coldfusion/cfml-reference/application-cfc-reference/application-variables.html

Example "Application.cfc" file:

<cfcomponent>
<cfset this.Name = "My Application Name" />
<cfset this.EnableRobustException = "True" />
</cfcomponent>

TLS 1.2 Client Support

2018-03-01T17:10:22Z

Codyw: Java 6 TLSv1.2 support correction.

__FORCETOC__
Wiki for tracking which scripting engines support TLS 1.2 HTTP clients
and instructions on how to enable support by changing version, running
command, etc.

==PHP (Coming Soon)==

==ColdFusion==
===Which versions of Java support TLS 1.2?===
{| class="wikitable"
! style="text-align: center;" | Java Version
! style="text-align: center;" | TLS 1.2 Support
|-
| style="text-align: center;" | 6 and earlier
| style="text-align: center; background-color: Red;" | Not Supported
|-
| style="text-align: center;" | Java 7
| style="text-align: center; background-color: Yellow;" | Supported with
changes
|-
| style="text-align: center;" | Java 8
| style="text-align: center; background-color: Green;" | Supported
|}
'''Note that it's usually best to simply upgrade to Java 8.'''

===Which version of Java does ColdFusion use?===
See below for a table of the default Java version for each supported version of ColdFusion

{| class="wikitable"
! style="text-align: center;" | ColdFusion Version
! style="text-align: center;" | Default Java Version
|-
| style="text-align: center;" | ColdFusion 10
| style="text-align: center;" | Java 6
|-
| style="text-align: center;" | ColdFusion 11
| style="text-align: center;" | Java 7
|-
| style="text-align: center;" | ColdFusion 2016
| style="text-align: center;" | Java 8
|}

You can determine exactly which version of Java you're using with the below code. 
<syntaxhighlight lang="cfm">
<cfoutput>#CreateObject("java", "java.lang.System").getProperty("java.version")#</cfoutput>
</syntaxhighlight>
The output of this command should look like <code>1.7.0_51</code>. In this example, the Java version being used is Java 7 update 51.

===Shared Hosting===
On our shared servers, reach out to our support team if you have any questions regarding whether your site is ready for TLS 1.2. Most of our shared servers are already using Java 8, and we're upgrading the rest of them. We intend to have the upgrades done before any TLS 1.2 deadlines.

===VPS Hosting===
====Java 5 and earlier====
Please let our support team know that you would like your JVM upgraded to Java 8. Note that a major Java upgrade in ColdFusion requires a few changes that aren't well documented.

====Java 6 or Java 7====
TLSv1.2 can be enabled with an additional java argument in your jvm.config. 
<code>-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2</code> 
This argument will allow ColdFusion to use TLSv1.2, and will keep TLSv1 and TLSv1.1 available for communication with servers that don't yet support TLSv1.2.

'''Note that it's usually best to simply upgrade to Java 8.'''

====Java 8====
Java 8 supports TLS 1.2 without any changes.

==ASP.Net==

{| class="wikitable"
! style="text-align: center;" | Framework Version
! style="text-align: center;" | TLS 1.2 Support
|-
| style="text-align: center;" | 2.0-3.5
| style="text-align: center; background-color: Red;" | Not Supported
|-
| style="text-align: center;" | 4.0-4.5
| style="text-align: center; background-color: Yellow;" | Supported with
changes
|-
| style="text-align: center;" | 4.6
| style="text-align: center; background-color: Green;" | Supported
|}

===Framework 2.0-3.5===

No TLS 1.2 support. You must update to at least framework version 4.0

===Framework 4.0===

For ASP.Net 4.0, you can use either of the following two methods to
enable TLS 1.2 support:

'''NOTE:''' .Net Framework 4.5 or above must be installed for this to
work. However, your application can still target Framework 4.0.

* Method one - per application support

C# Code:
System.Net.ServicePointManager.SecurityProtocol |=
(SecurityProtocolType)768 | (SecurityProtocolType)3072;

* Method two - server-wide support via registry change - '''All of our
shared servers have this enabled'''

UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1

===Framework 4.5===

For ASP.Net 4.5, you can use either of the following two methods to
enable TLS 1.2 support:

* Method one - per application support

C# Code:
System.Net.ServicePointManager.SecurityProtocol |=
System.Net.SecurityProtocolType.Tls11 |
System.Net.SecurityProtocolType.Tls12;

* Method two - server-wide support via registry change - '''All of our
shared servers have this enabled'''

UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1

===Framework 4.6===

ASP.Net 4.6 supports TLS 1.2 without any changes.

Node.js on Windows

2017-12-28T21:24:45Z

Codyw: updated grammar, examples, troubleshooting, and outline

== Installing Node.js on a Windows VPS ==

=== Node.js ===

Note that if you have Node.js already installed or the executable already on your server, then you can skip this step.

#Download and install the Node.js installer (MSI) for Windows: https://nodejs.org/download/
#*Be sure to install the correct version that matches your server's bitness.
#Accept the defaults and finish installing Node.js.

You can confirm that you've successfully installed Node.js by following these steps.
#Launch a new command prompt(cmd).
#Run 'node --version' and it should print out the Node.js version installed on your server.

=== iisnode ===

If you want to host Node.js applications with IIS, then you'll need to use the "iisnode" IIS module.

#Download and install the latest stable iisnode module from: https://github.com/Azure/iisnode/releases
#*Be sure to install the correct version that matches your server's bitness.
#Add "list folder" permissions on c:\home for IIS_IUSRS. You can use the "Advanced" permissions control to apply the permission to "This folder only". '''Caution:''' If you're hosting multiple applications for various customers you might need to make further security considerations.
#*This assumes that you're using the default site path of 'C:\Home\domain.tld' that we configure on Windows VPS servers. If you have a custom setup, then you'll need to be sure that the 'IIS_IUSRS' group has "list folder" permissions for all directories leading up to your site's webroot.

== Running Your First Node.js Application ==

=== Configure your site for iisnode ===

For your Node.js application to work with IIS, you will need to configure the site for use with iisnode. You can accomplish this with some web.config options, or a web.config option as well as a .yml config file. For the sake of simplicity and getting started quickly, we've provided a couple of examples below.

The only changes you'll probably need to make in the example yaml config are the paths to the node.exe executable and the interceptor.

'''web.config:'''

<syntaxhighlight lang="xml">
<configuration>
<system.webServer>

<handlers>
<add name="iisnode" path="node_app.js" verb="*" modules="iisnode" />
</handlers>

<rewrite>
<rules>
<rule name="nodejs">
<match url="(.*)" />
<conditions>
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
</conditions>
<action type="Rewrite" url="/node_app.js" />
</rule>
</rules>
</rewrite>

<security>
<requestFiltering>
<hiddenSegments>
<add segment="node_modules" />
<add segment="iisnode" />
</hiddenSegments>
</requestFiltering>
</security>

</system.webServer>
</configuration>
</syntaxhighlight>

'''iisnode.yml:'''

<syntaxhighlight lang="yaml">
# The optional iisnode.yml file provides overrides of
# the iisnode configuration settings specified in web.config.

node_env: production
nodeProcessCommandLine: "C:\Program Files\nodejs\node.exe"
interceptor: "C:\Program Files\iisnode\interceptor.js"
nodeProcessCountPerApplication: 1
maxConcurrentRequestsPerProcess: 1024
maxNamedPipeConnectionRetry: 24
namedPipeConnectionRetryDelay: 250
maxNamedPipeConnectionPoolSize: 512
maxNamedPipePooledConnectionAge: 30000
asyncCompletionThreadCount: 0
initialRequestBufferSize: 4096
maxRequestBufferSize: 65536
watchedFiles: *.js;iisnode.yml
uncFileChangesPollingInterval: 5000
gracefulShutdownTimeout: 60000
loggingEnabled: true
logDirectory: iisnode
debuggingEnabled: true
debuggerPortRange: 5058-6058
debuggerPathSegment: debug
maxLogFileSizeInKB: 128
maxTotalLogFileSizeInKB: 1024
maxLogFiles: 20
devErrorsEnabled: false
flushResponse: false
enableXFF: false
promoteServerVars:
</syntaxhighlight>

=== Create your application ===

For the most part, your Node.js application should work as expected. It's important to note that there are some differences. For example, the express .listen() method works differently with iisnode apps, which you can see later in the wiki. If necessary, you can find a handful of example applications in the iisnode github repo: https://github.com/Azure/iisnode/tree/master/src/samples/

In our example, we've created a very simple express application. You'll need to use npm to install the "express" node module. To do this, navigate to your site's web root in command prompt or powershell and then run the following command:

<pre>npm install express --save</pre>

Here is our example application:

'''node_app.js:'''

<syntaxhighlight lang="javascript">
var express = require('express');
var app = express();
app.get('/', function (req, res) {
res.send('Hello World!');
});
// This is REQUIRED for IISNODE to work
app.listen(process.env.PORT, () => {
console.log('listening')
})
</syntaxhighlight>

If you browse to your site, you should see the text "hello world".

If you need a simpler example that requires no 3rd party modules, then you can use this one from the iisnode github repo: https://github.com/Azure/iisnode/blob/master/src/samples/helloworld/hello.js

== Troubleshooting Your Node.js Application ==

If you followed this wiki, then logging should be enabled for your application. The standard output and standard error messages should be logged to their own respective log files in the "iisnode" directory.

=== Common Errors ===

'''Error: EPERM: operation not permitted, lstat 'C:\home''''

This means that your site's web user doesn't have permission to list the folder contents. Double-check the permissions of your site's web user and make sure that it can list the contents of all directories leading up to your site's web root.

[[Category:Tutorials]]
[[Category:Windows-VPS]]

Node.js

2017-12-28T21:23:35Z

Codyw: Codyw moved page Node.js to Node.js on Windows: Reduced scope to Windows only.

#REDIRECT [[Node.js on Windows]]

Node.js on Windows

2017-12-28T21:23:30Z

Codyw: Codyw moved page Node.js to Node.js on Windows: Reduced scope to Windows only.

== Installing Node.js on Windows VPS ==

#Download and install the Node.js installer (MSI) for Windows: https://nodejs.org/download/
#*Be sure to install the version with the correct bitness of your server. Note that if you have Node.js already installed or the executable already on your server you can skip this step, although you might need to set additional permissions.
#Download and install the iisnode module from: https://github.com/Azure/iisnode/downloads
#Add "list folder" permissions on c:\home for IIS_USERS. Caution if your hosting multiple applications for various customers you might need to make further security considerations.

=== Running Your Node.js Application ===

You should have a domain already created using our control panel WCP. Copy the Node.js application to a the destination folder, where you want to run it. For example: your-domain.com/node, will likely be in

<pre>
c:\home\your-domain.com\wwwroot\node
</pre>

You will need to create a web.config and or iisnode.yml file (or modify the existing), see the next section for specifics.

=== Modify iisnode web.config settings ===

'''If you followed the steps to install we suggest getting the example web.config and iisnode.yml from: C:\Program Files\iisnode\www\configuration'''

NOTE: The iisnode.yml file overrides any iisnode specific settings except for the handler and entrypoint which you are required to include in the web.config.

<pre>
<handlers>
<add name="iisnode" path="hello.js" verb="*" modules="iisnode" />
</handlers>
</pre>

==== Example web.config ====

The only thing you'll need to change in this web.config example is moving the path to the node.exe executable and the interceptor. The nice thing about the web.config provided by the example is it details all the available settings. Here's an example web.config:

<pre>
<configuration>
<system.webServer>



<handlers>
<add name="iisnode" path="hello.js" verb="*" modules="iisnode" />
</handlers>

<iisnode
nodeProcessCommandLine=""%programfiles%\nodejs\node.exe""
interceptor=""%programfiles%\iisnode\interceptor.js""
node_env="%node_env%"
nodeProcessCountPerApplication="1"
maxConcurrentRequestsPerProcess="1024"
maxNamedPipeConnectionRetry="100"
namedPipeConnectionRetryDelay="250"
maxNamedPipeConnectionPoolSize="512"
maxNamedPipePooledConnectionAge="30000"
asyncCompletionThreadCount="0"
initialRequestBufferSize="4096"
maxRequestBufferSize="65536"
watchedFiles="*.js;iisnode.yml"
uncFileChangesPollingInterval="5000"
gracefulShutdownTimeout="60000"
loggingEnabled="true"
logDirectory="iisnode"
debuggingEnabled="true"
debugHeaderEnabled="false"
debuggerPortRange="5058-6058"
debuggerPathSegment="debug"
maxLogFileSizeInKB="128"
maxTotalLogFileSizeInKB="1024"
maxLogFiles="20"
devErrorsEnabled="true"
flushResponse="false"
enableXFF="false"
promoteServerVars=""
configOverrides="iisnode.yml"
/>

</system.webServer>
</configuration>
</pre>

==== iisnode.yml for configuration ====

[http://tomasz.janczuk.org/2012/05/yaml-configuration-support-in-iisnode.html About the iisnode.yml configuration it's importance.]

[[Category:Tutorials]]
[[Category:Windows-VPS]]

MS Access

2017-12-16T23:01:46Z

Codyw: Add new MS Access wiki

== Do you support MS Access? ==

Yes, you can use MS Access datasources on any of our ColdFusion/Windows hosting plans. Our WCP(Windows Control Panel) has full support for MS Access and will allow you to create and manage MS Access datasources as needed.

== What you should know about MS Access. ==

The first and most important thing to know about MS Access is that it's not a production database engine, and should not be considered a suitable choice for a production environment. This essentially means that you will likely experience service or site crashes or hangs when using MS Access. Many legacy ColdFusion apps use MS Access as the datasource.

At Hostek we encourage our customers to use whatever they're most comfortable with. However, it's important to understand that you '''will''' experience issues when relying on MS Access as your site's datasource. MS Access has a use case in the desktop user space, but it was never meant to be used on a server. Additionally, Microsoft stated in a release that has since been removed (due to article age):

"Microsoft Access was not designed for server use. When multiple, concurrent users make requests of a Microsoft Access database (or database driver), unpredictable results may occur."

For these reasons, we strongly discourage the use of MS Access as the database for your ColdFusion application(s). You may be surprised how easy it is to switch to a better database engine.

== Converting your MS Access database. ==

If you're currently using an MS Access database, then we recommend switching to either MSSQL or MySQL. Since MS Access is a Microsoft product, you may find that MSSQL is much more similar in usage and syntax. There are free tools available online that will allow you to convert your MS Access datasource to either MSSQL or MySQL.

[http://www.bullzip.com/products/a2s/info.php Access to MSSQL]

[http://www.bullzip.com/products/a2m/info.php Access to MySQL]

Please note that you may need to test compatibility with your new database engine of choice. In some rare cases you'll have to make changes to your SQL query code itself in order to work with the new database. If any of your SQL queries need to be updated, you will need to do that yourself or consult with your ColdFusion developer.

How to select different ColdFusion versions

2017-06-21T17:25:17Z

Codyw: create cf version selector wiki

'''Please note that this tool is only temporarily available for testing scheduled major ColdFusion upgrades.'''

In this wiki, we’ll illustrate how to change the ColdFusion version of your site by using the “ColdFusion Version Selector” tool in WCP. 

# Login to WCP. You can learn about how to login to WCP in [https://wiki.hostek.com/WCP#How_To_Login_To_My_WCP_Control_Panel this linked wiki].
# If you have more than one domain in your account, click the “Hosted Domains” dropdown at the top-right of the screen, and then select the domain you would like to change the CF version for.
# In the “ColdFusion” tools section, click on the “ColdFusion Version Selector” tool.
# Next to the domain or subdomain that you would like to change the ColdFusion version for, click on the “manage” button.
# In the “ColdFusion Version” dropdown selector, select the version of ColdFusion you would like to switch to.
# Click the “save” button when you’re satisfied with your selection.

See below for a recording of the process.

[[File:change-cf-version.gif]]

File:Change-cf-version.gif

2017-06-21T17:21:52Z

Codyw: how to change ColdFusion version in WCP

how to change ColdFusion version in WCP

TLS 1.2 Client Support

2017-03-16T21:27:49Z

Codyw: /* ColdFusion */

__FORCETOC__
Wiki for tracking which scripting engines support TLS 1.2 HTTP clients
and instructions on how to enable support by changing version, running
command, etc.

==PHP (Coming Soon)==

==ColdFusion==
===Which versions of Java support TLS 1.2?===
{| class="wikitable"
! style="text-align: center;" | Java Version
! style="text-align: center;" | TLS 1.2 Support
|-
| style="text-align: center;" | 5 and earlier
| style="text-align: center; background-color: Red;" | Not Supported
|-
| style="text-align: center;" | Java 6 or Java 7
| style="text-align: center; background-color: Yellow;" | Supported with
changes
|-
| style="text-align: center;" | Java 8
| style="text-align: center; background-color: Green;" | Supported
|}
'''Note that it's usually best to simply upgrade to Java 8.'''

===Which version of Java does ColdFusion use?===
See below for a table of the default Java version for each supported version of ColdFusion

{| class="wikitable"
! style="text-align: center;" | ColdFusion Version
! style="text-align: center;" | Default Java Version
|-
| style="text-align: center;" | ColdFusion 10
| style="text-align: center;" | Java 6
|-
| style="text-align: center;" | ColdFusion 11
| style="text-align: center;" | Java 7
|-
| style="text-align: center;" | ColdFusion 2016
| style="text-align: center;" | Java 8
|}

You can determine exactly which version of Java you're using with the below code. 
<syntaxhighlight lang="cfm">
<cfoutput>#CreateObject("java", "java.lang.System").getProperty("java.version")#</cfoutput>
</syntaxhighlight>
The output of this command should look like <code>1.7.0_51</code>. In this example, the Java version being used is Java 7 update 51.

===Shared Hosting===
On our shared servers, reach out to our support team if you have any questions regarding whether your site is ready for TLS 1.2. Most of our shared servers are already using Java 8, and we're upgrading the rest of them. We intend to have the upgrades done before any TLS 1.2 deadlines.

===VPS Hosting===
====Java 5 and earlier====
Please let our support team know that you would like your JVM upgraded to Java 8. Note that a major Java upgrade in ColdFusion requires a few changes that aren't well documented.

====Java 6 or Java 7====
TLSv1.2 can be enabled with an additional java argument in your jvm.config. 
<code>-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2</code> 
This argument will allow ColdFusion to use TLSv1.2, and will keep TLSv1 and TLSv1.1 available for communication with servers that don't yet support TLSv1.2.

'''Note that it's usually best to simply upgrade to Java 8.'''

====Java 8====
Java 8 supports TLS 1.2 without any changes.

==ASP.Net==

{| class="wikitable"
! style="text-align: center;" | Framework Version
! style="text-align: center;" | TLS 1.2 Support
|-
| style="text-align: center;" | 2.0-3.5
| style="text-align: center; background-color: Red;" | Not Supported
|-
| style="text-align: center;" | 4.0-4.5
| style="text-align: center; background-color: Yellow;" | Supported with
changes
|-
| style="text-align: center;" | 4.6
| style="text-align: center; background-color: Green;" | Supported
|}

===Framework 2.0-3.5===

No TLS 1.2 support. You must update to at least framework version 4.0

===Framework 4.0===

For ASP.Net 4.0, you can use either of the following two methods to
enable TLS 1.2 support:

'''NOTE:''' .Net Framework 4.5 or above must be installed for this to
work. However, your application can still target Framework 4.0.

* Method one - per application support

C# Code:
System.Net.ServicePointManager.SecurityProtocol |=
(SecurityProtocolType)768 | (SecurityProtocolType)3072;

* Method two - server-wide support via registry change - '''All of our
shared servers have this enabled'''

UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1

===Framework 4.5===

For ASP.Net 4.5, you can use either of the following two methods to
enable TLS 1.2 support:

* Method one - per application support

C# Code:
System.Net.ServicePointManager.SecurityProtocol |=
System.Net.SecurityProtocolType.Tls11 |
System.Net.SecurityProtocolType.Tls12;

* Method two - server-wide support via registry change - '''All of our
shared servers have this enabled'''

UseStrongCrypto.reg file
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

OR

Command Prompt (cmd):
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
/v SchUseStrongCrypto /t REG_DWORD /d 1

OR

PowerShell:
Set-ItemProperty -Path
HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1
Set-ItemProperty -Path
HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 -Name
SchUseStrongCrypto -Value 1

===Framework 4.6===

ASP.Net 4.6 supports TLS 1.2 without any changes.

Bulk Mail

2016-11-07T16:30:52Z

Codyw: /* Ordering */

__FORCETOC__
==Bulk Email==
===Notices===
#The Bulk Email option is NOT for sending spam.
#It is for sending to legitimate customers and subscribers.
#It is NOT to be used to send to purchased lists.

===Pricing===
*Pricing for the Bulk Mail service.
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
! scope="col" style="background-color:lightgrey;" | Emails Per Month
! scope="col" align="center" style="background-color:lightgrey;" | Equals
! scope="col" style="background-color:lightgrey;" | Pricing
|-
! scope="row" | #1 - 25,000*
! scope="row" align="center" | =
| $10/month add-on
|-
! scope="row" |#25,001 - 50,000
! scope="row" align="center" | =
| $20/month add-on
|-
! scope="row" |#50,001 - 100,000
! scope="row" align="center" | =
| $35/month add-on
|-
! scope="row" |#100,001 - 200,000
! scope="row" align="center" | =
| $50/month add-on
|-
! scope="row" |#200,001 - 400,000
! scope="row" align="center" | =
| $75/month add-on
|-
! scope="row" |#400,001 - 750,000
! scope="row" align="center" | =
| $90/month add-on
|-
! scope="row" |#750,001 - 1,000,000
! scope="row" align="center" | =
| $110/month add-on
|-
! scope="row" |#1,000,001+
! scope="row" align="center" | =
| Contact sales [https://support.hostek.com/ here]
|}

* NO additional fee for 1 - 25,000 emails per month. The purpose of this pricing is if you do not want the delivery of the emails to be throttled (ie, 100 per hour).

===Ordering===
'''[https://cp.hostek.com/cart.php?a=add&pid=443 CLICK HERE TO ORDER A BULK MAIL ACCOUNT]''' and select the level you need.
*'''Please note''': If you have ''multiple domains'' '''OR''' if want ''more than one Bulk Mail Account'' you will need to order a separate service for each one.

==Bulk Email In Outlook==

===For new accounts in Outlook, follow these steps:===
# Add a new account under File--->Add New Account. Be sure your bulk account has been added to your actual mail server in Smartermail/Cpanel
# Select Manually configure server settings and click next
# Select Internet E-mail and click next
# Enter the name and the bulk e-mail address
# Select the account type you want for the incoming mail that's set up on Smartermail (even if the account won't receive incoming mail this needs to be done or Outlook setup cannot complete)
# Input the incoming mail server (typically mail.yourdomainname.com)
# Input the outgoing mail server which is bulkmail1.ezhostingserver.com
# Enter the full e-mail address for the username
# Enter the password you set for the user in Smartermail/Cpanel
# Click on More Settings
# Click on Outgoing Server
# Check the "My Outgoing Server Requires authentication" box
# Select "Log On Using" enter in the password you have set for your user
# Click on the "Advanced" tab
# Change the Outgoing Server port from 25 to 26
# Click OK and then Next

===For existing accounts in Outlook, follow these steps:===
# Click on File--->Account Settings
# Double-Click on your account
# Change the outgoing mail server to bulkmail1.ezhostingserver.com
# Click on More Settings
# Click on Outgoing Server
# Check the "My Outgoing Server Requires authentication" box
# Select "Log On Using" enter in the bulk username and password that was e-mailed to you here
# Click on the "Advanced" tab
# Change the Outgoing Server port from 25 to 26
# Click OK and then Next
*Following these steps will successfully set up your Outlook e-mail account to use the Bulk Mail service you purchased for sending e-mails.

==Bulk Email in SmarterMail==

===Setting up Bulk Email in SmarterMail===
#Login into '''Webmail''' (e.g. <nowiki>http://mail.yourawesomedomain.com/</nowiki>
#Go to '''Settings''' (Gears Icon)
#Open the '''Advanced Settings''' section
#Click on '''SMTP Accounts'''
#Click on '''New'''
#Fillout the form with the information you were provided after purchasing the Bulk Email User Account. Below is an Example:
##'''Server Address:''' bulkmail1.ezhostingserver.com
##'''Port:''' 25
##'''Display Name:''' example@yourawesomedomain.com
##'''Email Address:''' example@yourawesomedomain.com
##'''Username:''' example_yourawesomedomain_com
##'''Password:''' ******************
##'''Encryption:''' None
##'''Authentication Enabled:''' Yes
#Click '''Save'''
===Using the Bulk Email in SmarterMail===
#Go to the '''Mail''' section
#Click on '''New''' [to compose a new message]
#You'll notice that the '''From:''' Address has a '''drop-down menu''' now, '''click''' on this and choose the Email Address which you set up in the SMTP Accounts.
##If there are duplicates you choose the closest one to the bottom.
#Send your message(s) as you normally would.
*Note: If you have a MailingList, you'll simply send '''TO''' that MailingList's ID. (e.g. clients@yourawesomedomain.com)

[[Category:SmarterMail]]
[[Category:CPanel-Mail]]

Git

2016-05-20T18:29:20Z

Codyw: Created page with "==VPS== '''Can I use Git on my VPS?''' Yes, you can install and use Git on your VPS. Hostek doesn't actively support Git, but we're happy to look into any issues you may have..."

==VPS==
'''Can I use Git on my VPS?'''

Yes, you can install and use Git on your VPS. Hostek doesn't actively support Git, but we're happy to look into any issues you may have.

If you need assistance with opening a port or making any changes on your server to allow Git to work, please open a support ticket at https://support.hostek.com.

==Shared==
'''Can I use Git on my shared hosting package?'''

No, we don't currently support or facilitate the use of Git on our shared hosting packages.

There are several 3rd party services available to manage your code with Git and deploy via FTP.

External Mail Server

2016-05-11T21:45:21Z

Codyw: /* cPanel */ correct steps to set email route to remote mail exchanger

To have emails delivered to an external mail server.

==cPanel==
In cPanel you'll need to follow these steps:

# Log into cPanel and click '''"MX Entry"'''
# Select your domain from the drop down menu
# Click the button for '''"Remote Mail Exchanger"'''
# Click the '''"Change"''' button to confirm your changes

==WCP==
In WCP you'll need to follow these steps:

# Log into WCP and click '''"DNS Editor"'''
# Click the edit button next to the MX record you want to change
# Enter the server IP for your remote email server
# Click '''"Save"'''

[[Category:Control_Panels]]
[[Category:Email]]