Forum Discussion

Sajan_Mania_381's avatar
Sajan_Mania_381
Icon for Altostratus rankAltostratus
Mar 30, 2019

http error 404 - no webpage was found for the web address .

I have a VIP with port 9443 configured with Performance L4 Virtual server type with Fastl4 profile doing SSL passthrough .But I see VIP and pool members are up but I am getting http error 404 .

 

Can someone tell what could be the issue ? Is this indicating there is an issue with Backend server or do I need to check anything on the VIP config ?

 

 

7 Replies

  • You can verify whether the services are enabled on the servers on 9443 by trying to access them individually ? And when you enable the pool and the VIP, make sure you have port https on 9443.You can also try to enable the http profile if you have not done already.

     

  • 1.Service are listening on backend server 2.for SSL passthrough can we enable http profile ? Will it not give certificate error ? 3.make sure you have port https on 9443 - How ?

     

  • Newer OS versions support http profile on Fast Layer 4 virtual server types. There is much complex way it works but worth trying. It may/may not give an error. When you define the pool, which port is selected ? If you dig into error 404, you would get to know that the services are not available,so need to be sure that the service is available, by trying to access the same on individual server

     

  • Newer OS versions support http profile on Fast Layer 4 virtual server types. There is much complex way it works but worth trying - When I am not placing my certificate on F5 is it recommended to use http profile ?

     

  • It's more likely to be an issue with your server side config itself. However, as said previously, you can enable http profile even in this case. Are you able to access the services hosted on the server by accessing them individually and not going through F5 ?

     

  • "When I am not placing my certificate on F5 is it recommended to use http profile ?"

     

    No, you should not use the HTTP profile if you aren't decrypting the traffic on the F5, e.g. you are doing SSL pass through.

     

    In an SSL pass through scenario, it is the server, not the BIG-IP returning the 404 response you are seeing. It seems likely that your F5 configuration is functioning correctly, but your content servers aren't configured correctly or don't have a webroot document.