Hi All, (Note that I have deliberately broken all domain names by inserting whitespace because they are getting detected as links, and as a noob I cannot post >2 links in a post) I am trying to install discourse on a redhat VM at my work. I have the following constraints: Host has no direct acc…

That does sound grueling. It looks like someone managed to do it ; perhaps their notes (with a problem you’ll have down the road) will help.

Looks like gem does not respect the https proxy env var. I can see here that the proxy needs to be passed as a switch on the gem command or set in .gemrc: Depending on your gem version, one of these should work: gem install --http-proxy http://[user]:[password]@[server]:[port] gem install -p ht…

Hi Jay Thanks for the pointer. I’ve been searching around on here. but most mentions of proxy are regarding configuring a working discourse to be behind a reverse proxy, The page you linked conformed my hypothesis regarding gem not respecting env var for proxy. Unfortunately this is for a working…

This is possible, you need: Export http and https ENV variables in your current shell Add the same variables to the env block inside the containers/app.yml file Add the same variables to the docker system.d service config file (read system.d docs on this, you will need to create a new servi…

Looking good. Added HTTP_PROXY and HTTPS_PROXY env variables and its going well so far…

Traditionally, the environment variable names for proxies are lower case. Perhaps -e https_proxy=<...> might have worked?

Good point. Seems that the upperCASE env vars work sometimes. I noticed that nginx log had errors connecting to avatars.discourse.org , and pretty sure its due to only having HTTP_PROXY I changed to lowercase. Thanks!

So did the install work for you?

Difficult to say right now. The install completes :+1: I cannot access the web UI :-1: Trying to debug atm. Portainer running on the same docker works fine (port 9000), but neither 80 or 443 is responding for discourse. Errors in logs: nginx log I am seeing this every second: 2017/07/19 14:2…

Install discourse with internet access only via proxy

Product Support Self-hosting

jimbob (James) 18. Juli 2017 um 20:04 6

Thanks!
Just need to do the middle bullet.
I already updated the docker system.d

Thema		Antworten	Aufrufe
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	27	1242	12. März 2024
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4264	20. September 2022
I want to install using a reverse proxy for Apache Self-hosting	13	4855	8. August 2021
Error while trying to install Discourse Self-hosting	7	1851	26. Dezember 2017
Unable to access after installation - HTTP Self-hosting	18	4365	10. Mai 2017

Install discourse with internet access only via proxy

Verwandte Themen