Skip to main content
DirkDuesentrieb
New Member
September 7, 2022
Question

Workaround: explicit proxy reports "504 Gateway Timeout" after updating to v6.2.11

  • September 7, 2022
  • 2 replies
  • 4553 views

Hi,

after updating to v6.2.11 some connections via the explicit proxy failed, the error was "504 Gateway Timeout".

In my case the explicit proxy used a different source IP for connections over a VPN. This failed because the new source IP was not part of the VPN-topology. 

 

The workaround was to change all proxy policy rules that use the VPN as outgoing interface and set "Outgoing source IP" to "Original Source IP".

 

Hope it might help someone!

 

Greetings,

 

Dirk

2 replies

Rathan_FTNT
Staff
Staff
September 7, 2022

Hello Dirk,

Seems like this is matching the known issue 733863 from 
https://docs.fortinet.com/document/fortigate/6.4.6/fortios-release-notes/236526/known-issues

It is fixed in 7.0.2
regards,

Rathan



DirkDuesentrieb
New Member
September 7, 2022

Hi @Rathan_FTNT 

 

no, the different handling of the outgoing IP must be a new feature/bug in v6.2.11. We updated from v6.2.10 where everything was fine.

 

Regards,

Dirk

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!