I’ve successfully deployed Discourse on a Digital Ocean Droplet, but after initiating a rebuild, I encountered problems. Logs: View Here - Notably, there’s an “x86_64 arch detected” message. App.yml Configuration: View Here Has anyone faced a similar issue? Would appreciate any insights or solutions.

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. [image] Discourse Chatbot robot Plugin information_source Summary The Original AI Chatbot for Discourse hammer_and_wrench Repository Link GitHub - merefield/discourse-chatbot: An AI bot with RAG capability for Topics, Chat & Customer Support in Discourse, currently powered by OpenAI · GitHub open_book Install Guide How to install plugins in Discourse heart Sponsorship Please consider becoming an ongoing sponsor of my open source work at a level that suits your or your organisation’s resources and needs to ens… @techwithanirudh’s site is now up and running.

Lines 99 til 101 are in the wrong indentation level, they need one more. See here for a proper example: samples/standalone.yml main - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log

Done! I’m stilling getting the same issue, though

You can try passing the whole YAML file through a linter to check for more issues.

I’ve been facing challenges with my Discourse setup: YAML File and Syntax: I’ve verified my YAML configuration using YamlLint; it didn’t flag any issues. However, a syntax error popped up from a Ruby directory:/usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/config.rb:148:in `block (2 levels) in run_commands': Invalid run command cd (SyntaxError) ... from /usr/local/bin/pups:25:in ` ' Rebuild and Access: I reverted to the default app.yml file and made some modifications. The rebuild was successful. Yet, when I try accessing the site, I encounter these errors: [image] [image] W3M Browser Test: To further diagnose, I installed w3m, a terminal browser, on the droplet. Accessing localhost resulted in a ‘502 bad gateway’ error: [image] SSL Issues I thought this might be a SSL issue and am now renewing the ssl certs Any insights or help would be greatly appreciated!

[image] Anirudh Sriram: 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.

I don’t have a backup of my forum, I’m very new to setting up discourse.

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.

I already have users and data, I don’t want to lose everything and start from scratch

Issue after Rebuilding Discourse on Digital Ocean Droplet

Product Support Self-hosting

JammyDodger September 6, 2023, 12:36pm 13

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.

Topic		Replies	Views
My site is down after I installed a plugin Self-hosting	21	1210	December 7, 2022
My forum goes down when I do launcher rebuild app Self-hosting	15	2065	October 23, 2022
Rebuild app doesnt work Self-hosting	9	1458	September 29, 2016
Rebuild of Discourse fails due to spaces in YAML file Self-hosting	8	1684	April 12, 2018
Site down, error rebuilding!c due to yml error Self-hosting	9	749	September 6, 2023

Issue after Rebuilding Discourse on Digital Ocean Droplet

Related topics