Hi there,
there seems to be a lot of confusion about Surfprotection, error messages, configs, etc - so I'd like to give some hints, try to solve some config issues and last but not least try to find and fix possible bugs.
If you use SurfProtection and encounter any kind of problems, please post them here. Before posting, make sure you have 5.006 installed and running and please read the whole posting with all the known issues, tipps, ...
1. SurfProtection - Known Issues:
-----------------------------------
'Cache is unable to process/forward your request at this time'
This problem occurs (normally) after reconfiguring anything related to the contentfilter. Currently the proxy/contentfilter gets restarted in a not very 'time-efficient' way so it will take some time until your request can be processed. We are working on this issue to improve speed after configuring.
In case you _always_ see this message, please post your configuration here.
'All sites are getting blocked by a profile called '.''
This problem occurs, if no profile matches your request, which means e.g. there is a profile/assignment which matches your username or the network you are coming from. We'll change the message to make it more explaining. In case you are sure the configuration is ok, but all sites are still getting blocked, post here with config and a small description.
Edit: This issue has been addressed with Up2date 5.007 - the error reads now "No matching profile found"
Internet Explorer displayes XML content when downloading a file
This is a known issue which should be solved ASAP. In case you encounter this the only workaround is using Mozilla or disabling/bypassing the proxy.
Edit: This issue has been address with Up2Date 5.007 - Internet Explorer should now be able to download files and see the progressbar as well.
2. SurfProtection - Config hints:
--------------------------------
When changing config in WebAdmin, please always make sure you have a proper profile with a correct assignment to usernames or networks/hosts.
After doing config changes, you may need to wait some seconds (or some more seconds on slower hardware).
When using SurfProtection with all it's features I highly recommend using 256MB RAM as a minimum - with 128MB the box will start swapping and get _very_ slow. (128MB is great when not using contentscaning at all)
3. SurfProtection - Reporting here:
-----------------------------------
Once again: when posting, please make sure you have at least 5.006 and add basic configuration information. In case we can not solve the problem here (UBB) and I can not reproduce it in the lab, I might need to login to the box to have a closer look.
cheers
~marcel
This thread was automatically locked due to age.
