Im back here just searching around to see what the latest news on this reverse proxy issue is, I've had these same issues with any new version I try after 6.0.2.10 almost to a T. I'm behind an Apache reverse proxy. If i restart service might work for an hour. If I whitelist the Apache server it still happens. I think I have checked and unchecked everything anywhere in the new settings. I've tried just about every release of BI and they all have done it post 6.0.2.10 in my case 6.0.2.10 always lets it work. It has to be something in the ban user agents settings, although it even happens when its blank. Its the only thing that is different about these "settings" version to version that is obvious.
The latest I have confirmed to still have, at least my issue, is 6.0.6.9 and today 6.0.7.0 is out and im not even going to bother. 6.0.2.10 is working. I've seen others have success post 6.0.2.x., but in my scenario new versions of BI dont like a simple Apache reverse proxy for some reason. I did explicitly add the following into my virtual host file, but it should be passing by default.
Code:RequestHeader set X-Real-IP %{REMOTE_ADDR}s RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
Im not sure. Waiting, ill keep trying.
I had the same problem like everyone else. My reverse proxy worked before updating from BI5, but stopped when I updated to BI6.
Thanks to your post, I reverted to 6.0.2.10 and now I can access my BI instance from my phone using the reverse proxy
It's a shame that the "improved" the security and caused this issue.
If you ever find a workaround on the more recent versions, please let us know!
Thanks a lot for pointing out the last "good" version.
Hope you have a nice day!
