Site fails to load with js errors

[carlokok]

Our site (https://talk.remobjects.com/) started failing to load with the last few updates:

Laden voor het <script> met bron ‘https://talk.remobjects.com/assets/ember_jquery-27e777857b8c0730dacfe09cb11711365d21a5db4f9ee0b85d494e4259cf6cda.js’ is mislukt. [talk.remobjects.com:34](https://talk.remobjects.com/)

ReferenceError: define is not defined[Meer info] [_preload-store-ec90ffab9d7a6d9e507dda7cf7343e9d50b8bce624f7f44486ac8fd6b9814309.js:1](https://talk.remobjects.com/assets/_preload-store-ec90ffab9d7a6d9e507dda7cf7343e9d50b8bce624f7f44486ac8fd6b9814309.js)

Laden voor het <script> met bron ‘https://talk.remobjects.com/assets/vendor-20c2f328b5abb11fe184c1b75687e13d2b1ecc3ef8c7a3340da616da2acb03bb.js’ is mislukt. [talk.remobjects.com:38](https://talk.remobjects.com/)

ReferenceError: define is not defined[Meer info] [_pretty-text-bundle-d8a2e94eb658e9772d1ffdfcc0c3c5d31eba61f2c36e5f86a0d59f2d76e795ba.js:1](https://talk.remobjects.com/assets/_pretty-text-bundle-d8a2e94eb658e9772d1ffdfcc0c3c5d31eba61f2c36e5f86a0d59f2d76e795ba.js)

ReferenceError: define is not defined[Meer info] [application-faebd89d087a88aed7d48f6dd6c16a4721027e95b7da1fc6db583719d0ada076.js:1:1](https://talk.remobjects.com/assets/application-faebd89d087a88aed7d48f6dd6c16a4721027e95b7da1fc6db583719d0ada076.js)

ReferenceError: Ember is not defined[Meer info] [plugin-ece81ae2de07f89c2a2358bde79f6a75a400c536bb254955ee48ee6a2c35860c.js:1:1](https://talk.remobjects.com/assets/plugin-ece81ae2de07f89c2a2358bde79f6a75a400c536bb254955ee48ee6a2c35860c.js)

ReferenceError: define is not defined[Meer info] [_plugin-third-party-95176350723c7352bf3851c4a776723ad45db51c33dd061787efcc6dc0177e89.js:1](https://talk.remobjects.com/assets/_plugin-third-party-95176350723c7352bf3851c4a776723ad45db51c33dd061787efcc6dc0177e89.js)

ReferenceError: define is not defined[Meer info] [_admin-df2063af5c4693fff66917c700756e4fd7644887948651199a4c0398445a012b.js:1](https://talk.remobjects.com/assets/_admin-df2063af5c4693fff66917c700756e4fd7644887948651199a4c0398445a012b.js)

ReferenceError: require is not defined[Meer info] [talk.remobjects.com:435:13](https://talk.remobjects.com/)

ReferenceError: Ember is not defined[Meer info] [talk.remobjects.com:452:3](https://talk.remobjects.com/)

ReferenceError: require is not defined[Meer info]

Tried updating again but that didn’t make any real difference. What else can I try?

The site itself does function fine in already opened tabs.

[david (David Taylor)]

Try safe mode:

How to use Discourse Safe Mode

Discourse has a “JavaScript Safe Mode” any user can use to isolate the root cause of a JavaScript issue. To access safe mode go to: http://your-site-name/safe-mode for example this is the safe mode for meta: https://meta.discourse.org/safe-mode [image] To exit safe mode simply close your browser tab When entering safe mode you can select between: Disable all site customizations Disable unofficial plugins Disable official plugins By default all 3 options are selected, but you …

If that works, then the problem is being caused by one of your themes or plugins

[carlokok]

Thanks; that gives the exact same result:

RemObjects Talk

[david (David Taylor)]

I think the next thing to try would be a command-line rebuild, assuming you have a standard self-hosted installation.

How do I manually update Discourse and Docker image to latest?

If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occasionally need to do this additional step. Discourse itself should be updated about twice a month, by clicking the “Update to Latest Version” button in your admin dashboard ( admin/upgrade). We do beta releases roughly once every week. Every two months we recommend SSH’ing…

[Johani (Joe)]

I’m seeing this in Chrome:

I remember reading that SPDY errors have something to do with SSL / https or things along that nature, I could be wrong though.

[carlokok]

Thanks! Chrome gave a better hint there (the weird thign was, if you load those urls manually they’re fine, if you let the browser load them, it doesn’t work). turns out my disk was full for the outside nginx; a cleanup made it work.