Skip to main content
ZenHub houses documentation to support you if you’re using Contensis Classic. Contensis Classic includes our WYSIWYG and templating features. If you’re working with a newer version of Contensis, is your go-to place to find anything Contensis-related when building with content types.
There is a newer version of Contensis. Click to find out more and download the latest version.

Configure internet access for Contensis

This article explains how to configure Internet access for your server if you are using a proxy server. If you are not using a proxy you do not need to follow this guide.

Before we start you need to have access to the machine.config on the CMS Server(s) requiring access. You will also need the proxy server rules as proxy servers can be configured to allow non-authenticated access to servers on a specified IP range or server names. You will more than likely need to ask your server administrators to change these rules for you to allow access to Contensis servers.

Why Contensis needs internet access

Contensis requires access to the internet for a number of reasons. Firstly, we need to be able to verify your software license and any modules you may have purchased; we periodically ping back to our central licensing servers.

Secondly, as we integrate with Google Analytics we need to retrieve the content collected and stored on Google's servers to display on your Contensis dashboard.

Furthermore, we need access to the internet for Quality Assurance reasons. The QA service sends page data back to our servers for validation. We also need internet access for the broken link checker, as this part of QA runs on your server and needs to verify any and all broken links you may be linking out to from your web pages.

As well as your CMS server your publishing server also needs internet access for a few reasons. The RSS Reader needs internet access as it will need to connect to every address that has subscribed to the RSS feed. Also if you're making use of the weather control, this will connect to the weather service on our servers to grab its data.

Configure internet access

To make sure that all your internet traffic is being routed through your proxy server you need to change settings in machine.config and the default web.config files on the CMS Server which can be found in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config. We need to modify both machine.config and web.config because the Contensis services, run outside of a web context. Use the code below to update the machine.config file.

Be sure to enter in your proxy server address and port. This code instructs the .NET to use the default proxy settings for the server in any WebRequests requests it makes. You will also need to do the same for web.config although if the settings already exist they will need to be overridden.

Configure default system proxy on the CMS server

The final step is to set the default proxy on the CMS server.

  1. Log in to your CMS Server.
  2. Open Control Panel.
  3. Select Internet Options.
  4. Select the Connections Tab.
  5. Place a tick in the Use a proxy server for your LAN option and enter its name or IP address and port information.
  6. Now click Save and restart IIS server.

When you re-run the Contensis System Diagnostic Scan from within the management console you should see a success against the Internet Connection test.