Problems installing on existing EC2 server

AI-generated summary

Problems installing on existing EC2 server

User greg_c is experiencing issues installing Discourse on an existing Amazon EC2 server. The installation process caused the server to become unresponsive, and greg_c suspects it may be due to high CPU usage. After regaining access, greg_c ran discourse-doctor and found an error related to a port being in use.

JammyDodger and crcoli7307 offered assistance, suggesting that the installation process might take a while and recommending alternative SSH methods or running ./launcher rebuild app. crcoli7307 also warned that running multiple websites on the same server as Discourse can cause issues and provided a link to relevant documentation.

Frustrated with the process, greg_c decided to opt for hosted Discourse instead. JammyDodger and others offered support, mentioning alternative hosting options, including Discourse.org’s hosting and pfaffman’s dashboard, which can automate the installation and configuration process.

Truly, I would never have expected a simple install of forum software would just wreck my amazon ec2 server.

I can’t even connect to it now.

What the hell is it doing?

Hello and welcome @greg_c :slight_smile:

From the screenshot, it looks like it’s installing Discourse? Have you had any errors at all?

It just disconnected my putty session, no idea if it finished

seems that it uses massive cpu or something causing everything to pause during install.
I can log back in.

Its not the only domain on the server, maybe getting confused by that, hard to say.
I ran discourse-doctor and I think I saw an error about unable to use a port since in use.

idk will have to look around.

The part of the install in which the screenshot was taken from normally takes a while to complete from personal experience. Perhaps try using ssh from the Windows Command Processor (aka Command Prompt) instead of PuTTY, doubt it will make a difference but try connecting from ssh over command prompt and run ./launcher rebuild app since it seems like you’ve already completed the configuration.

It’s possible, maybe try installing Discourse on a clean droplet instead of one with other websites. If you have multiple websites and Discourse running on the same server, you must follow the instructions outlined in this topic:

Yeah I think I will just get it hosting, $100 a month is a lot but better than me spending my time on thjis.

Ha. Yes, self-hosting isn’t everyone’s cup of tea. :slight_smile: There are quite a few hosted options though, as well as being able to pay someone to set it up for you initially (and then you maintain it). We even have free trials for our hosting if you fancy checking it out before committing to a hosting option - https://www.discourse.org/pricing

Fair enough. Good luck! Let me know if you need anything.

No one is unhappy with discourse.org hosting. My new dashboard (https://dashboard.literatecomputing.com/) will do the installation and configure mailgun and create a digital ocean droplet (or use a fresh ec2 that you create). Running on a server that’s doing something else is a bit of a chore though.