Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 14836 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM Reverse Proxy still tries to connects to an old AWS ELB IP

LGSommers

Situation is UTM is on AWS. Using WAF where in real ws is pointing to Amazon ELB.

Virtual WebServer shows up an error from time to time.

Noticed that it's happening whenever Amazon changes their IP address but not sure why would it matter because UTM Real WebServer is pointing to a DNS Host of the ELB.

Only way to resolved it was to disable and enable the real webserver. 

ReverseProxy.log

Still tries to connect to x.x.x.100, that ip doesnt exist anymore

2015:11:13-21:20:43 ort_utm2 reverseproxy: [Fri Nov 13 21:20:43.113375 2015] [proxy:error] [pid 17116:tid 3971750768] (110)Connection timed out: AH00957: HTTPS: attempt to connect to x.x.x.100:443 (xxxxx.us-west-2.elb.amazonaws.com) failed

ELB IP address is now x.x.x.25.

Any thoughts?

Thanks in advance!



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to PeterGordon

    Hi,

    we only support ELB correctly since 9.405.

    Therefore, you create a DNS Group like the KBA proposed and you use this DNS Group as host object in your real webserver.
    In the real webserver edit form you also have to select 'Disable backend connection pooling' under Advanced.

    You can use this ELB real webserver as any other webserver in the virtual webserver form (no other special options needed).

    Best,
    Sabine

    Edit: because I have no idea if you need a Firewall rule for the return packets.

  • 0 in reply to Evianne

    The proposed fix and firmware update does not work.

    1. Updated firmware to 9405-5.
    2. Created new internal AWS ELB.
    3. Created new DNS Group using new internal ELB FQDN.
    4. Confirmed site working and no errors in Sophos WAF.
    5. AWS ELB had a scale down event.
    6. Site broke just like before with same errors.

Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?