# Standalone Uppy companion and Uppy dashboard - nginx proxy pass

**URL:** <https://community.transloadit.com/t/standalone-uppy-companion-and-uppy-dashboard-nginx-proxy-pass/15348>\
**Category:** Uppy\
**Created:** [July 3, 2020, 5:43pm UTC](https://community.transloadit.com/t/standalone-uppy-companion-and-uppy-dashboard-nginx-proxy-pass/15348 "2020-07-03T17:43:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tamici](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/tamici/32/259_2.png) [@tamici](https://community.transloadit.com/u/tamici)\
**Post date:** [July 3, 2020, 5:43pm UTC](https://community.transloadit.com/t/standalone-uppy-companion-and-uppy-dashboard-nginx-proxy-pass/15348/1 "2020-07-03T17:43:39Z")

</div>

Hi,  
I’ve been trying to set up Uppy for two days now and I need help. I’ve used the demo on [uppy.io](http://uppy.io) and it’s a slick product, but so far I haven’t been able to make it work.

I’m building a web application with go on the backend and a little bit of js in the frontend.

To avoid CORS requests I want to have the companion under the same domain as my application.

```auto
location / {
    ...
    # proxy to web 
    proxy_pass http://127.0.0.1:8100;
}

location /uppy/ {
	...
    # proxy to standalone uppy companion
	proxy_pass http://127.0.0.1:8200;
}

```

I now have Uppy companion running on `https://mydomain.com/uppy/companion/`, and I can see that it works by going to, for instance, `https://mydomain.com/uppy/companion/metrics`.

Now comes the pain.

In the frontend as a companion url I set `https://mydomain.com/uppy/companion/` because `/uppy/companion/` is for whatever reason transformed into `https:///uppy/companion/`.

And I get all sorts of errors:

When clicking on any cloud provider (I’m using the Dropbox, Google Drive and Onedrive plugins) to connect

```auto
Error: Could not get https://mydomain.com/uppy/companion/drive/list/root.
Error: Failed request with status: 404. Not Found
message: Not Found

```

Can anyone point me in the right direction? I’m open to change my setup, I just want to get this working with a standalone server.

Thanks,  
Tommaso

---

<div class="post-metadata">

**Author:** ![ifedapoolarewaju](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/ifedapoolarewaju/32/36_2.png) [@ifedapoolarewaju](https://community.transloadit.com/u/ifedapoolarewaju)\
**Post date:** [July 7, 2020, 8:56am UTC](https://community.transloadit.com/t/standalone-uppy-companion-and-uppy-dashboard-nginx-proxy-pass/15348/2 "2020-07-07T08:56:47Z")

</div>

Hi there, if your Companion is running at `https://mydomain.com/uppy/companion/` then you need to set the [server.path option](https://uppy.io/docs/companion/#Options) to `/uppy/companion`

so something like:

```auto
{
    server: {
          path: '/uppy/companion'
    }
}

```

---

<div class="post-metadata">

**Author:** ![tamici](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/tamici/32/259_2.png) [@tamici](https://community.transloadit.com/u/tamici)\
**Post date:** [August 5, 2020, 4:36pm UTC](https://community.transloadit.com/t/standalone-uppy-companion-and-uppy-dashboard-nginx-proxy-pass/15348/3 "2020-08-05T16:36:07Z")

</div>

Hi, thanks for taking the time to reply.

I’ve made some progress since posting here in part thanks to your suggestion. I’m now at the point where  
I can see the OAuth screen for the different providers,

I can accept the request of permissions, then I’m redirected to the page with the uppy dashboard. So far so good.

The issue is then that I get a 401 when the dashboard makes a call [https://mydomain.com/uppy/companion/drive/list/root](https://mydomain.com/uppy/companion/drive/list/root)

I think I’ll revisit the companion when 2.0.0 is out of beta. I’ll stick with tus for now.