# Discourse Unlock **URL:** https://meta.discourse.org/t/discourse-unlock/194801 **Category:** Plugin **Tags:** web3, end-of-life, experimental **Created:** [June 23, 2021, 3:16pm UTC](https://meta.discourse.org/t/discourse-unlock/194801 "2021-06-23T15:16:27Z") **Posts on this page:** 20 **Page:** 2
### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger) #### Post date: [December 21, 2022, 6:32pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/29 "2022-12-21T18:32:44Z")
If you have a [standard install](https://meta.discourse.org/t/142537?silent=true), and are comfortable with the server side of things, you can access the rails console using: `cd /var/discourse` `./launcher enter app` `rails c` And to disable chat: `SiteSetting.chat_enabled = false` Though hopefully we should have this conflict ironed out soon so Chat and Unlock play nicely with each other again. đŸ™‚đŸ€ž ---
### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman) #### Post date: [December 21, 2022, 7:38pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/30 "2022-12-21T19:38:22Z")
Since he was comfortable with rails, that was the easiest way to do it. Another is to add this to the `env:` section of `app.yml`: ``` DISCOURSE_CHAT_ENABLED: false ``` This works with all site settings; it overrides the database and removes the setting from `/admin/settings`. ---
### Author: ![jancernik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jancernik/32/275892_2.png) [@jancernik](https://meta.discourse.org/u/jancernik) #### Post date: [December 22, 2022, 1:59pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/31 "2022-12-22T13:59:46Z")
I just merged this fix. Let me know if it works now with chat enabled [https://github.com/discourse/discourse-unlock/pull/4](https://github.com/discourse/discourse-unlock/pull/4) ---
### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger) #### Post date: [December 22, 2022, 3:28pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/32 "2022-12-22T15:28:20Z")
I have just upgraded and it works for me. đŸ„ł 👍 ---
### Author: ![mognet](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mognet](https://meta.discourse.org/u/mognet) #### Post date: [December 22, 2022, 6:16pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/33 "2022-12-22T18:16:15Z")
I’d love to see this with Monero. ---
### Author: ![Bathinda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bathinda/32/135888_2.png) [@Bathinda](https://meta.discourse.org/u/Bathinda) #### Post date: [December 29, 2022, 8:34am UTC](https://meta.discourse.org/t/discourse-unlock/194801/34 "2022-12-29T08:34:02Z")
> [@pfaffman](#): > > `DISCOURSE_CHAT_ENABLED: false` Though I’m not facing any such difficulty (of broken site, nor have I activated this ‘unlock’ plugin yet), but still, even though I’ve ‘Discourse Chat’ plugin and [my site](https://BathindaHelper.com) _does_ have chat activated, there is no such line (as ‘Discourse\_Chat\_Enabled’) in my ‘Web\_only.yml’ file. Am I missing something? ---
### Author: ![Shirly\_Nowak](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shirly_nowak/32/571731_2.png) [@Shirly\_Nowak](https://meta.discourse.org/u/Shirly_Nowak) #### Post date: [January 10, 2023, 4:02pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/35 "2023-01-10T16:02:01Z")
Hi @kam44 , I was wondering if this could be used for the log in of Discourse, so it only allows members with a certain NFT in their wallet to access. đŸ€” ---
### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead) #### Post date: [January 11, 2023, 7:14pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/36 "2023-01-11T19:14:40Z")
+1 (real _cryptocurrency_) ---
### Author: ![kam44](https://avatars.discourse-cdn.com/v4/letter/k/e47c2d/32.png) [@kam44](https://meta.discourse.org/u/kam44) #### Post date: [January 12, 2023, 3:27pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/37 "2023-01-12T15:27:46Z")
Yes, could be a next feature, to also login with unlock, meanwhile you should check the Sign-In with Ethereum discourse plugin : [GitHub - spruceid/discourse-siwe-auth: Discourse plugin for SIWE authentication · GitHub](https://github.com/spruceid/discourse-siwe-auth) ---
### Author: ![Justman10000](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justman10000/32/252913_2.png) [@Justman10000](https://meta.discourse.org/u/Justman10000) #### Post date: [May 6, 2023, 6:56pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/38 "2023-05-06T18:56:45Z")
Not bad at all! But to setup that all the crown, this should be extended to all payments
 ---
### Author: ![JDoy99](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jdoy99/32/290866_2.png) [@JDoy99](https://meta.discourse.org/u/JDoy99) #### Post date: [June 22, 2023, 10:59am UTC](https://meta.discourse.org/t/discourse-unlock/194801/39 "2023-06-22T10:59:25Z")
Hi there guys, I have an issue now that I am trying to customise the plugin, its not showing my locks on the paywall for a starter so I’m not sure why that is happening, but secondly, I am trying to update my 2x custom locks to new addresses and I have implemented them in the plugin but they are now not unlocking. Safe to say Ruby and Docker are not my friends, so any help would be greatly appreciated! Paid help more than welcome at this stage as I am loosing my hair.. ---
### Author: ![RuxBux](https://avatars.discourse-cdn.com/v4/letter/r/9dc877/32.png) [@RuxBux](https://meta.discourse.org/u/RuxBux) #### Post date: [June 24, 2023, 5:02pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/40 "2023-06-24T17:02:59Z")
Hello friends. I have updated to latest Discourse version, and then installed Unlock plugin. After creating Lock, that will require BSC BEP20 Token to open locked content on category, i got address to add to Discourse plugin. After doing that, adding 56 as NetworkID for Binance Smart Chain, then i try to simulate all and i always get this. > # Something went wrong
 > > To report this, please open an issue with the event ID and details on github or tell us about it on discord. > > Error > can’t convert undefined to object > > Event ID > 8686f5e2ac1847df98d90c959f382444 Any clue what could be the problem? ---
### Author: ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven) #### Post date: [June 24, 2023, 5:18pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/41 "2023-06-24T17:18:35Z")
Check the logs at `your_forum.com/logs`, it might give you some infos ---
### Author: ![RuxBux](https://avatars.discourse-cdn.com/v4/letter/r/9dc877/32.png) [@RuxBux](https://meta.discourse.org/u/RuxBux) #### Post date: [June 24, 2023, 5:41pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/42 "2023-06-24T17:41:15Z")
thanks, this is what i have found our when i try to open locked category, to simulate paying with token. > Job exception: \* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready. > > net-pop-0.1.2/lib/net/pop.rb:1004:in `check_response' net-pop-0.1.2/lib/net/pop.rb:897:in `initialize’ > net-pop-0.1.2/lib/net/pop.rb:566:in `new' net-pop-0.1.2/lib/net/pop.rb:566:in `do\_start’ > net-pop-0.1.2/lib/net/pop.rb:530:in `start' /var/www/discourse/app/jobs/scheduled/poll_mailbox.rb:39:in `poll\_pop3’ > /var/www/discourse/app/jobs/scheduled/poll\_mailbox.rb:14:in `execute' /var/www/discourse/app/jobs/base.rb:292:in `block (2 levels) in perform’ > rails\_multisite-5.0.0/lib/rails\_multisite/connection\_management.rb:82:in `with_connection' /var/www/discourse/app/jobs/base.rb:279:in `block in perform’ > /var/www/discourse/app/jobs/base.rb:275:in `each' /var/www/discourse/app/jobs/base.rb:275:in `perform’ > /var/www/discourse/app/jobs/base.rb:346:in `perform' mini_scheduler-0.16.0/lib/mini_scheduler/manager.rb:122:in `process\_queue’ > mini\_scheduler-0.16.0/lib/mini\_scheduler/manager.rb:70:in `worker_loop' mini_scheduler-0.16.0/lib/mini_scheduler/manager.rb:59:in `block (2 levels) in ensure\_worker\_threads’ ---
### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip) #### Post date: [June 26, 2023, 8:38am UTC](https://meta.discourse.org/t/discourse-unlock/194801/44 "2023-06-26T08:38:57Z")
I’m not familiar with Binance Smart Chain network and how it works with Unlock but from what you’ve given us, it looks like an issue with Unlock and not Discourse? That error message is from Unlock and you should probably go to their GitHub / Discord to get some help. ---
### Author: ![cmdntd](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmdntd/32/192008_2.png) [@cmdntd](https://meta.discourse.org/u/cmdntd) #### Post date: [October 6, 2023, 11:09am UTC](https://meta.discourse.org/t/discourse-unlock/194801/45 "2023-10-06T11:09:41Z")
I can not login to app by metamask ```plaintext https://app.unlock-protocol.com/locks ``` ---
### Author: ![cmdntd](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmdntd/32/192008_2.png) [@cmdntd](https://meta.discourse.org/u/cmdntd) #### Post date: [October 6, 2023, 11:20am UTC](https://meta.discourse.org/t/discourse-unlock/194801/46 "2023-10-06T11:20:34Z")
It seems ok. But you should change to right network first. ---
### Author: ![Titi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/titi/32/333006_2.png) [@Titi](https://meta.discourse.org/u/Titi) #### Post date: [October 29, 2023, 7:01pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/47 "2023-10-29T19:01:08Z")
Hello, Did anyone used this plugin before? Is it possible for you please to share concrete examples of use? ---
### Author: ![Elisee](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Elisee](https://meta.discourse.org/u/Elisee) #### Post date: [January 26, 2024, 6:08pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/48 "2024-01-26T18:08:49Z")
Hello, Is the plugin still working ? I added it but can’t connect to it, nothing is happening at this stage ![image](https://global.discourse-cdn.com/meta/original/4X/9/2/b/92be113431f228c361997ef2b2f42b8f1312773e.png) I’m using Metamask with Polygon ---
### Author: ![cmdntd](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmdntd/32/192008_2.png) [@cmdntd](https://meta.discourse.org/u/cmdntd) #### Post date: [May 20, 2024, 7:45pm UTC](https://meta.discourse.org/t/discourse-unlock/194801/49 "2024-05-20T19:45:48Z")
This just lock categories. Could you develop to lock every topic/post? [Previous page](https://meta.discourse.org/t/discourse-unlock/194801.md?page=1) [Next page](https://meta.discourse.org/t/discourse-unlock/194801.md?page=3)