NimbostratusHi all, I tried to redirect ports 80 and 443 in a VS, this manner:
My VS1 is configured to listening on port 80 and my pool to listening in port 1080 My VS2 is configured to listening on port 443 and my pool to listening in port 1081 The response to client in both cases is: This page can't be displayed
I think the solution is more complex than this simple configuration.
Please Any idea for fix this?
NacreousThe F5 will automatically forward traffic from your VS port to your pool member on what ever port it resides with no additional configuration. The F5 doesnt care what ports they use, it just passes the traffic.
What matters is the right thing is listening on your server. You should have a webserver that does not use SSL listening on port 1080 for the first virtual. You should have a webserver that does use SSL listening on port 1081. This assumes you are not using a clientssl/serverssl profile. Its pretty easy to tell if they are setup correctly by testing from the command line of the F5.
curl http://x.x.x.x:1080
curl -k https://x.x.x.x:1081
NimbostratusThe document has moved here.
In Sync] ~ curl -k http://11.240.64.32:1081 400 Bad Request Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
[jcpena@F2000S-SBD1-00A-CORE-C1U1:Active:In Sync] ~ curl -k https://11.240.64.32:1081 302 Found Found
The document has moved .
CumulonimbusDo you have SNAT configured? If not try enabling SNAT Automap.
NacreousOk that tells us a lot. You may find it easier to post output to places like https://gist.github.org and include a link here.
The first curl responds with a redirect that adds a trailing slash and then uses Try it again with the trailing slash... curl http://11.240.64.32:1080/
The second curl was a typo as you used http:// instead https:// and you are lucky at least it gave you a hint.
The third curl responded with another redirect but doesnt tell you the destination in the message. Try the curl again but this time use the -i option to tell curl to include the HTTP headers.
NimbostratusNacreouscurl -ik ...
NimbostratusThe document has moved .
NacreousFrom those results I think you are correct in saying the serverside confiugration needs to be looked at. The http webserver on port 1080 is redirecting you to a https website which should not be happening for starters.
The https webserver on port 1081 appears to be redirecting you to an error page.
Do these websites have a DNS name? If so try adding -h "Host: dns_name" to the curl request and see if that helps.
curl -ik -h "Host: dns_name" https://....