Contrib.social

Varnish configured with :port,PROXY

Open on Drupal.org →
Created on 19 November 2024, 30 days ago

Problem/Motivation

Web server set up with hitch on port 443 which then directs to varnish on :6086,PROXY. Back end is nginx. I am having difficulty configuring adv_varnish to talk to varnish because of the ",PROXY".
Got curl error 52 empty response, then hacked guzzle code to add CURLOPT_PROXY and CURLOPT_HTTPPROXYTUNNEL which then gave curl error 56 Proxy CONNECT aborted.
How should I configure Varnish server host in General settings to handle this situation? Currently its 127.0.0.1:6086 If I add ",PROXY" or "--proxy" there are parsing errors and WSOD.

💬 Support request
Status

Active

Version

4.0

Component

User interface

Created by

🇳🇿New Zealand scrypter

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @scrypter
  • Comment 26 days ago →
    🇵🇱Poland shumer Wroclaw

    That's an interesting request, I never had a setup like that so it's hard to provide proper details here (unless someone who used that module with that setup can share knowledge)

    I can only imagine that Drupal can talk to Varnish avoiding the PROXY in case you can tell Varnish to bin the additional port to support that 

    varnishd \
    -a :80 \
    -a :8443,PROXY \ # Existing PROXY-enabled port for Hitch
    -a :6087        # New port for direct connections from adv_varnish
    -f /etc/varnish/default.vcl \
    -s malloc,2g

    You should not need to hack Guzzle then, Drupal should be able to reach Varnish on that port.
    (But that's just my theory)

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024