Follow

Why do I never have any luck trying to install Pleroma?

It wouldn’t work on a Raspberry Pi and it won’t work on an Ubuntu server.

Stupid Pleroma.

@alan Was wondering how that project was going... from pre-vacation, no? I set mine up over freebsd and don't remember it being too much of a hassle ~ haven't tried on the other platforms. Where did things go awry?

@MindOfJoe I gave up months back and went with Mastodon on my Pi, but my old desktop PC was defunct so I put Ubuntu server on it to give it another go.

I’m getting up to the point where the newly-created database is migrated to Postgres but the migration throws up a bunch of errors about the user/DB password being incorrect.

@alan The only way I could get it to work on Ubuntu was to install the OTP version. See if that makes a difference for you? https://docs-develop.pleroma.social/backend/installation/otp_en/

@ray I started to do that but I didn’t know how to create the scripts and where to save them 😔

@alan Hmm the directions I shared don’t have scripts. They are all commands to execute at prompt. Where are you stuck in it?

@ray I was copying and pasting all the commands but the $shell command opened up a different dialogue and I’m not sure the commands I entered were being registered.

The section “Installing Pleroma” at docs-develop.pleroma.social/ba looks more like a script rather than individual commands.

@alan I guess it could be scripted but I entered each command individually at the prompt, step by step. I believe that was the intention of it.

@ray I’ll need to try it again then.

As in the screen shot, there appear to be commands and what appears to be a script but obviously I’ve misinterpreted it.

I refuse to let it beat me when it can clearly be installed with ease by many other people 😂

@alan I saw it as a long list of commands to execute with explanations behind each. ; ). Go for it! I’m not as technically oriented as most here but I kept at it and got it working. My mistake was I accidentally skipped a step or two; it’s a long ass list of commands to do!

So I backtracked and started over. It worked! Now I’m too skeered to update it lol.

@ray 😂

I’m sure I’ll get there eventually. Getting it working on Raspios was always going to be hit or miss but there’s no reason why this shouldn’t work on Ubuntu.

@alan @ray

Sorry for the late rejoin. I just spun up an ubuntu 20.04 server vm in virtualbox and followed the instructions here: https://www.howtoforge.com/how-to-install-pleroma-social-network-platform-on-ubuntu-20-04/ . The instructions describe deploying pleroma, postgresql, and nginx, all on the same box.

The only mistake I found was that, while they did update the package sources to include postgresql and their signing key, they didn't give the command to install it afterward (as root, apt install postgresql ). I used a self-signed cert rather than certbot since I was installing / testing on my laptop, but otherwise followed the instructions. New instance running fine ~ no problems. I don't expect you'd see any problems here with the latest ubuntu (21.something).

The trickiest pieces that would be easy to screw up is making sure you're root when it says root, pleroma when pleroma, and postgres when postgres. The command prompts ("$") don't indicate when you're root or a different user, so take care. Otherwise, a bunch of cut & paste.

If something is screwed up with the pleroma db, I'd suggest dropping the pleroma database as well as the pleroma (or whatever) user from postgres and regenerating the config, answering the default pleroma, pleroma, and autogenerated for the user, the database, and the password, and try continuing from there.
@alan @ray

[That's for a clean install, of course ~ not for a mastodon-to-pleroma migration. Suggest seeing if you can get the clean one running first before tackling anything else.]

@MindOfJoe @ray I’m trying a clean install because I want to set up a new instance. If that eventually works, I want to set up a second Pleroma instance on the server and then migrate my Mastodon instance over. I’ve found a script for it, so it’s worth a go.

@MindOfJoe @ray I was very careful with which user I was entering commands and am fairly certain I didn’t miss anything out, but who knows?

Setting up a certificate with Certbot worked fine.

I’m going to drop the databases and database users and try to go again from there.

Thanks for trying it for me to see what I could be doing wrong- I appreciate it 👍🏻

@alan @ray No problem. There are probably lots of valid instruction sets out there (these are not the ones I initially used); I just wanted to run through one myself so I could certify it worked before suggesting you try it. ✔

@MindOfJoe @ray I thought it would be sensible to use the official guide but I’ll have a look at the one you posted.

@alan @ray All the sites duplicate each other and occasionally add tweaks or commentary. FWIW, I just googled ubuntu & pleroma and picked one near the top that looked readable and ran it 🤷

I'm not the authority ~ just sayin' that ~ just now, using 20.04 ~ that link worked. fwiw 😁
@alan @ray LOL ~ well, get on it, slacker! Not like it's midnight or anything there ~ sheesh! 😉

@MindOfJoe @ray True; it’s not even 11pm yet and I only got up for work at 2am this morning 😜

@alan @ray Yeah, I saw your first post of the morning ~ I was up. Get busy! :-p

@MindOfJoe @ray I bet you’ve had at least 3 naps since then 😴 🤪

@alan @ray Look at us all, living the dream ~ lol 💤
Show newer
@alan Mind if I provide a just-happened-a-moment-ago success story with Pleroma?

I have been meaning to move my mycrowd.ca instance from a VPS to a dedicated server for weeks now. The VPS runs Debian, the dedicated runs Gentoo.

I dumped & copied the DB over, ensured the DB user was setup the same with ownership, copied the user account (containing the whole pleroma setup) over, did the DNS, then certbot and nginx bits. Utilized the init script provided by pleroma (with some adjustments for user/port/runfile specifics, etc.) after running a "MIX_ENV=prod mix compile" to ensure the build was going to be fine on the new server.

Things built fine, the init script fired things up appropriately, and I was back in business after a full migration. I think I might have had about 15 minutes of outage on the site, so for farting around with a move like this while doing other work was a success story for Pleroma as far as I'm concerned.

Now, these are things *I should* be able to do without much or any stress, so I'm not making a suggestion here that you or others shouldn't have issues, not at all. I understand there's quite a number of moving parts and if something doesn't go quite right it could be tricky to deal with.

I'm looking forward to hearing further about what's gone on with your install attempt.

@kinetix I’ll give it another go tomorrow.

I have no idea what the issue with authentication/passwords was when trying to migrate the DB.

I even logged into the the DB and then manually changed the password to the one in prod.secret.exs, but still no cigar.

I tried a few times with DBs of different names, so I’ll need to delete those and the installation folders before I try again.

Ideally, I want to set up a new instance and migrate blimey.social to a second Pleroma instance.

@kinetix Well done for migrating everything over successfully 👍🏻

@alan Oh, I presume then the issue must've come during this section?

"# Run the config generator
su pleroma -s $SHELL -lc "./bin/pleroma_ctl instance gen --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql"

# Create the postgres database
su postgres -s $SHELL -lc "psql -f /tmp/setup_db.psql"

# Create the database schema
su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"
"

If you still have the /tmp/setup_db.psql file I wonder if it will have the user creation bit that it used? I *think* the password that winds up in the config file is md5 hashed/encrypted - you may have a config/setup_db.psql file too, hopefully, if you don't have the one in /tmp any longer. I still have mine and it does a "CREATE USER blah WITH ENCRYPTED PASSWORD 'ThePasswordStringShownInprod.secret.exs'", so hopefully this helps if you are looking to fix stuff by hand again.

Hope something in here is useful!

@kinetix Thanks for the suggestion- I’ll look at those files tomorrow to see if I can find anything!

If I can’t fix it, it only takes 10 minutes to reinstall Ubuntu server 😬

Sign in to participate in the conversation
Blimey Social

This is a private instance for family and friends only.