# Getting a '500' error when trying to install

**URL:** https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618
**Category:** Support
**Tags:** custom-header-links
**Created:** [September 3, 2023, 7:43am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618 "2023-09-03T07:43:05Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 3, 2023, 7:30am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/1 "2023-09-03T07:30:05Z")

</div>

Hi. When I try to install, in/via “Recommended” where the bit is listed, I get: “500 error”  
When I go to preview I get this in the centre of the page:

 ![denied](https://global.discourse-cdn.com/meta/original/4X/a/f/4/af4d977d518b853caa96b7c5c9bef34bd64781d4.png)

Any suggestion on why that is?  
I am guessing that my connection to the service is in fact denied but… why.

---

<div class="post-metadata">

### 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: [September 3, 2023, 7:43am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/2 "2023-09-03T07:43:05Z")

</div>

It looks like that’s not the correct link. If you use the one from the OP it should work fine - [GitHub - discourse/discourse-custom-header-links · GitHub](https://github.com/discourse/discourse-custom-header-links)

If you can tell me where were you trying to install that link from I’ll have a check to see if we can update that.

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 3, 2023, 7:56am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/3 "2023-09-03T07:56:54Z")

</div>

When I try with _git_ – [GitHub - discourse/discourse-custom-header-links · GitHub](https://github.com/discourse/discourse-custom-header-links)  
I get the same “500 error”

---

<div class="post-metadata">

### 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: [September 3, 2023, 8:04am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/4 "2023-09-03T08:04:57Z")

</div>

Hmm. 🤔 It seems to be working fine for me (both from the ‘Popular’ section and pasting the [https://github.com/discourse/discourse-custom-header-links](https://github.com/discourse/discourse-custom-header-links) link).

Could you try the ‘install this theme component’ button in the OP as an alternative?

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 3, 2023, 8:09am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/5 "2023-09-03T08:09:33Z")

</div>

I cannot do that as I understand my site, which is a test-lab, would have to be publicly accessible, right?

---

<div class="post-metadata">

### 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: [September 3, 2023, 8:36am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/6 "2023-09-03T08:36:38Z")

</div>

That may explain the old links. Is it up-to-date?

I think another alternative could be to download the zip and upload it that way:

 ![download zip](https://global.discourse-cdn.com/meta/original/4X/9/9/9/999b61b3a4f6bc8174ff34c0fd1221f3e8bad9da.png)

 ![upload zip](https://global.discourse-cdn.com/meta/original/4X/3/7/4/3749e3ead853d8c64db7245f0819b7894d91546c.png)

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 3, 2023, 8:41am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/7 "2023-09-03T08:41:19Z")

</div>

Everything seems to be working a ok, **sidekiq** is, no obvious errors nor warnings.  
Some other bits - e.g category banners - installed via _popular_ okey.  
ver. 3.0.5 / 461966e028  
I’ll try **zip**

---

<div class="post-metadata">

### 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: [September 3, 2023, 8:49am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/8 "2023-09-03T08:49:22Z")

</div>

> [@lejeczek](#):
>
> ver. 3.0.5 / 461966e028

FWIW, the latest `stable` version is 3.1 (and `tests-passed` at least 3.2.0.beta1-dev) so I think you do need to upgrade. 👍

> [@3.1.0: Major Release](https://meta.discourse.org/t/3-1-0-major-release/273447):
>
> Today, we release Discourse 3.1 rocket We’ve completed the 3.1.0 development cycle and pushed out the final release. Check out our blog post, as well as all the 3.1.0.betaX #release-notes topics for details.

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 3, 2023, 9:15am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/9 "2023-09-03T09:15:29Z")

</div>

Not sure if that did it - perhaps destruction & creation of the container did - but now with updated to 3.0.6 version, Discourse can install CHL via _popular_.

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 9, 2023, 7:01am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/11 "2023-09-09T07:01:39Z")

</div>

I keep getting that error for all/any theme &| component now.  
Do these work - I’m asking for when I go to “Preview” I get redirected to: [Theme Creator](https://discourse.theme-creator.io/latest) with a pup-up and a button “View Theme” which if I go for I end up at ‘[discourse - Theme Creator](https://discourse.theme-creator.io/c/discourse/1)’

---

<div class="post-metadata">

### 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: [September 9, 2023, 2:25pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/12 "2023-09-09T14:25:35Z")

</div>

How did you install discourse? Is this a [standard install](https://meta.discourse.org/t/142537?silent=true)? Did you upgrade to the current 3.1 version?

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 9, 2023, 2:58pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/13 "2023-09-09T14:58:09Z")

</div>

Yes. btw - should “standard” install end up having dev release (mine shows 3.2.0.beta1-dev) ?

In some logs I see:  
…

```Started
Processing by Admin::ThemesController#import as */*
  Parameters: {"remote"=>"https://github.com/discourse/discourse-category-banners"}
  Rendered text template (Duration: 0.0ms | Allocations: 1)
Completed 418 in 2ms (Views: 0.4ms | ActiveRecord: 0.0ms | Allocations: 1273)
Failed to process hijacked response correctly : Timeout::Error : Timeout::Error

```

Would the fact that I have Nginx proxy external to the host/node play a role in it? (everything seems to work normal)  
From within container I can _curl_ those URIs — of _view_ of some component which fail with **500** — just a ok.  
Is there a way to get more verbose debug for those bits?  
Components installed via **zip** seem to work okey.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [September 9, 2023, 3:37pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/14 "2023-09-09T15:37:13Z")

</div>

> [@lejeczek](#):
>
> Yes. btw - should “standard” install end up having dev release (mine shows 3.2.0.beta1-dev) ?

Yes, the default branch is “tests passed” (see also [Understanding Discourse release channels](https://meta.discourse.org/t/why-does-discourse-always-install-beta-versions-by-default/264400)).  
The “dev” suffix was added recently.  
[From Discourse 3.2: adding -dev suffix to beta versions under active development](https://meta.discourse.org/t/from-discourse-3-2-adding-dev-suffix-to-beta-versions-under-active-development/273490)

---

<div class="post-metadata">

### 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: [September 9, 2023, 6:40pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/15 "2023-09-09T18:40:08Z")

</div>

> [@lejeczek](#):
>
> `Timeout::Error`

Maybe a performance issue. Enough ram? Other stuff taking all the cpu?

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 12, 2023, 2:46pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/16 "2023-09-12T14:46:01Z")

</div>

> [@pfaffman](#):
>
> Maybe a performance issue. Enough ram? Other stuff taking all the cpu?

I’d not think so, 4 core 8GB of RAM and it’s only freshly installed lab - the very moment Discourse fails that way I can _curl_, within the container, that same URI just fine.

What I think would be helpful here is if I knew how to get/make logs more verbose/debugged - if **devel** reads here perhaps can advice on that.

---

<div class="post-metadata">

### 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: [September 12, 2023, 2:51pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/17 "2023-09-12T14:51:05Z")

</div>

`tail -f /var/discourse/shared/standalone/log/rails/production.log`

or inside the container

`/shared/log/rails/production.log`

Looking back over this, my guess is that you have a docker config problem and it cannot access github. But I’m not sure how that could be true if you did a [standard install](https://meta.discourse.org/t/142537?silent=true), as it would have cloned plugins from inside the container.

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 12, 2023, 3:04pm UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/18 "2023-09-12T15:04:34Z")

</div>

These are the logs I pasted already, earlier - I still hope those could be made more verbose & telling.

I also said, in my last comment, that I can _curl_ those very URI of the **component** which is Github URI, just fine, within the container - you think what you said, docker config, might be the issue really?

---

<div class="post-metadata">

### Author: ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)
#### Post date: [September 13, 2023, 5:15am UTC](https://meta.discourse.org/t/getting-a-500-error-when-trying-to-install/277618/19 "2023-09-13T05:15:25Z")

</div>

Must have been a number of factors — rebuilding container, host’s DNS, … — it works now, no _500_ errors.
