IIS 7.5 and IIS 8.0 European Hosting

BLOG about IIS 7.5 Hosting, IIS 8.0 Hosting and Its Technology - Dedicated to European Windows Hosting Customer

European Full Trust ASP.NET Hosting - UK :: How to Fix The System.SecurityException error occurs when a SocketTools

clock October 31, 2014 08:27 by author Scott

When you application requires Full Trust permission and your hosting provider provider doesn’t offer Full Trust permission, then your application won’t work. This is an error message that you might find if your hosting provider doesn’t support Full Trust

“The System.SecurityException error occurs when a SocketTools .NET component is used with an ASP.NET application, displaying the error message: The application attempted to perform an operation not allowed by the security policy.”

More Information

This error indicates that the server is not configured for full trust. The SocketTools .NET components require unrestricted access to specific system resources such as the networking subsystem and system registry. To grant full trust to your ASP.NET application, you need to modify the web.config file to include the following:

<location allowOverride="true">
    <trust level="Full" originUrl=".*"/>

Note that setting the code access security level to full trust enables the application to call native code, access system services, open database connections and access the registry and modify files outside of the server’s virtual directory.

If your hosting provider doesn’t provide full trust, then above code won’t work too. So, you need to find hosting provider that support Full Trust.


IIS 8 Hosting UK - HostForLIF.eu :: Adding Your FTP Site on IIS 8

clock October 29, 2014 09:37 by author Peter

In this article you'll learn the way to add a new FTP site on IIS 8. Before going through this article make sure that FTP and IIS are installed on your system. If you wish to find out a way to install IIS then you'll go through this article: Installing IIS. Now allow us to see the procedure needed to add a new FTP site on IIS 8.

Step 1. First of all Open the Administrative Tools from the START Menu.

Now within the Administrative Tools, there is several options will be available within the list among that you need to choose the IIS Manager and so double-click on that to open it.

Step 2. Now the IIS Manager Window are going to be opened. On the left hand side you'll see a pane named Connection Pane, within the Connection Pane a Server node are going to be available, you need to expand this Server node and so right-click on your Server name and so choose the option named Add FTP site.

Step 3. A new form are going to be opened. Now you need to give the site information that you just that you aiming to create, 1st give the name for this New site and then give the Physical Path by clicking on the Browse Button. This physical path can verify a folder wherever the Content Directory are going to be created.

After select the Name and Physical Path click on the "Next" button.

Step 4. Next, named as Binding and SSL Settings. You must fill the IP Address. Click on the drop down Button and so choose the IP Address, if you do not have any IP Address then you'll choose an option available named All Unassigned. After providing the IP Address, give the Port number.

Step 5. On an equivalent page Uncheck the start FTP site automatically. In SSL 3 options are going to be available, among these choices I selected  the third option, in alternative words need SSL and then I give the SSL Certificate. After give all that information click on "Next".

Step 6. On the next page Authentication and Authorization is to be provided. On Authentication Permitted if you want to permit all the users then you'll check the "Anonymous" otherwise you'll check the "Basic".

In the Authorization I permit all users authorization to Permitted and Write, you'll provide no matter authorization that satisfies your needs. After providing all the information, click on the "Finish" button to create the site.

Step 7. Now in the Sites you'll see that the new website is available under the IIS Default web site.

IIS 7.5 Hosting - HostForLIFE.eu :: Application Pool Idle Time-out Settings on IIS

clock October 23, 2014 09:48 by author Peter

Whether you host in-house or with a managed Windows hosting provider, if you self-administer a web server it's sensible to understand that by default IIS 7.5 sets application pools to “time-out” when twenty minutes of inactivity. therefore if you don’t have a visitor to your website within twenty minutes the application pool can shut down those system resources. Then the next time a request comes into the site IIS7 can automatically restart the application pool and serve the requested pages.

This is an excellent way to preserve resources since each running application pool will place a certain quantity of overhead on the system. But, it conjointly implies that the primary request – the one that causes the application pool to restart – is incredibly slow. it's slow as a result of the method literally must begin, then load the desired assemblies (like .NET) then load the requested pages. betting on the size and complexity of your application, this would possibly simply be a couple of seconds or it'd take 30+ seconds (during which time a user would possible quit and move on to a different site).

If you wish to increase the length of the time-out setting, simply change it from the default of twenty to however several minutes you wish. you can also modify the setting to zero (zero) which effectively disables the timeout so the application pool can never shut down due to being idle.

