I am trying to setup Companion, but am having issues with my integration.
I have an nginx reverse proxy sitting in front of Companion stand-alone so that I can provide valid https. So far everything works (as in connecting to oauth service such as dropbox), but I cannot actually initialize the upload. When I try to do so, in the browser console I get the following error:
However, if I upload using the “My Device” option which uses TUS, there is no issues. I have TUS setup the same way as I’m trying to set up Companion (behind a nignx reverse proxy).
Here is my nginx reverse proxy config (just the location block):
What about your includes? I’m mostly looking for a bit that e.g. redirects to use trailing slashes. That could throw a 301 that we’re not expecting, maybe.
I’m also wondering what happens when you target Companion directly, does it work then? Or also throws the 301?
Ok, I went ahead and spun up a server and only installed nginx and done the reverse proxy that way and everything works fine. I’m thinking it’s something conflicting on the main box.
Is there maybe also HAProxy installed or is it behind a service like ALB or CloudFlare which can do 301 redirects on your behalf? If not and it’s really nginx, enabling the debug log on Nginx will reveal why it is redirecting.