### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [5 september 2023 om 16:25 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/1 "2023-09-05T16:25:58Z")
I’ve successfully deployed Discourse on a Digital Ocean Droplet, but after initiating a rebuild, I encountered problems.
- **Logs** : [View Here](https://pastebin.com/ch3KQyJQ) - Notably, there’s an “x86\_64 arch detected” message.
- **App.yml Configuration** : [View Here](https://pastebin.com/tTqHLy1F)
Has anyone faced a similar issue? Would appreciate any insights or solutions.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [5 september 2023 om 16:41 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/2 "2023-09-05T16:41:00Z")
Lines 99 til 101 are in the wrong indentation level, they need one more. See here for a proper example:
>
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [5 september 2023 om 16:44 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/3 "2023-09-05T16:44:14Z")
Done! I’m stilling getting the same issue, though
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [5 september 2023 om 18:03 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/4 "2023-09-05T18:03:00Z")
You can try passing the whole YAML file through a linter to check for more issues.
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 06:02 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/9 "2023-09-06T06:02:47Z")
I’ve been facing challenges with my Discourse setup:
1. **YAML File and Syntax** :
2. **Rebuild and Access** :
3. **W3M Browser Test** :
4. **SSL Issues**
Any insights or help would be greatly appreciated!
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 10:20 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/10 "2023-09-06T10:20:05Z")
My forum’s down from 2 days.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [6 september 2023 om 11:34 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/11 "2023-09-06T11:34:56Z")
> [@techwithanirudh](#):
>
> 1.
> - I thought this might be a SSL issue and am now renewing the ssl certs
It might be, if you reached their request limit. How did your review end?
Do you have a backup of your forum, and did you try restoring it on another server? If my forum were down for 2 days, I’d take 30 minutes to try that.
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 11:35 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/12 "2023-09-06T11:35:38Z")
I don’t have a backup of my forum, I’m very new to setting up discourse.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [6 september 2023 om 12:36 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/13 "2023-09-06T12:36:17Z")
If you’re starting from scratch, you should try installing a fresh instance using a new subdomain. That should sidestep the letsencrypt rate limit if you’ve hit it. 👍
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6 september 2023 om 12:44 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/14 "2023-09-06T12:44:18Z")
Having cloudflare in front of your site is one way to see that let’s encrypt fails. I’d recommend using DNS-only until you’re sure that let’s encrypt is working correctly.
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 13:17 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/15 "2023-09-06T13:17:13Z")
I already have users and data, I don’t want to lose everything and start from scratch
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 13:19 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/16 "2023-09-06T13:19:00Z")
Thanks for the tip! It’s now on DNS only! 🙂
Edit: I’m now also getting  error,
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6 september 2023 om 14:16 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/17 "2023-09-06T14:16:31Z")
It sounds like the easy solution is to move to a different subdomain, or wait a week until let’s encrypt will give you a cert. The harder way is to add a second subdomain that points to your server and modify your `app.yml` to request a cert for both subdomains. [Set up Let’s Encrypt with multiple domains](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains/56685). Since it appears that your problems started because you’re having trouble with YML formatting, this rather complicated solution might not work for you.
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [6 september 2023 om 15:34 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/18 "2023-09-06T15:34:23Z")
> [@techwithanirudh](#):
>
> I already have users and data
Then you absolutely need to be sure you have a backup, and have it somewhere safe.
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [6 september 2023 om 15:58 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/19 "2023-09-06T15:58:23Z")
Thanks for the idea, I used a different subdomain now, but I’m having the same issue.
A ‘502’ and a ‘Connection Refused’.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6 september 2023 om 17:10 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/20 "2023-09-06T17:10:44Z")
> [@techwithanirudh](#):
>
> I’m having the same issue.
Does your DNS for the subdomain point to that server IP address? And you don’t have any other A or AAAA records for the subdomain?
I recommend that you run `./discourse-setup` that will check that incoming connections to your domain are reaching your server.
Can you ssh to your server by hostname with `ssh user@subdomain.yoursite.com` (or whatever your subdomain?
---
### Author:  [@techwithanirudh](https://meta.discourse.org/u/techwithanirudh)
#### Post date: [7 september 2023 om 04:51 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/21 "2023-09-07T04:51:27Z")
> [@pfaffman](#):
>
> Does your DNS for the subdomain point to that server IP address? And you don’t have any other A or AAAA records for the subdomain?
Yes, I’ve ensured the DNS for the subdomain points to the server IP address, and there are no other conflicting A or AAAA records for it.
> [@pfaffman](#):
>
> I recommend that you run `./discourse-setup` that will check that incoming connections to your domain are reaching your server.
I’ve executed the command and here’s the output
**Latest Update:** Post-execution of `discourse-setup` , navigating to [home.techwithanirudh.com](https://home.techwithanirudh.com/) results in a “502 Bad Gateway” error. Here’s a snapshot of the error (referring to the attached image).
> [@pfaffman](#):
>
> Can you ssh to your server by hostname with `ssh user@subdomain.yoursite.com` (or whatever your subdomain?
Absolutely, SSH-ing into the server using the hostname works perfectly.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [7 september 2023 om 06:29 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/22 "2023-09-07T06:29:38Z")
I worked with @techwithanirudh offline to resolve this … @techwithanirudh wasn’t aware of the chatbot uninstall instructions.
The giveaway here (atm) was the 502 due to the container not starting properly due to the index remaining in the db without supporting code in the postgres library. The uninstall instructions remove the index from the db so you can safely build without building the index library.
> [@Discourse Chatbot robot](https://meta.discourse.org/t/discourse-chatbot-now-smarter-than-chatgpt/256652#uninstalling-the-plugin-important-13):
>
> information_sourceSummary The Original AI Chatbot for Discoursehammer_and_wrenchRepository Link [GitHub - merefield/discourse-chatbot: An AI bot with RAG capability for Topics, Chat & Customer Support in Discourse, currently powered by OpenAI · GitHub](https://github.com/merefield/discourse-chatbot)open_bookInstall Guide [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157)heartSponsorship Please consider becoming an ongoing [sponsor of my open source work](https://github.com/sponsors/merefield) at a level that suits your or your organisation’s resources and needs to ens…
@techwithanirudh’s site is now up and running.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [7 oktober 2023 om 06:30 UTC](https://meta.discourse.org/t/issue-after-rebuilding-discourse-on-digital-ocean-droplet/277877/23 "2023-10-07T06:30:35Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.