"My presentation stopped working while I was viewing the course! What's wrong with the course?"

Don't worry; our servers are okay.

  1. cached filesYour web-browser caches (stores) files into its history from previous lessons, and may try to recycle previous lesson files instead of getting new ones for the current lesson from our server as it should. This causes your presentation or practice questions suddenly to appear to freeze, or "hang." This happens if you are working especially hard and re-taking lessons more quickly than your browser expires its cached files. If you experience unexpected freezing, simply go to your browser's configuration settings and clear/delete the browser's history/cache, and then re-start your lesson.

    How to clear history data:  Google Chrome   Internet Explorer   Safari 

  2. If you are connecting to the course through:
    • a company's network proxy server,
    • through a VPN to your office to the Internet,
    • a hotel Internet connection,
    • a "web-accelerated" dial-up connection, or
    • a "web-accelerated" mobile/wireless connection,

Please realize that a proxy server might be configured to cache and serve Internet files from earlier sessions. This problem is beyond your control, and is also beyond our control. It is a problem with the connection configuration of your Internet service provider. Consequently, you may experience difficulties in getting up-to-date files that are necessary for viewing your course module. You can:

  1. Ask your network administrator to configure the proxy server to disable caching of any files from the website https://www.certifiedinfosec.com/ .
    - OR -
  2. Connect to the campus using a different Internet connection that does not utilize a web-content caching server.
    - OR -
  3. Eventually, the caching server should automatically expire the saved content, thus allowing new content to be requested and served. How long does this take? Only the administrator of the caching server knows for sure. Don't forget that the new content requested will then also be cached, which will potentially interfere with later sessions.