- EZproxy continues to crash after you have updated a stanza
- Standalone EZproxy
First most of the time EZproxy will tell you why it can't start in the messages.txt file. It logs issues with startup or successful startups in that file. However, if you recently updated a stanza you may have added more text then needed.
- Search your config.txt for the word IncludeFile
- Remove that directive and the text that follows it
If you copied the stanza from our site. You will note at the bottom of the page it states the following.
"A Hosted EZproxy Include File is available for this resource. Hosted EZproxy customers will receive automatic updates with OCLC’s latest version of this stanza. Note: Hosted EZproxy customers in the Americas using self-service may reference the Include File by adding the following line to config.txt:"
Sometimes it is missed that the portion below this is not needed for standalone EZproxy users. Just copy the text above it into your config. Since you do not have a folder named database or a text file with the include EZproxy fails to load.
As of version 6.6.2 you will no longer be prevented from starting EZproxy. You will still see an error in the message.txt for the file not being found.