Title: Troubleshooting “internal script failure”
Last modified: March 15, 2017

---

# Troubleshooting “internal script failure”

 *  Resolved [aspeagle](https://wordpress.org/support/users/aspeagle/)
 * (@aspeagle)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/)
 * I’m getting a generic “internal script failure” from phpCAS when I click the 
   link to log into CAS… but, I’m not seeing anything in the logs.
 * What’s the best way to debug this?
    -  This topic was modified 9 years, 2 months ago by [aspeagle](https://wordpress.org/support/users/aspeagle/).

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Paul Ryan](https://wordpress.org/support/users/figureone/)
 * (@figureone)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/#post-8926972)
 * Hm, PHP errors should show up in the web server logs. Are you sure you’re looking
   in the right place?
    [http://php.net/manual/en/function.error-reporting.php](http://php.net/manual/en/function.error-reporting.php)
   You can also temporarily set error messages to output to the client browser for
   more details: [http://stackoverflow.com/questions/1053424/how-do-i-get-php-errors-to-display](http://stackoverflow.com/questions/1053424/how-do-i-get-php-errors-to-display)
 * Another thing to check is maybe the errors are happening on the CAS server and
   not the server running WordPress?
 *  [fotan](https://wordpress.org/support/users/fotan/)
 * (@fotan)
 * [9 years ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/#post-9202958)
 * I just ran into this while testing and found that my sysadmin hadn’t installed
   mcrypt in PHP. Once he enabled it, the error went away. This is pretty old, but
   maybe it will help someone at some point. 🙂
 *  Plugin Author [Paul Ryan](https://wordpress.org/support/users/figureone/)
 * (@figureone)
 * [9 years ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/#post-9203136)
 * Version 2.6.10 should have removed the mcrypt dependency, let me know if you’re
   still seeing it in the logs!
    [https://github.com/uhm-coe/authorizer/commit/c8ae8e80a158f12e9649cb0566cecd38230b1dc9](https://github.com/uhm-coe/authorizer/commit/c8ae8e80a158f12e9649cb0566cecd38230b1dc9)
 *  [scooterlord](https://wordpress.org/support/users/scooterlord/)
 * (@scooterlord)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/#post-9547824)
 * Hello. I am too getting this error and cannot debug properly – my error log doesn’t
   show anything. Any more pointers?
    -  This reply was modified 8 years, 8 months ago by [scooterlord](https://wordpress.org/support/users/scooterlord/).

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Troubleshooting “internal script failure”’ is closed to new replies.

 * ![](https://ps.w.org/authorizer/assets/icon-256x256.jpg?rev=1967453)
 * [Authorizer](https://wordpress.org/plugins/authorizer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/authorizer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/authorizer/)
 * [Active Topics](https://wordpress.org/support/plugin/authorizer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/authorizer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/authorizer/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [scooterlord](https://wordpress.org/support/users/scooterlord/)
 * Last activity: [8 years, 8 months ago](https://wordpress.org/support/topic/troubleshooting-internal-script-error/#post-9547824)
 * Status: resolved