Dealing with corporate proxy


(Liam McArdle) #1

I originally posted this issue in the “Troubleshooting email on a new Discourse install” (Troubleshooting email on a new Discourse install), as I originally encountered it when trying to create my first user. However upon further investigation, it looks like it is a wider issue related to how the corporate proxy URI is set in the environment variables.

Per this issue, Troubleshooting email on a new Discourse install, I had to modify containers/app.yml to add http_proxy: http://some-corporate-proxy-address.com:port-number. This got me over my initial issue with bootstrapping the app. Once bootstrapped, I was able to start the app and visit the webpage. Clicking “Sign Up” and entering my corporate email address however did NOT result in an email. troubleshooted that issue and verified that yes I am able to send mail from that server. However, I found that I was not able to run any rake tasks, i.e.:

./launcher enter app
rake admin:create

or even:
./launcher enter app
rake -T

all rake tasks give me the error:

URI::InvalidURIError: bad URI(is not URI?): http_proxy=http://address-to-my-proxy:80
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-twitter-1.0.1/lib/omniauth/strategies/twitter.rb:11:in `<class:Twitter>'

Looking at the error, yes that is a bad URI, as it is adding the environment variable name before the actual URI address.

Any idea how to get around this issue?


(Jeff Atwood) #2

This seems like a legit bug, what do you think @sam?


(Sam Saffron) #3

Possibly a bug, @mcardleliam did you ever sort this out