Title: receiving parsererror SyntaxError: Unexpected token
Last modified: August 30, 2016

---

# receiving parsererror SyntaxError: Unexpected token

 *  [tsabar](https://wordpress.org/support/users/tsabar/)
 * (@tsabar)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/receiving-parsererror-syntaxerror-unexpected-token/)
 * regardless of the test i choose, i always receive the following error when running
   an ssl test:
 * parsererror
    SyntaxError: Unexpected token <
 * what could this be due to?
 * thanx
 * [https://wordpress.org/plugins/ssl-insecure-content-fixer/](https://wordpress.org/plugins/ssl-insecure-content-fixer/)

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

 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/receiving-parsererror-syntaxerror-unexpected-token/#post-6879700)
 * That sounds like something (another plugin or your theme) adding some junk to
   the output of my AJAX calls. It’s very likely that it’s an error in a plugin 
   or your theme, so maybe try adding this to your wp-config.php file under the 
   bit about `WP_DEBUG`:
 * `define('WP_DEBUG_DISPLAY', false);`
 * If you are comfortable with your browser’s console, you can look at the AJAX 
   call in the network tab to find out exactly what junk is being inserted.
 * cheers,
    Ross
 *  Thread Starter [tsabar](https://wordpress.org/support/users/tsabar/)
 * (@tsabar)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/receiving-parsererror-syntaxerror-unexpected-token/#post-6879712)
 * thanx for responding so quickly. i added the line to the wp-config file to no
   effect.
 * if i see the lock showing up on the browser can i just assume it is working properly?
 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/receiving-parsererror-syntaxerror-unexpected-token/#post-6879716)
 * Yup. You only need to change the HTTPS Detection settings if WordPress can’t 
   detect HTTPS, and you’d never get the lock if that was happening.
 * cheers,
    Ross

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

The topic ‘receiving parsererror SyntaxError: Unexpected token’ is closed to new
replies.

 * ![](https://ps.w.org/ssl-insecure-content-fixer/assets/icon-256x256.png?rev=2590634)
 * [SSL Insecure Content Fixer](https://wordpress.org/plugins/ssl-insecure-content-fixer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ssl-insecure-content-fixer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/)
 * [Active Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [webaware](https://wordpress.org/support/users/webaware/)
 * Last activity: [10 years, 5 months ago](https://wordpress.org/support/topic/receiving-parsererror-syntaxerror-unexpected-token/#post-6879716)
 * Status: not resolved