We've recently noticed an increase in "proxy errors" (see screenshot attached) when using databases remotely through WAM. It can happen when trying to access a resource or while using it. Usually the errors can be fixed by clearing the browser cache, but our users usually don't know to do this. It seems to be a problem especially with Gale databases, but I've seen it with EBSCO and other providers. There doesn't seem to be an issue when we use unproxied links. Our systems librarian said she restarts our webpac processes daily. If anyone has encountered this and found a way to resolve it, please let me know.
Electronic Resources Librarian
University of San Francisco