# No longer seeing .../finish-installation/register

**URL:** https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951
**Category:** Self-hosting
**Created:** [February 5, 2017, 5:15pm UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951 "2017-02-05T17:15:07Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [February 5, 2017, 5:15pm UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/1 "2017-02-05T17:15:07Z")

</div>

I installed discourse yesterday but stopped the process at the …/finish-installation/register screen because I wanted to go ahead and install wordpress first. Today I wanted to come back to disourse and finish the installation but `http://forum.mydomain.net/finish-installation/register` now gives me “Oops! That page doesn’t exist or is private.” Should I just register via the “Signup” button or is that a different process?

I am assuming that this has nothing to do with the issue described [here](https://meta.discourse.org/t/did-not-get-admin-registration-screens-after-finstall/53925) because I originally did see the finish-installation screen and because the issue has been fixed in december.

I also tried `http://forum.mydomain.net/wizard` but that brought me to the dafault welcome post.

---

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [February 5, 2017, 5:59pm UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/2 "2017-02-05T17:59:46Z")

</div>

Problem solved: the finish-installation page reappeared after I rebooted the droplet.

If someone can explain what happened, please do (always keen to understand).

---

<div class="post-metadata">

### Author: ![ento](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ento/32/121212_2.png) [@ento](https://meta.discourse.org/u/ento)
#### Post date: [February 11, 2017, 5:39am UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/3 "2017-02-11T05:39:16Z")

</div>

This happened to me too. Here’s my theory:

- Discourse performed its daily backup sometime before you came back to finish the installation.

- A successful backup creates a system message.

- Creating a system message updates the user record for the Discourse system user.

- Updating a system user, who is an admin, [clears the flag](https://github.com/discourse/discourse/blob/675cb1c71569193b079440a0b2d476d804fc18c0/app/models/user.rb#L925-L930) to show the installation screen.

- If the flag is not set, `/finish-installation/register` [displays an “Oops! That page doesn’t exist or is private” page](https://github.com/discourse/discourse/blob/675cb1c71569193b079440a0b2d476d804fc18c0/app/controllers/finish_installation_controller.rb#L61-L64).

- Rebooting the server instance [sets the flag again](https://github.com/discourse/discourse/blob/675cb1c71569193b079440a0b2d476d804fc18c0/config/initializers/006-ensure_login_hint.rb#L16-L19) if there is only one admin user, which is the system user at this point.

Log of database sleuthing I did:

“The backup was successful” message:

```plaintext
discourse=> select created_at, updated_at, substring(raw, 0, 25) from posts order by id desc limit 1;
-[RECORD 1]-------------------------
created_at | 2017-02-11 03:38:05.02299
updated_at | 2017-02-11 03:38:05.02299
substring | The backup was successfu

```

System user’s last\_posted\_at and updated\_at:

(not sure about the three-second gap)

```plaintext
discourse=> select created_at, updated_at, last_posted_at from users where id=-1;
-[RECORD 1]--+---------------------------
created_at | 2017-02-09 09:31:23.724877
updated_at | 2017-02-11 03:38:08.296426
last_posted_at | 2017-02-11 03:38:05.02299

```

has\_login\_hint’s updated\_at:

```plaintext
discourse=> select updated_at from site_settings where name='has_login_hint';
-[RECORD 1]--------------------------
updated_at | 2017-02-11 03:38:08.304158

```

---

<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: [February 11, 2017, 8:59am UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/4 "2017-02-11T08:59:15Z")

</div>

Is this plausible @eviltrout?

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [February 13, 2017, 3:55pm UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/5 "2017-02-13T15:55:42Z")

</div>

This is some great detective work and I think the likely cause of this issue.

This should fix it:

[https://github.com/discourse/discourse/commit/e1d358ffbf8550686bd415604899ed35f82fb6a2](https://github.com/discourse/discourse/commit/e1d358ffbf8550686bd415604899ed35f82fb6a2)

---

<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: [February 14, 2017, 12:01am UTC](https://meta.discourse.org/t/no-longer-seeing-finish-installation-register/56951/6 "2017-02-14T00:01:56Z")

</div>


