@mewmew I hate peertube already.

@shebang why?

@mewmew Because its being a bitch and the logs aren't telling me why. In fact the logs report everything is peachy keen. The proxy seems to be setup perfectly fine, but yeah just a blank page and I have no clue as to why its doing that.

OR WHY THAT WOULDNT GENERATE AN ERROR IN THE FUCKING LOG.

@shebang looks like your reverse proxy isn't serving the files - it's not a problem with PeerTube it's an issue with your nginx config

@mewmew No idea why though. Its definitely pointing to the server, and the server is definitely listening on the correct address. ​

@shebang @mewmew Cry to curl the upstream server from inside the host (eg `curl 127.0.0.1:5000`). Do you get the result you expect?

@alex @shebang upstream server isn't the issue, it's the static files.

@mewmew @alex Yeah, its looking on the proxy server for the files instead of the peertube server. But I'm clueless as to why for the moment. I must be blind and missing something important...

@shebang @alex wait, that makes perfect sense - it loads the files from the local filesystem, which is where apache is running. You need to run the reverse proxy on the same server as PeerTube (then, put a reverse proxy in front of that on your proxy server).

@mewmew @alex Ooh I need two webservers of course... argh lemme think here

@shebang @alex well, you're not supposed to have it behind a proxy on a different machine. You could also just mount your storage directory as s3fs and use redirects but that's more complex (don't recommend)

@shebang @mewmew The terminology in this thread is getting confusing. I think you need only one physical server. There are 2 software servers: the PeerTube server and the static file server. The static file server has to serve static files then proxy other requests to the PeerTube server.

@alex @mewmew Right.

But we've got a main proxy server here that forwards requests to the real servers based on hostname. So that adds a big fat layer of complexity.

@shebang @mewmew Do you mean you have freespeech.host and freespech.tube both pointed at one load balancer that forwards requests to other servers on the internal network? I have a similar setup on Gleasonator and I just serve the staticfiles directly from the load balancer. It does complicate things but I use Ansible to automate it.

@alex @mewmew Exactly. I suppose I could just serve the static files locally but that will be upgrading a pain in the butt. I'd rather that each bit of software be its own contained thing though.

@shebang @mewmew Ahh okay. Are you using Nginx on the proxy machine? I haven't tried this yet, but I think HAProxy might be able to forward the full HTTP request to the upstream machine including the domain, so you might be able to run Nginx on the upstream machine. Been wondering how to solve this problem myself.

@alex @mewmew Yeah the proxy main is nginx. Its working pretty well for a number of things, but peertube is being a bit more difficult. It adds a lot of complication between the peertube nginx wants to server ssl but that the proxy handles that so I need to fuckulate things and see how it goes, I guess.

@alex @mewmew and holy shit my words are all over the place. You get the gist of what I'm trying to say here.