Forum Discussion
NimbostratusUnable to launch the Visual Policy Editor (VPE)
Hello,
I've recently upgraded my F5 from 11.3.0HF2 to 11.4.1HF4. Since then, I can't use the Visual Policy Editor (VPE) as everytime I click on the link to edit the access policy, the F5 prompts the following message :
You are currently logged out of the system.
Please re-logon from the Main Window to continue your operation
I've checked, and the auth cookies are well transmited during the request. I seems the be related to the Firefox version I'm using :
- FF 3.6.3 OK
- FF 29.0.1 NOK
- FF 30.0.0 NOK
- Opera 12.17 OK
Rolling back to the version 11.3 solves the issue. I've also tryied with the version 11.5.1HF2, and the problem is the same.
Does anyone have faced this problem or maybe have a solution (rather than using an older version of FF or another browser) ?
Thanks in advance.
7 Replies
Kevin_Davies_40Nacreous
Have you disabled cookies in the privacy/security setting of your browser?
J__Pogeant_1557Hello,
As said, I've checked the HTTP request, and all the cookies are sent (at least the same used to browse any other working page on the web interface).
I can login on the web interface and browse into without problem. The problem only occurs when I click on the link to launch the VPE.
- Kevin_Davies_40
Oh sorry I missed that bit about auth cookies. Is there anything between you and the F5. A proxy perhaps? Can you bypass that proxy?
- J__Pogeant_1557
I have a direct access between me and the F5.
I really think it's software related (FF or F5, or both), specially with the different behaviour depending of the browser version I'm using :)
- Kevin_Davies_40
It could well be. I use chrome personally, its the fastest F5 GUI by a country mile.
- J__Pogeant_1557
OK nevermind, this was a cache related issue.
By cleaning it, the problem doesn't happen. I guess my browser kept an old version of a JS...
Algebraic_MirrorCirrostratus
I just had the same problem, also with Firefox (v 36.0.1). Cache clearing fixed mine as well. The thought of cache clearing hadn't occurred to me yet, so thank your for your post! You saved me some time and helped me move forward.
I'd be curious to know what causes Firefox to get into this state in the first place. I've never seen this with Chrome or IE.
