Title: Still getting chrome inspect element errors
Last modified: August 24, 2016

---

# Still getting chrome inspect element errors

 *  Resolved [Champenois](https://wordpress.org/support/users/champenois/)
 * (@champenois)
 * [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/)
 * Hi there, I’ve searched to see if you’ve answered this and can’t find it.
    All
   errors have gone except some 44 relating to jquery:(following is one example)
   jquery-2.1.0.min.js:4 POST [https://localhost:26143/skypectoc/v1/pnr/parse](https://localhost:26143/skypectoc/v1/pnr/parse)
   net::ERR_CONNECTION_REFUSED
 * Can you help me with what to do?
    Tks a lot..
 * [https://wordpress.org/plugins/ssl-insecure-content-fixer/](https://wordpress.org/plugins/ssl-insecure-content-fixer/)

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

 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/#post-6161824)
 * G’day Champenois,
 * Are you getting this error on your local server, or on a live website? That URL
   is for a non-standard port on a local machine (hence localhost) and I’d expect
   it to return a connection refused error or just hang.
 * NB: it looks like something on your website (e.g. your theme, or a plugin) is
   replacing the standard jQuery library bundled with WordPress. That’s asking for
   trouble. Find out what’s doing it and stop it.
 * cheers,
    Ross
 *  Thread Starter [Champenois](https://wordpress.org/support/users/champenois/)
 * (@champenois)
 * [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/#post-6161840)
 * Tks a lot for the reply Ross,
    The error only stated today after I installed 
   an ssl certificate. That’s when all the trouble started..
 * Yes, live site
 * I’ve deactivated all plugins and changed to a basic theme and still get: errors
   2: [https://localhost:26143/skypectoc/v1/pnr/parse](https://localhost:26143/skypectoc/v1/pnr/parse)
   Failed to load resource: net::ERR_CONNECTION_REFUSED
 * Can deactivated plugins and themes still cause trouble?
 * Not sure what to do after this!.. 🙁 John
 *  Thread Starter [Champenois](https://wordpress.org/support/users/champenois/)
 * (@champenois)
 * [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/#post-6161895)
 * Hi Ross, cause established, extension removed, problem gone.
    Tks again for the
   help, John ====================== Forum excerpt: /skypectoc/v1/pnr/parse it’s
   called by the Skype Plugin (installed on chrome) thats why you see that XHR call
   only in google chrome. Uninstall Skype Plugin. ======================
 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/#post-6161897)
 * Ah, a browser extension! Must remember that one. Glad to hear you resolved the
   problem.
 * cheers,
    Ross

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

The topic ‘Still getting chrome inspect element errors’ 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/)

 * 4 replies
 * 2 participants
 * Last reply from: [webaware](https://wordpress.org/support/users/webaware/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/still-getting-chrome-inspect-element-errors/#post-6161897)
 * Status: resolved