Surfulater has a small Web Server built-in to it which is used to acquire and display images in Knowledge Base content(Articles & Folders). This web server is also used by the Firefox and Chrome Surfulater Extensions to capture web page content. If you are unable to see images in articles or capture content in Firefox or Chrome, it is most likely because you have a Firewall, other than the standard Windows Firewall, which is blocking access to the built-in Surfulater Web Server. Some Anti-Virus software such as ESET NOD32 can also block access to our built-in Web Server,

These Firewalls will typically prompt you when a program is run for the first time, asking whether you want to grant or deny access. For Surfulater to work correctly it is crucial that you allow all access requests.

The Surfulater Web Server is used for more than just serving up images. It is used to communicate with the Surfulater Firefox and Chrome Extensions, to serve up Attachments and more. If any other program is blocking access to the built-in Surfulater Web server, these aspects will not work either.

Access to Surfulater's built-in Web Server can also fail if the Windows hosts file breaks access to localhost, so this is another thing to check. The hosts file is located in C:\Windows\System32\drivers\etc. Thanks to Nick Pearson for tracking this down.

Please read Firewalls are wonderful things except when they aren’t. for more on this issue.

Commencing with Surfulater version 3.40 we now check and notify you if there is a problem accessing the built-in web server. Help topics in the new Troubleshooting folder provide more information on how to resolve this.