Forum Discussion
Allanwynn_16283
Nimbostratus
Oct 13, 2015sharepoint running on port 443 - error 404 not found
Hi,
We are implementing sharepoint setup using f5 ltm.
servers:
spws1.company.com
spws2.company.com
are running using https or 443
when i configured it with f5 running on port 443...
Ryannnnnnnnn
Altocumulus
Oct 14, 2015so from your BIG-IP have you curl'd like so (obviously substituting names and IP's)
curl -v -H "Host: sharepoint.company.com" https://1.1.1.10
What was the output?
- Allanwynn_16283Nov 13, 2015
Nimbostratus
Hi Sorry for the very late reply [root@mkti-f5-lb1:Active:In Sync] config curl -v -H "Host: spws1.pgpc.net" https://172.16.2.190 * About to connect() to 172.16.2.190 port 443 (0) * Trying 172.16.2.190... connected * Connected to 172.16.2.190 (172.16.2.190) port 443 (0) * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS alert, Server hello (2): * SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed * Closing connection 0 curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. - Allanwynn_16283Nov 13, 2015
Nimbostratus
BTW, the first output is form F5 to the Server, This from F5 to the virtual server itself [root@mkti-f5-lb1:Active:In Sync] config curl -v -H "Host: sp.pgpc.net" https://172.16.2.127 * About to connect() to 172.16.2.127 port 443 (0) * Trying 172.16.2.127... connected * Connected to 172.16.2.127 (172.16.2.127) port 443 (0) * successfully set certificate verify locations: * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS alert, Server hello (2): * SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed * Closing connection 0 curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
