Re: About Using ProxyPass Directive (Apache Users)

I still get these warnings when I try run Apache:

[Tue Jan 15 19:38:22.300249 2019] [env:warn] [pid 12988:tid 556] AH01506: PassEnv variable <apikey> was undefined
[Tue Jan 15 19:38:22.301248 2019] [env:warn] [pid 12988:tid 556] AH01506: PassEnv variable <accesskey> was undefined

How do I set the PassEnv value correctly? Right now it's like this:

PassEnv apikey "<apikey_value>"
PassEnv accesskey "<accesskey_value>"
"

Is that wrong? Note: I'm not putting the actual API keys here. They're just placeholders.

By the way, it's good to put the ServerName in httpd.conf as something other than the actual name of the server app I want to put behind the reverse proxy, right? Or would it be better to give it the same name as the actual app?

From: Jonathon Koyle <litereader@xxxxxxxxx>
Sent: Tuesday, January 15, 2019 6:47 PM
To: users@xxxxxxxxxxxxxxxx
Subject: Re: About Using ProxyPass Directive

By default, the httpd.conf has the directive Listen 80. If you don't want Apache to listen on 80 you will need to remove/change it. You are allowed to have as many listen directives as you want Apache to bind. ServerName does not usually include a port, and does not specify what IP or port Apache binds to.

On Tue, Jan 15, 2019, 06:28 Osman Zakir <osmanzakir90@xxxxxxxxxxx wrote:

@Eric Covener I got the port forwarding to work and am now able to get my app using my external IP address on port 8443 (but it's not using SSL right now). I still need to actually get Apache to start before I put my app behind the reverse proxy, and port 80 is being used by the system. I tried to change the "ServerName" value to 0.0.0.0:8080, but it's still trying to connect on 0.0.0.0:80 which is giving an about it not being able to bind to any listening ports. I'll see if I can find another setting in the httpd.conf file to use in the meantime, but for now I'll also ask this: what do you suggest I do?