Having lots of problems installing discourse.
Cant use two containers because of a weird ssh container problem.
Single container.. app.yml leads to duplicate containers.
Tried lots of ai assisted fixes but we’ve been going round in circles.
Docker seems to be very flaky atm.
After 3 days of multiple attempts I’m giving up for the weekend.
Has anyone successfully installed a self hosted instance in the last day or so?
Did you try starting on a brand new server and following the standard install guide?
Please forget two container setups, unless you know what you doing.
2 Likes
Yes new server.
Said I’d tried both methods.
Done two container many times.
Following guide to letter.
How your reply is a solution to my problem beats me.
Falco’s reply is an attempt to gather more information, quite necessary given the lack of relevant information.
Why are you being rude to someone attempting to gather further information to help you?
The only useful information in your post is:
This line is just confusing:
since ssh has nothing to do with docker.
1 Like
It does, its an old method of accessing a container.
Last line of web_only.yml
Can you clarify, following the issues you had, did you spin up a brand new droplet and try again?
That’s a warning. Not an error.
Sounds like not Discourse’s fault. Does
docker run hello-world
work?
Just ran a 2-container install and it worked as expected.
And then a ran a app.yml install and it worked too. The specs pretty much guarantee that a standard install works.
3 Likes
What is your server specs? Recently discovered that a 4g ram server requires swap.
2 Likes
Was showing as FATAL. Otherwise I’d have been unaware as in all previous installs.
I had docker problems, two containers with web_only were running?
Possibly caused by Docker and unauthorized requests so I had to get a docker hub login.
Then I had to work out I needed to be root when I logged in.
I also had mail delivery problems because DO have quietly blocked Port 587 -March 2025 and thought it was my credentials until I’d tried everything. I’m not sure SMPT domain is being filled in correctly.
Port 2525 works. (Mailjet)
(Sam) All these errors and I’m rebuilding the server from scratch each time for future stability.
I don’t post here any more as a rule but wanted to leave the info about the port block and docker hub.
I was on the receiving end of intense bullying by some of the ‘team’, (go team!) after I used a DM to one, unaware it would be read by everyone and about 40 piled on with comments or likes. A nasty experience after years of posting.
So I stay well clear of posting. I’m read only.
Is there a competition on for most solutions? Its not helpful especially if there is no solution offered.
So I run into LetsEncrypt limits and … when I get out of SSL jail I’m confident … ok fairly confident it will work.
Perhaps this Docker Hub login requirement needs to go in the official install. It seems necessary. .. as root!
I’m not sure about memory. I was using the $8 Intel on DO. Then after a couple of failures, I upped it to a $32 dollar Intel (free credit to burn) as I thought it would speed the failure process up.
Once I get an instance up & running I really need to go back to the cheapest until I launch the site.
1 Like
This post of mine has the info for setting up a swap file.
I think my 4core 4g instance is around $8/month.
Saw DO post here recently about them blocking 587.
Not sure but if having mail problems. Look into using www.brevo.com they have a free tier that may work well to test. It gives 300 emails free a day
1 Like