Tradam.fyi

Pydio really sucks LMAO

Theme: Rant

Created: September 13th, 2020 01:39
Updated: September 13th, 2020 19:32

Eyes laid on this: 21


Edit:

So originally this was a post about how to install Pydio. Don't do that, Pydio is a mess which has a useless forum that has countless questions on it left unanswered. Multiple times I found my exact issue on the forum, one one of 2 states:

  1. The user left a very valid question, completely unanswered by any developers.
  2. The user left a question, developers actually replied(😲) by asking for more info(error log and such). The user then replies and the dev never responds(lmao)

I say all of this from experience, I had my setup complete after following the below steps. But uploads started failing even below 100mb(thats right, all uploads failed above 100mb). So I decided to restart the server. Pydio would never launch again from this server. Trying to boot it gave it all kinds of errors. I'm giving up on using someone else's poopy cloud share service type program and I'm just going to stick to using sshfs for the time being until I am able to code my own non poopy cloud solution. I left my instructions below I guess cuz eh why not. If you wanna follow them, good luck with Pydio lmao.

End of edit.

So I wanted some kind of personal cloud hosting solution type thing, where I could set it up on a server box I have and be able to upload and download files to and from it(with a website interface). Although I do want to code my own using ruby on rails, it's a bit time consuming and considering I have school assignments to focus on I decided to put that on the back-burner. Instead I plan to use a premade hosting solution and set it up on a server box.

There are actually quite a few to choose from(Nextcloud, Seafile, etc.) so I decided to pick one that is not the biggest, and has a logo I like(yea I know, not the best decision making process, but eh this is supposed to be a temporary solution so whatever, no point wasting too much time) so I opted to go with Pydio. They have a cool planet logo.

It was really difficult, confusing, and time consuming to get this up and running so I suppose I will make a little guide for how to install it on Artix as that is what my server boxes use. Would I use it again if I had to choose from the start? I don't know. I'm not too certain any of the other solution would be any easier or have better features or whatever. I guess I don't care that much since I am planning to make my own (less bloated) solution. I will also be using nginx as a way to serve Pydio, as it's confusing and poopy to try and serve Pydio directly to the web, and you want to use nginx anyway so you have the ability to serve multiple services on the server box.

Logically, I went to the Arch Wiki first to see their guide for installing it. Don't do that. This is probably the first time I'm recommending to NOT use the Arch wiki, because all the other times I have used it, it has been a life saver. Not in this case, the AUR has a version of Pydio that I could not figure out how to use, and the Arch wiki guide also seemed to either be outdated or just not thorough enough.

Instead follow this page. Follow everything in this guide, except the line where it says to

setcap 'cap_net_bind_service=+ep' cells

This will break nginx as this command will allow Pydio to hold the 80/443 ports hostage. At the end it says to do

./cells start

but you need to do (keep reading before you do this)

./cells install

first. Not a very good guide, but good enough so its gets a C-. Next we set up nginx.

Follow the guide from the same website. Here they talk about Internal and External Urls. They do not do a good enough job explaining this because I was quite confused throughout so I will try to do a better job here. Internal Url is actually used by Pydio, whatever you set this to is where you need to point nginx to listen to. nginx will go to this url, get data from Pydio and then send it out to the web. External Url is where I got confused and mislead. Pydio doesn't actually technically do anything with this url. You need to set this to be whatever url/ip that points to nginx, which will then grab data from Pydio. That means if I want something like example.com to be where I can access Pydio, that is what you set the External Url to. The reason for this is that once the Pydio website is loaded, it will send requests back to nginx, and to do that successfully it needs to know the correct url it came from, to ask nginx correctly. I made the mistake of setting this to localhost, as I thought the External Ip is the ip where nginx can pick up from, but it is not. That is the internal ip. Now that you know this you can go back in the guide to run the installer for cells, or keep reading and do the installing after.

Ok so what do you need from this page of the tutorial? Copy the "Basic NGINX reverse proxy configuration" and place this into a .conf file in your sites-available folder. Because this config is given to you pre-broken(because of course it is) you need to fix it. First, each line that has listen on it, you need to remove the following: any word with "http" or "https", and any word that has the [::]: pattern. Not sure why these are here as they seem to only break nginx, and work flawlessly without those included. Next any part that has an ip address, change to your internal url. Any part that has the url example.pydio.com you change to whatever your "External Url" is as explained earlier. This is what your website is that goes to Pydio. Note that this doesn't have to be "url" but it can be the ip of your server box as well.

After all that shenanigans, Pydio should work. Hopefully I didn't leave anything out important because I also had to do a few other extra steps to get this working for my set up(I used cloud flare rdns, along with cloudflare ssl) so I did have a few extra shenanigans to deal with.

I also have a few other issues with Pydio that I haven't been able to fix. First off the theme CANNOT be changed or edited without paying for their EnTeRpRiSe EdItIoN. Ugh. And second, I am unable to upload files larger then ~125mb because the upload begins looping before failing outright. No changing of settings in Pydio or nginx fixes this and I kind a just gave up for the time being as I have school things to work on. Will I try to fix this issue? Well maybe. I don't know yet. It might not be worth spending the time trying to learn how this very specific system works, such skills not being transferable, and the system being so anti-customisation without paying, so therefore having little value to me. I will most likely just continue using this temporary system until I have time to create my own that I can be satisfied with, rather then frustrated trying to fix or use this one. It does suck, but luckily for me the files I need uploaded at the time can be split into smaller files so that's what I'll be doing.

Let me know if this guide/rant sucked or whatever, spent like 5+ hours installing/setting up Pydio, and like maybe 30 mins writing this.


Back to Index