# JSON::ParserError on Jobs::VersionCheck

**URL:** <https://meta.discourse.org/t/json-parsererror-on-jobs-versioncheck/64650>\
**Category:** Bug\
**Created:** [17 يونيو 2017، 12:44ص UTC](https://meta.discourse.org/t/json-parsererror-on-jobs-versioncheck/64650 "2017-06-17T00:44:00Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![AlbertA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alberta/32/73923_2.png) [@AlbertA](https://meta.discourse.org/u/AlbertA)\
**Post date:** [17 يونيو 2017، 12:44ص UTC](https://meta.discourse.org/t/json-parsererror-on-jobs-versioncheck/64650/1 "2017-06-17T00:44:00Z")

</div>

Hi!

I just installed a forum on an ubuntu 16.04 linode instance using docker instructions.

I also created an instance on a local VM so I could import my old smf2 based forum to it.

Once imported I created a backup in the local VM through the discourse backup tab.

I then applied this backup onto my linode instance following these instructions:

> [@Is there any way to restore your site from backup in the terminal?](https://meta.discourse.org/t/is-there-any-way-to-restore-your-site-from-backup-in-the-terminal/42377/9):
>
> It worked for me by first getting into the app ./launcher enter app then discourse enable\_restore discourse restore \<filename.of.the.backup.tar.gz\> discourse disable\_restore Using the script/discourse didn’t work

Everything seems to work fine except the version check in the admin dashboard: “A check for updates has not been performed. Ensure sidekiq is running.”

I’m using the latest release of discourse (as of this post discourse (c5f42f0) ) and HTTPS is enabled.

Sidekiq is running and actually has a few retry jobs all with:

> ` Jobs::HandledExceptionWrapper: Wrapped JSON::ParserError: 743: unexpected token at '<html> <head> <title>Discourse</title> <link href="https://fonts.googleapis.com/css?family=Open+Sans:300,600,700...`

The logs say:

> ```
> Job exception: 743: unexpected token at '<html> <head> <title>Discourse</title> <link href="https://fonts.googleapis.com/css?family=Open+Sans:300,600,700" rel="stylesheet" type="text/css"> <sty
> 7:15 pm
> Job exception: 743: unexpected token at '<html>
> <head>
> <title>Discourse</title>
> 
> ```

> ```
> <link href="https://fonts.googleapis.com/css?family=Open+Sans:300,600,700" rel="stylesheet" type="text/css">
> <style>
> body {
> font-family: 'Open Sans',Arial,sans-serif;
> background-color: rgb(231,238,247);
> background-image: url('https://discourse-cdn.s3.amazonaws.com/bg.jpg');
> background-repeat: repeat;
> background-position: left top;
> padding-bottom: 3em;
> }
> 
> ```

> ```
> #logo {
> width: 80%;
> }
> 
> ```

> ```
> #discourse-twitter {
> margin-top: 2em;
> }
> 
> ```

> ```
> .content {
> width: 60%;
> max-width: 600px;
> margin: 1em auto;
> background-color: white;
> padding: 1em;
> box-shadow: 0 5px 10px rgba(0,0,0,0.2);
> border-radius: 2px;
> border: 1px solid #ccc;
> }
> 
> ```

> ```
> h1 {
> text-align: center;
> font-size: 1.5em;
> color: #666;
> font-weight: normal;
> }
> </style>
> </head>
> 
> ```

> ```
> <body>
> <div class='content'>
> 
> ```

> ```
> <center><img src="https://discourse-cdn.s3.amazonaws.com/discourse-logo.png" id='logo' alt='Discourse'></center>
> 
> ```

> ```
> <h1>Sorry, we're experiencing technical difficulties!</h1>
> 
> ```

> ```
> <center><img src="https://global.discourse-cdn.com/meta/images/emoji/twitter/frowning.png" width="72" height="72" alt="frowning"></center>
> 
> ```

> ```
> <p>This community can't be reached at the moment.
> <strong>Our team has been alerted and we're working on it.</strong></p>
> 
> ```

> ```
> <p>Please follow <a href="https://twitter.com/discourse">@discourse</a> for updates.</p>
> 
> ```

> ```
> <div id='discourse-twitter'>
> <center>
> <a class="twitter-timeline" href="https://twitter.com/discourse" data-widget-id="596039779378208769">Tweets by @discourse</a>
> <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
> </center>
> </div>
> </div>
> 
> ```

> ```
> </body>
> </html>
> '
> 
> ```

backtrace:

> ```
> /usr/local/lib/ruby/2.4.0/json/common.rb:156:in `parse'
> /usr/local/lib/ruby/2.4.0/json/common.rb:156:in `parse'
> /var/www/discourse/lib/discourse_hub.rb:43:in `singular_action'
> /var/www/discourse/lib/discourse_hub.rb:27:in `get'
> /var/www/discourse/lib/discourse_hub.rb:13:in `discourse_version_check'
> /var/www/discourse/app/jobs/scheduled/version_check.rb:13:in `execute'
> /var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'
> 
> ```

So it seems version check is expecting a JSON response but it’s not getting it.  
Any ideas how I could resolve this?

I’ve already rebooted the node and ./launch rebuild app with no effect.

---

_[View the full topic](https://meta.discourse.org/t/json-parsererror-on-jobs-versioncheck/64650)._
