I tried to install my first plugin, the reactions plugin, following this guide. My .yml file looks like this: ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/di…

Hmm. That is rather unusual. And the rebuild was successful? (And the right server. Sounds silly, but has happened before :slight_smile:) And it’s definitely not on your /admin/plugins page?

I didn’t see any errors on the first rebuild after installing the plugin but I tried a rebuild again to see if it would work and it did show errors: error Error: https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz: ESOCKETTIMEDOUT at ClientRequest.<anonymous> (/usr/share/yarn/lib/cli.js:142037:1…

Try this link. [imagen] Announcing Discourse Doctor dev Following the example from Discourse-doctor woman_health_worker , I’ve created discourse-doctor, now included in discourse_docker. If you run ./discourse-doctor, you’ll see something like: DISCOURSE DOCTOR Tue Jul 24…

[imagen] Aaron Walsh: Try this link. I actually just ran discourse doctor and it’s asking if I want to create a publicly available version of the file. I don’t want my information public so is there a way to do it without public availability but still share it?

I’ve always selected N (No) with no issues. I couldn’t specifically tell you the backend of it, but I know this could potentially help you with this issue.

Ok, here is the output of discourse doctor: DISCOURSE DOCTOR Sun Jun 9 16:11:34 UTC 2024 OS: Linux hv-client-35215-device-38240 5.15.0-112-generic #122-Ubuntu SMP Thu May 23 07:48:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Found containers/app.yml ==================== YML SETTINGS ==============…

[imagen] forummaster: error Error: https://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz: ESOCKETTIMEDOUT at ClientRequest.<anonymous> (/usr/share/yarn/lib/cli.js:142037:19) at Object.onceWrapper (node:events:631:28) at ClientRequest.emit (node:events:517:28) at TLSSocket.emitReques…

[imagen] Firepup Sixfifty: I believe this is your fatal error, can your machine successfully access https://registry.yarnpkg.com ? curl -I -L https://registry.yarnpkg.com HTTP/2 200 date: Sun, 09 Jun 2024 16:38:58 GMT content-type: application/json cf-ray: 89128e1899ab8b47-TPA cf-cache-status…

Odd. Is the disk speed for that machine reasonably fast? There’s been issues before with slow disks: [imagen] Continuous Issues when Rebuilding Discourse This post on GitHub also seems to mention Yarn timing out when being installed on a slow disk.

The forum is back up and running after running discourse doctor but the plugin still isn’t installed. I checked updates in the the admin panel and it says a new version of docker manager and discourse is available. Should I update or try to solve this first as is?

No se puede instalar el plugin de reacción

Soporte Instalación

Firepup650 (Firepup Sixfifty) 9 Junio, 2024 16:45 11

Extraño. ¿La velocidad del disco de esa máquina es razonablemente rápida? Ha habido problemas antes con discos lentos:

Tema		Respuestas	Vistas
Continuous Issues when Rebuilding Discourse Self-hosting	6	677	19 Marzo 2024
Discourse Installation Failure on Fresh Server: FAILED TO BOOTSTRAP Self-hosting	11	1046	7 Mayo 2023
Yarn error Self-hosting	23	602	28 Junio 2024
Site down, rebuild failed due to landing plugin Self-hosting	16	1435	22 Julio 2022
Help with discourse rebuild failure Support	3	143	18 Diciembre 2024

No se puede instalar el plugin de reacción

Temas relacionados