# Invitation 'Accept' button not working

**URL:** https://meta.discourse.org/t/invitation-accept-button-not-working/128722
**Category:** Support
**Created:** [September 16, 2019, 8:01pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722 "2019-09-16T20:01:27Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 16, 2019, 8:01pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/1 "2019-09-16T20:01:27Z")

</div>

I have sent out invitations, both by email and via link. The ‘Accept’ button does not work for anyone. I have confirmed this behavior.

---

<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: [September 17, 2019, 4:08am UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/2 "2019-09-17T04:08:08Z")

</div>

Based on prior reports I have seen for similar issues, this could mean HTTPS isn’t configured properly on your site?

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 2:51pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/3 "2019-09-17T14:51:15Z")

</div>

Interesting. Any guidance on how to troubleshoot? My cert is validating. Not sure where to go from here.

I did a DO droplet, so it automated setup.

 ![11%20AM](https://global.discourse-cdn.com/meta/original/3X/f/0/f0b8677b39da3e8017a3f9366c4869963b87dba5.png)

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 3:04pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/4 "2019-09-17T15:04:29Z")

</div>

Qualys SSL Test looks good as well.

 ![41%20AM](https://global.discourse-cdn.com/meta/original/3X/d/1/d1fc16cf80c0ea3513152c8d5ecfc364b8e2e99f.png)

> **[SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=macrofab.wiki)**
>
> A comprehensive free SSL test for your public web servers.

---

<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: [September 17, 2019, 3:08pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/5 "2019-09-17T15:08:22Z")

</div>

Is the site setting ‘force Https’ enabled?

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 3:17pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/6 "2019-09-17T15:17:51Z")

</div>

I don’t see this in the Discourse settings, so I’m guessing you are referring to something on the underlying server?

---

<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: [September 17, 2019, 3:24pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/7 "2019-09-17T15:24:18Z")

</div>

It should be in the site setting at `/admin/site_settings/category/security?filter=force%20https`, unless you are one of our hosted customers.

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 3:33pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/8 "2019-09-17T15:33:39Z")

</div>

> [@dax](#):
>
> force%20https

 ![10%20AM](https://global.discourse-cdn.com/meta/original/3X/a/5/a54e2ef4747b09561c918c9dcc6763b647025199.png)

I get no results for this.

---

<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: [September 17, 2019, 4:37pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/9 "2019-09-17T16:37:39Z")

</div>

Enable it via console:

```plaintext
cd /var/discourse
./launcher enter app
rails c
SiteSetting.force_https = true
exit

```

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 5:41pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/10 "2019-09-17T17:41:48Z")

</div>

So are these command taking the desired action, or are they making the setting visible in the UI? If the later, then it does not appear to have worked.

---

<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: [September 17, 2019, 6:27pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/11 "2019-09-17T18:27:55Z")

</div>

> [@Chris\_Mullins](#):
>
> the desired action

The former. Now we know for sure that `force HTTPS` is enabled on your site.

---

<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: [September 17, 2019, 9:04pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/12 "2019-09-17T21:04:38Z")

</div>

Did this fix your problem @Chris_Mullins? I am unclear how you got into this state, how did you set up Discourse? Is your site behind a proxy of some kind?

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 9:38pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/13 "2019-09-17T21:38:17Z")

</div>

Thanks for checking. Still struggling. Seems as if it may be related to this issue:

[https://meta.discourse.org/t/user-cannot-signup-something-went-wrong/110188](https://meta.discourse.org/t/user-cannot-signup-something-went-wrong/110188)

Were you ever able to dispose of this issue?

Latest client try:

- New Account signup
- New email
- New Firefox install

Results:

 ![53%20PM](https://global.discourse-cdn.com/meta/original/3X/4/0/40c4fee601c932bb3706f8fb5adb386f8ac39e51.png)

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 9:40pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/14 "2019-09-17T21:40:14Z")

</div>

Server side:  
Digital Ocean droplet, automated setup.

### [v2.4.0.beta4 +10](https://github.com/discourse/discourse/compare/ddd45d1419fa6d76287149c4c65fd889c29bb062...tests-passed)

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 9:41pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/15 "2019-09-17T21:41:26Z")

</div>

At one time I had this working. 1st invited user got in fine. At that point I must have done something to break.

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 9:45pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/16 "2019-09-17T21:45:44Z")

</div>

Happy to let you in for a peek if desired.

---

<div class="post-metadata">

### Author: ![Chris\_Mullins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_mullins/32/156119_2.png) [@Chris\_Mullins](https://meta.discourse.org/u/Chris_Mullins)
#### Post date: [September 17, 2019, 9:51pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/17 "2019-09-17T21:51:09Z")

</div>

These are changes that could be related? Or maybe don’t work the way I think they do…

 ![19%20PM](https://global.discourse-cdn.com/meta/original/3X/6/e/6e18a6c5566df9e1c2f9703f47ed2c48da662c04.png)

---

<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: [September 17, 2019, 11:02pm UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/18 "2019-09-17T23:02:38Z")

</div>

I’m not sure, do you see anything there @dax? The error message isn’t great. It could be this recent problem related to duplicate user prefs in the database:

> [@User cannot signup due to duplicate values in category notification states](https://meta.discourse.org/t/user-cannot-signup-due-to-duplicate-values-in-category-notification-states/127444):
>
> Hello Members can’t sign up to the site. This has started 11 days ago and no new users have been able to join the site ever since this was reported. Here is the logs I’ve found for this. A little note: We have migrated Vbulletin 4 database like 2 months ago to discourse. We never encountered this problem before. Any help will be highly appreciated. Thanks

Do you see any relevant errors in /logs when logged in as an admin?

---

<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: [September 18, 2019, 9:59am UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/19 "2019-09-18T09:59:27Z")

</div>

> [@codinghorror](#):
>
> do you see anything there @dax?

Nope.

@Chris_Mullins can you please send me an invite to [dax@discourse.org](mailto:dax@discourse.org)?

---

<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: [September 18, 2019, 10:03am UTC](https://meta.discourse.org/t/invitation-accept-button-not-working/128722/20 "2019-09-18T10:03:05Z")

</div>

We should wait until he checks `/logs` first as it could be the above error.

[Next page](https://meta.discourse.org/t/invitation-accept-button-not-working/128722.md?page=2)
