A user, ckhawand, seeks help installing Discourse on their Hostinger VPS running Ubuntu 16.04, expressing frustration with technical hurdles like Apache conflicts and Docker issues. merefield encourages self-learning, highlighting the valuable skills gained, and guides them toward the official Docker installation guide. The discussion reveals challenges with port conflicts and Docker setup, with ckhawand eventually seeking external help. Other users, PabloC and NPH, offer paid installation services, with JammyDodger suggesting posting in the Marketplace category for broader visibility.
So… I recently got a VPS (hostinger VPS plan 6), well, a powerful one let’s say, here are its specs:
|CPU Cores|8|
|Total CPU Speed|19.2Ghz|
|Memory|8Gb|
|Disk Space|160Gb|
|Bandwidth|8000Gb|
Alright, so I have no experience in VPSs, tried many tutorials online, that told me I have Apache already installed.
I’m using Ubuntu 16.04, and I could provide with SSH details, if anyone can install it for me
The discourse would be live here: http://forum.cksoftwares.com
Just MHO, but getting someone to help you with a one off install is all very well, but won’t help you for the long term - you need to support your installation in Production and that requires getting dirty occasionally. Without the experience of setting it up yourself that is going to be tricky.
Then again, perhaps you can hire someone to install and support your instance going forward:
Don’t give up! There’s a whole community here to help you that will be even more responsive if you ask about specific issues and roadblocks.
btw, you should definitely make this ‘https’ when you get round to it (which is just a case of a setting in app.yml) - you want your traffic to be encrypted to protect yourself and your users.
Okay, after deleting Apache and NGINX using sudo apt-get remove apache* sudo apt-get remove nginx*
Then restarting the server, I have been able to proceed to inputing my forum infos.
However, I’m stuck with the Device "docker0" does not exist. issue
checked some topics here, but none of them worked
I think your issue is down to how the vanilla build on your hosting VPS is configured … there is probably a really simple modification to get it working.