- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fortiweb not forwarding to single back end server.
Solved! Go to Solution.
- Labels:
-
FortiWeb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue us resolved, thanks for your time, default Mgmt port is 8080, the same port used for Proxy listening! i changed this in settings to 8081 to free up 8080 to be used as the HTTP listener, the back end wasnt recieving traffic, as it was MGMT traffic! bit daft why it would use 8080 as the default HTTP for manangement!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Enable traffic logs on the policy and redo the test. Then share what you see on both traffic log and attack log.
Created on ‎02-11-2024 08:12 AM Edited on ‎02-11-2024 08:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fairly new to these. where is the logging for the policy? If I goto Policy > Server Policy and edit my policy, there is no option to enable traffic logs? EDIT : FOUND THE SETTING, looking at X-FORWARDED FOR setting too, these seem important?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All of this is enabled, I don't see anything at all in the traffic log, which is kind of impossible!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which FWB version are you using? I'd first fix the log issue otherwise troubleshooting will be almost impossible.
What do you see on the client's browser when you try?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fortiweb-VM 7.22, Build 0344
Client sees "timeout - xxxxxx taking too long to respond"
Traffic Log is Enabled.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Then I'd start by updating to 7.2.7 which is the most stable of 7.2 versions. I've already seen log related issues (and other issues) in low patch versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We get the GET request on port 8080 on the VIP, then the next line on the capture is: status code 302, http 1.1 302 found (text/html)
it never send it to the back end.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
302 = redirection.
It seems there is a redirection from your back end web server to another URL.
