How to use proxy with budibase

[rolandwang19]

I've set tried everything I can find online, and can't seem to get budibase to use the proxy on my linux server. I've set the proxy in every example I could find online, and ran the container with the proxy. I'm able to curl with the proxy on the server and everything works fine. I just can't get the application to call an external API no matter where I've tried to set the proxy.

/etc/systemd/system/docker.service.d/http-proxy.conf
systemctl edit docker.service
/etc/sysconfig/docker
/etc/yum.conf
/etc/environment
~/.docker/config.json

sudo docker run -d -t
--env http_proxy=""
--env https_proxy=""
--env HTTP_PROXY=""
--env HTTPS_PROXY=""
--name=budibase
-p 10000:80
-v /local/path/data:/data
--restart unless-stopped
budibase/budibase:latest

[ThomasK33]

The GLOBAL_AGENT_HTTP_PROXY and GLOBAL_AGENT_HTTPS_PROXY env variables did the trick for me

[shogunpurple]

@rolandwang19 what does your run command look like exactly? Looking at the above - is it:

sudo docker run -d -t
--env GLOBAL_AGENT_HTTP_PROXY="http://something.net"
--env GLOBAL_AGENT_HTTPS_PROXY="https://something.net"
--name=budibase
-p 10000:80
-v /local/path/data:/data
--restart unless-stopped
budibase/budibase:latest

[rolandwang19]

Yeah, that's exactly what it looks like. I also tried altering the docker-compose file with the added environment variables and get the same when I use docker-compose

[shogunpurple]

maybe a silly question - but you have changed the -v /local/path/data:/data to a valid path on your machine?

[rolandwang19]

Yeah, no dice. Even tried removing it.

[rolandwang19]

Actually, what path should actually be used? I mapped to local path, and I checked the container and see that it exists, but what's the purposed of the volume and what should actually be in the local path data folder?