Forum Discussion
rajeev_81179
Nimbostratus
NimbostratusForbidden : Apache server 192.168.X.X port 443
We just upgraded F5 in our DC, from 5100 to 6900 (ver 9.x) and It was working fine when I had the 5100 and i was able to use it the IE. I am able to telnet access the unit but i am trying to use the GUI and get the error:
Forbidden
You dont have permission to access on this server.
Aditionally, a 403 forbidden error was encountered while trying to use an error document to handle request.
-------------------------------
Apache server at 192.168.x.x port 443
Wondering i need to make any chages on the f5, or start any service on F5 so that it can be views on IE for GUI...thanks
Also I am able to access backup f5, but it does not display any images liek as thought java is disabled(although its not, have checked it)
4 Replies
hoolioCirrostratus
Hi,
I'd guess there is an access control list configured on the admin GUI. You can check SOL7448 for details on where this is configured:
SOL7448: Restricting access to the Configuration utility by source IP address
https://support.f5.com/kb/en-us/solutions/public/7000/400/sol7448.html
Aaron- rajeev_81179Aaron,
Thank you very much for your reply, you are spot on, but i googled the error and then kind of got an idea about it and then looked at the standby unit and realised it was something to do with permissions. However thank you very much for your answer - rajeev_81179Aaron,
with the same upgrade, when I have snmp issues also. When i run the snmpwalk -c ASP -v2c 1.1.1.1 on the active device it says no response from host, but when I run the same command on the standby unit, it works fine and SNMP is working on the standby unit. I am able to ping both the devices.
I restarted the SNMPD service and checked config/snmpd.conf file and compared both the files and the settings seem to be fine, infact I sync the box(active) from peer(standby) and still have the same issue.
Any help is much appreciated.... 
Ben_Chase_15007We ran into a similar issue when going from 9.1.3 to 9.3.1 to 9.4.8 when it was released. We had never messed with the httpd permission settings, so I'm not sure why this happened, but the fix that support gave me was to issue 'b httpd allow all' and that fixed the issue (assuming you actually don't want ACLs on your web gui).
