# How to restart Discourse after server reboot?

**URL:** https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181
**Category:** Self-hosting
**Created:** [December 28, 2018, 8:36am UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181 "2018-12-28T08:36:46Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![iraszl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iraszl/32/120318_2.png) [@iraszl](https://meta.discourse.org/u/iraszl)
#### Post date: [December 28, 2018, 8:36am UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/1 "2018-12-28T08:36:46Z")

</div>

I have a DO droplet. And I installed discourse with docker as recommended. It was working fine. I also restored Discourse from a backup. Still worked fine. Then, I wanted to restart the server so the new backup takes full effect, and caches clear out. I ssh-d into the droplet and gave the ‘reboot’ command. The server rebooted but the site doesn’t load anymore. White page of death. Do I have to restart Discourse or docker? Please help!

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 28, 2018, 9:39am UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/2 "2018-12-28T09:39:40Z")

</div>

The install isn’t correct as per our official installation guide; docker startup is always automatic if you’ve followed the guide.

If you followed our [official install](https://meta.discourse.org/t/142537?silent=true) guide closely, without deviating from the install steps, and the install was running prior to restoring the backup, this is more likely some kind of backup restore issue. Are you sure there aren’t any JS errors in the F12 browser console on the “white page of death”?

---

<div class="post-metadata">

### Author: ![iraszl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iraszl/32/120318_2.png) [@iraszl](https://meta.discourse.org/u/iraszl)
#### Post date: [December 28, 2018, 9:54am UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/3 "2018-12-28T09:54:21Z")

</div>

You’re right! There are js errors. Any idea what is wrong? See errors below:

> ```
> > Refused to load the script '<URL>' because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'report-sample' <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> <URL> https: 'unsafe-inline'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
> > 
> > www.themefair.com/:25 Refused to load the script 'http://www.themefair.com/assets/locales/en-ed716b03cc4bab12e892d910c3a88c2d69c5f46a1184f73b09390e8cb7dbe602.js' because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'report-sample' https://www.themefair.com/logs/ https://www.themefair.com/sidekiq/ https://www.themefair.com/mini-profiler-resources/ https://www.themefair.com/assets/ https://www.themefair.com/brotli_asset/ https://www.themefair.com/extra-locales/ https://www.themefair.com/highlight-js/ https://www.themefair.com/javascripts/ https://www.themefair.com/plugins/ https://www.themefair.com/theme-javascripts/ https://www.themefair.com/svg-sprite/ https://www.google-analytics.com/analytics.js https: 'unsafe-inline'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
> ...
> 
> ```

---

<div class="post-metadata">

### Author: ![dax](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dax/32/244677_2.png) [@dax](https://meta.discourse.org/u/dax)
#### Post date: [December 28, 2018, 12:15pm UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/4 "2018-12-28T12:15:29Z")

</div>

Is CSP turn on or off on your site?

> [@Mitigate XSS Attacks with Content Security Policy](https://meta.discourse.org/t/mitigate-xss-attacks-with-content-security-policy/104243#heading--extend-default-csp):
>
> bookmark This guide explains how to use Content Security Policy (CSP) to mitigate Cross-Site Scripting (XSS) attacks in Discourse. It covers CSP basics, configuration, and best practices. person_raising_hand Required user level: Administrator Summary Content Security Policy (CSP) is a crucial security feature in Discourse that helps protect against Cross-Site Scripting (XSS) and other injection attacks. This guide covers the basics of CSP, how it’s implemented in Discourse, and how to c…

---

<div class="post-metadata">

### Author: ![iraszl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iraszl/32/120318_2.png) [@iraszl](https://meta.discourse.org/u/iraszl)
#### Post date: [December 28, 2018, 3:18pm UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/5 "2018-12-28T15:18:30Z")

</div>

Do you mean this setting on Discourse?

 ![49%20PM](https://global.discourse-cdn.com/meta/original/3X/3/5/35f9ba001776f0516e6beca417ced507d2e20466.png)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [January 27, 2019, 3:31pm UTC](https://meta.discourse.org/t/how-to-restart-discourse-after-server-reboot/105181/6 "2019-01-27T15:31:23Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
