# Data explorer taking instance down on rebuild

**URL:** <https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078>\
**Category:** Self-hosting\
**Tags:** data-explorer\
**Created:** [February 23, 2023, 4:44pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078 "2023-02-23T16:44:10Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [February 23, 2023, 4:44pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/1 "2023-02-23T16:44:10Z")

</div>

So I just rebuilt an instance, it uses the [standard install](https://meta.discourse.org/t/142537?silent=true) template, SSL is enabled and there’s nothing sat in front of it (reverse proxy or otherwise).

I’m seeing an error 502 from nginx after rebuilding.

@pfaffman just rebuilt a staging instance and has confirmed he’s seeing the same issue.

From the nginx error log:

`2023/02/23 16:42:23 [error] 572#572: *4 connect() failed (111: Connection refused) while connecting to upstream, client: CLIENT_IP, server: _, request: "GET /service-worker.js HTTP/2.0", upstream: "http://127.0.0.1:3000/service-worker.js", host: "HOSTNAME", referrer: ""`

I wondered if this was related to disabling a couple of official plugins, so put them back into the YML, but no dice.

---

_[View the full topic](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078)._