To make this change, open Server Manager; Expand the Roles node; Expand the web Server (IIS) node. Then click on the web Server (IIS) node; Expand the node along with your local server name; and click on the application Pools icon. You’ll then see a list of the application pools that are defined on your server. within the right-hand pane you’ll see an option for Advanced Settings -> click that.

Once you see the Advanced Settings dialog box simply look for the Idle Time-out (minutes) property; click wherever the default “20″ is, and change it to no matter value you prefer.

This is only 1 of the many settings that may impact the performance, uptime, and functioning of your web site. If you don’t have the time or interest in learning and maintaining the various settings for a secure high-performing web server, you would possibly need to consider a totally managed windows hosting solution and let a trained and experienced administrator take care of the work for you.

IIS 8.0 Hosting UK - HostForLIFE.eu :: Testing Web Site using SSL on Localhost (IIS)

clock October 22, 2014 06:49 by author Peter

SSL (Secure Socket Layer) is a cryptographic protocol developed by Netscape to supply communications security on the net. cryptographic technology uses 2 keys to encrypt data, one for public (public key) and another for recipient (secret key). SSL enabled websites communicate with a web server employing a security channel (secret key) that prevents tempering, eavesdropping (or merely say hacking). SSL is presumably used for a login section, payment system, on-line banking industry etc that's very sensitive info for a company or person. after we enable SSL for a web site the address can begin with "https://" (indicating hypertext Transfer Protocol Secure) rather than "http://".

To test this, you ought to have IIS installed. there's no need for further software like Visual Studio or any other web site development kit because only one hypertext markup language file can be tested. Follow the steps to enable SSL on Windows Server 2012 operating system; another operational System may have a slight distinction.

1. Open the IIS Manager and choose root computer name -> and double click on "Server Certifications". look at the image given below.

2. Now within the window that seems you'll find "Server Certificates" that are already installed. No problem if another one already exists, I recommend to delete all by choosing each and build a new one. If you're not using your system to host an expert web site then, delete all. Look at the correct panel; you'll find "Create Self-Signed Certificate"; click on it. You'll be prompted to enter the friendly name for SSL and click on OK button.

3. After clicking on the OK button you'll realize a new SSL entry. Currently navigate to "Site List" and right-click on that to choose the "Edit Binding" option. Consider the image given below.

4. When you click on "Edit Binding", you'll get a new window requesting a protocol type. There is also 3 or four items, in my example there's only 1 by default that's "http". No downside if you've got many more. at least one ought to be there. now click on the "Add" button and within the window that appears choose the "Type" to "https" and "SSL Certificate" to "yourSSLname". after you are done, i recommend to delete all other protocol types, only keep https. shut the little window listing protocols at the end.

5. Now everything is configured and enabled for you. Let's take a look at it. Please note I only have the only protocol "https". Since browsers by default use http you've got to use here https while requesting via browser.

European HostForLIFE.eu Proudly Launches PrestaShop 1.6 Hosting

clock October 16, 2014 09:21 by author Peter

HostForLIFE.eu, a leading Windows web hosting provider with innovative technology solutions and a dedicated professional services team, today announced the support for PrestaShop 1.6 Hosting plan due to high demand of PrestaShop 1.6 users in Europe. HostForLIFE.eu hosts its servers in top class data centers that is located in Amsterdam, London and Seattle (US) to guarantee 99.9% network uptime. All data center feature redundancies in network connectivity, power, HVAC, security, and fire suppression. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee.

PrestaShop 1.6 is a free and open-source e-commerce web application, committed to providing the best shopping cart experience for both merchants and customers. It is written in PHP, is highly customizable, supports all the major payment services, is translated in many languages and localized for many countries, is fully responsive (both front- and back-office), etc. PrestaShop 1.6 offers new and improved navigation elements making navigating your online shop easier and more effective than ever.

PrestaShop 1.6 presents a comprehensive, intuitive user administration panel, and gives you hundreds of standard functions that can be adapted or personalized in order to respond to all of customer needs. The front office template on PrestaShop 1.6 is now mobile responsive, allowing customer online shop to display perfectly when accessed from a mobile and tablet device.

At the forefront of the latest innovative web technology, PrestaShop 1.6 integrates with Bootstrap 3.0, FontAwesome, Sass Compass and D3 Data Driven Documents. Online Shopping has never been so technologically brilliant. A unique e-commerce feature you will only find in PrestaShop 1.6, Net Profit Margin is automatically updated in real-time.

Further information and the full range of features PrestaShop 1.6 Hosting can be viewed here http://hostforlife.eu/European-PrestaShop-16-Hosting

About HostForLIFE.eu
HostForLIFE.eu is an European Windows Hosting Provider which focuses on the Windows Platform only. HostForLIFE.eu deliver on-demand hosting solutions including Shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes.

HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.microsoft.com/web/hosting/HostingProvider/Details/953). Their service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries. Besides this award, they have also won several awards from reputable organizations in the hosting industry and the detail can be found on their official website.

European IIS 8.5 Hosting - UK :: Hosting node.js in IIS

clock October 15, 2014 07:40 by author Scott

In this post, I will discuss about hosting node.js application in IIS on Windows using iisnode project. OK, let’s begin.

First thing you need to do is install iisnode project side to get the module and samples installed on your Windows box with IIS7 enabled. The hello world sample consists of two files: hello.js and web.config.
This is the hello.js file from the helloworld sample:

var http = require('http');

http.createServer(function (req, res) {
    res.writeHead(200, {'Content-Type': 'text/plain'});
    res.end('Hello, world! [helloworld sample]');

You will notice that the only difference between this code and the hello world sample from the front page of http://nodejs.org is in the specification of the listening address for the HTTP server. Since IIS controls the base address for all HTTP listeners, a node.js application must use the listen address provided by the iisnode module through the process.env.PORT environment variable rather than specify its own.


The web.config file is required to instruct IIS that the hello.js file contains a node.js application. Otherwise IIS would consider this file to be client side JavaScript and serve it as static content. The web.config designates hello.js as a node.js application by scoping the registration of the handler in the iisnode module to that file only:

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

This handler registration allows the same web site to contain other *.js files (e.g. jQuery libraries) that IIS will continue serving as static files.

The Advantages Using iisnode

WebSocket Support

As of version 0.2.x, iisnode supports hosting Websocket applications in IIS 8 on Windows Server 2012 and Windows 8. You can use any standard node.js modules that implement the Websocket protocol, including socket.io.

Scalability on multi-core servers

For every node.js application (e.g. hello.js above), iisnode module can create many node.exe process and load balance traffic between them. The nodeProcessCountPerApplication setting controls the number of node.exe processes that will be created for each node.js application. Each node.exe process can accommodate a configurable number of concurrent requests (maxConcurrentRequestsPerProcess setting). When the overall concurrent active request quota has been reached for an application (maxConcurrentRequestsPerProcess * nodeProcessCountPerApplication ), the iisnode module starts rejecting new HTTP requests with a 503 (Server Too Busy) status code. Requests are dispatched across multiple node.exe processes serving a node.js application with a round-robin load balancing algorithm.


Whenever the JavaScript file with a node.js application changes (as a result of a new deployment), the iismodule will gracefully upgrade to the new version. All node.exe processes running the previous version of the application that are still processing requests are allowed to gracefully finish processing in a configurable time frame (gracefulShutdownTimeout setting). All new requests that arrive after the JavaScript file has been updated are dispatched to a new node.exe process that runs the new version of the application. The watchedFiles setting specifies the list of files iisnode will be watching for changes.

Changes in the JavaScript file are detected regardless if the file resides on a local file system or a UNC share, but the underlying mechanisms are different. In case of a local file system, an OS level directory watching mechanism is used which provides low latency, asynchronous notifications about file changes. In case of files residing on a UNC share, file timestamps are periodically polled for changes with a configurable interval (uncFileChangesPollingInterval setting).

Integrated debugging

With iisnode integrated debugging you can remotely debug node.js application using any WebKit-enabled browser.

Access to logs over HTTP

To help in ‘console.log’ debugging, the iisnode module redirects output generated by node.exe processes to stdout or stderr to a text file. IIS will then serve these files as static textual content over HTTP. Capturing stdout and stderr in files is controlled with a configuration setting (loggingEnabled). If enabled, iisnode module will create a per-application special directory to store the log files. The directory is located next to the *.js file itself and its name is is specifed with the logDirectoryName setting (by default “iisnode”). The directory will then contain several text files with log information as well as an index.html file with a simple list of all log files in that directory. Given that, the logs can be accessed from the browser using HTTP: given a node.js application available at http://mysite.com/foo.js, the log files of the application would by default be located at http://mysite.com/iisnode/index.html.

The logDirectoryName is configurable to allow for obfuscation of the log location in cases when the service is publicly available. In fact, it can be set to a cryptographically secure or otherwise hard to guess string (e.g. GUID) to provide a pragmatic level of logs privacy. For example, by setting logDirectoryName to ‘A526A1F2-4E22-4488-B930-6A71CC7649CD’ logs would be exposed at http://mysite.com/A526A1F2-4E22-4488-B930-6A71CC7649CD/index.html.

Log files are not allowed to grow unbounded. The maxLogFileSizeInKB setting controls the maximum size of an individual log file. When the log grows beyond that limit, iisnode module will stop writing to that file and create a new log file to write to. To avoid unbounded growth of the total number of log files in the logging directory, iisnode enforces two additional quotas. The maxLogFiles setting controls the maximum number of log files that are kept. The maxTotalLogFileSizeInKB controls the maximum total size of all logs files in the logging directory. Whenever any of the quotas are exceeded, iisnode will remove any log files not actively written to in the ascending order of the last write time.

Note that this design of the logging feature allows the node.js application to be scaled out to multiple servers as long as the logging directory resides on a shared network drive.

Side by side with other content types

One of the more interesting benefits of hosting node.js applications in IIS using the iisnode module is support for a variety of content types within a single web site. Next to a node.js application one can host static HTLM files, client side JavaScript scripts, PHP scripts, ASP.NET applications, WCF services, and other types of content IIS supports. Just like the iisnode module handles node.js applications in a particular site, other content types will be handled by the registered IIS handlers.

Indicating which files within a web site are node.js applications and should be handled by the iisnode module is done by registring the iinode handler for those files in web.config. In the simplest form, one can register the iisnode module for a single *.js file in a web site using the ‘path’ attribute of the ‘add’ element of the handler collection:

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

Alternatively, one can decide that all files in a particular directory are supposed to be treated as node.js applications. A web.config using the <location> element can be used to achieve such configuration:

<location path="nodejsapps">
<add name="iisnode" path="*.js" verb="*" modules="iisnode" />

One other approach one can employ is to differentiate node.js applications from client side JavaScript scripts by assigning a file name extension to node.js applications other than *.js, e.g. *.njs. This allows a global iisnode handler registration that may apply across all  sites on a given machine, since the *.njs extension is unique:

<add name="iisnode" path="*.njs" verb="*" modules="iisnode" />

Output caching

IIS output caching mechanism allows you to greatly improve the throughput of a node.js application hosted in iisnode if the content you serve can be cached for a time period even as short as 1 second. When IIS output caching is enabled, IIS will capture the HTTP response generated by the node.js application and use it to respond to similar HTTP requests that arrive within a preconfigured time window. This mechanism is extremely efficient, especially if kernel level output caching is enabled.

URL Rewriting

The iisnode module composes very well with the URL Rewriting module for IIS. URL rewriting allows you to normalize the URL space of the application and decide which IIS handlers are responsible for which parts of the URL space. For example, you can use URL rewriting to serve static content using the IIS’es native static content handler (which is a more efficient way of doing it that serving static content from node.js), while only letting iisnode handle the dynamic content.

You will want to use URL rewriting for majority of node.js web site applications deployed to iisnode, in particular those using the express framework or other MVC frameworks.

Minimal changes to existing HTTP node.js application code

It has been the aspiration for iisnode to not require extensive changes to existing, self-hosted node.js HTTP applications. To that end, most applications will only require a change in the specification of the listen address for the HTTP server, since that address is assigned by the IIS as opposed to left for the application to choose. The iisnode module will pass the listen address to the node.exe worker process in the PORT environment variable, and the application can read it from process.env.PORT:

var http = require('http');

http.createServer(function (req, res) {
    res.writeHead(200, {'Content-Type': 'text/plain'});
    res.end('I am listening on ' + process.env.PORT);

If you access the endpoint created by the application above, you will notice the application is actually listening on a named pipe address. This is because the iisnode module uses HTTP over named pipes as a communication mechanism between the module and the worker node.exe process. One implication of this is HTTPS applications will need to be refactored to use HTTP instead of HTTPS. For those applications, HTTPS can be configured and managed at the IIS level itself.

Configuration with YAML or web.config

The iisnode module allows many of the configuration options to be adjusted using the iisnode.yml file or the system.webServer/iisnode section of web.config. Settings in the iisnode.yml file, if present, take precedence over settings in the web.config. Below is the list of options (most of which were described above) with their default values.

# 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"
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
logDirectoryName: iisnode
debuggingEnabled: true
debuggerPortRange: 5058-6058
debuggerPathSegment: debug
maxLogFileSizeInKB: 128
maxTotalLogFileSizeInKB: 1024
maxLogFiles: 20
devErrorsEnabled: true
flushResponse: false
enableXFF: false

Configuration using environment variables

In addition to using web.config and iisnode.yml, you can also configure iisnode by setting environment variables of the IIS worker process. Every setting available in iisnode.yml can also be controlled with environment variables. This option is useful for hosting providers wishing to offer a web based management experience for iisnode.

Integrated management experience

The iisnode module configuration system is integrated with IIS configuration which allows common IIS management tools to be used to manipulate it. In particular, the appcmd.exe management tool that ships with IIS can be used to augment the iismodule configuration. For example, to set the maxProcessCountPerApplication value to 2 for the “Default Web Site/node” application, one can issue the following command:

%systemroot%\system32\inetsrv\appcmd.exe set config "Default Web Site/node" -section:iisnode /maxProcessCountPerApplication:2

This allows for scripting the configuration of node.js applications deployed to IIS.

IIS 8.5 Hosting - HostForLIFE.eu :: How to Fix: “HTTP Error 401.3 – Unauthorized” Error in IIS ?

clock October 8, 2014 08:05 by author Peter

Today, I am going to show you how to fix How to Fix: “HTTP Error 401.3 – Unauthorized” Error in IIS. While working on my site, I got a small issue with IIS. I had set up a new virtual directory for the site but when the site was viewed in the browser the IIS error was displayed:
Server Error in Application “DEFAULT WEB SITE”
HTTP Error 401.3 – Unauthorized
You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.

As you can see on the picture below:

Judging from the error the permissions on the folder was incorrect. And a quick peek at the properties confirmed this. Admittedly, I don’t have much experience with  IIS 7+ (IIS 6 & 6.5 that’s a different story). So when I tried to add the correct user account to the I couldn’t identify the correct user account. Honestly, I was actually looking for IUSR_MachineName . As it turns out IUSR_MachineName was removed in IIS 7 and replaced with IUSR. So adding the IUSR user account to the folder and everything worked. Yes, it was a simple fix but it can be an annoying one if you don’t know what to look for.

HostForLIFE.eu Proudly Launches Hosting with SiteLock Malware Detector

clock October 6, 2014 06:30 by author Peter

HostForLIFE.eu, a leading Windows web hosting provider with innovative technology solutions and a dedicated professional services team, today announced the support of SiteLock Malware Detector on all their newest hosting environments. HostForLIFE.eu Hosting with SiteLock Malware Detector plan starts from just as low as $36.00 / year only and this plan has supported daily malware scan, trust seal, application scan, TrueSpeed CDN, etc.

HostForLIFE.eu offers the greatest performance and flexibility hosting with SiteLock Malware Detector at an economical price. HostForLIFE.eu provides flexible hosting solutions that enable their company to give maximum uptime to customer. SiteLock monitors your website 24x7 for vulnerabilities and attacks, which means you can worry less about your website and more about your business.

SiteLock is a cloud-based, website security solution for small businesses. It works as an early detection alarm for common online threats like malware injections, bot attacks etc. It not only protects websites from potential online threats, but also fixes vulnerabilities. With the presence of SiteLock, your website will be protected and scanned against viruses, spyware, malware, identity theft and other online scams. Note that, as they rely more and more on internet technology, these online viruses and scams become bigger and smarter to handle.

Over 70% Customers look for a sign of security before providing personal details online. The SiteLock Trust Seal not only re-assures customers, but also boosts sales. The customer doesn’t need technical ability to install and set up SiteLock for their website. SiteLock is cloud-based and starts scanning website and email instantly.
With this SiteLock feature, you can be assured that you will always be one step ahead of online hackers and swindlers’ illegal intentions. With more than 6 years in the web hosting business, HostForLIFE’s technical staff is more than ready on its feet to develop and tackle viruses, malware and the likes to sustain the safe and reliable use of your website.

Further information and the full range of features hosting with SiteLock Malware Detector can be viewed here http://www.hostforlife.eu/Hosting-with-Sitelock-Malware-Detector-in-Europe

About HostForLIFE.eu

HostForLIFE.eu is European Windows Hosting Provider which focuses on Windows Platform only. We deliver on-demand hosting solutions including Shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes.

We have offered the latest Windows 2016 Hosting, ASP.NET Core 2.2.1 Hosting, ASP.NET MVC 6 Hosting and SQL 2017 Hosting.

Tag cloud

Sign in