You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not able to connect to any SF cluster using sfctl on macOS 11.4. Googling around i see mentions of sfctl attempting to negotiate TLS 1.0 instead of 1.2, however i can't find a parameter that would allow me to amend the protocol version for the handshake.
Cluster version: 8.0.514.9590 (managed SF cluster)
Cluster version: 8.0.521.9590 (unmanaged SF cluster)
^ These are two independent clusters, with independent pub/priv key pairs as client certs, the right FQDN in the subject and their SHA-1 thumbprint added via the Azure Portal to the cluster.
$ pip show sfctl
Name: sfctl
Version: 11.1.0
Summary: Azure Service Fabric command line
Location: /usr/local/lib/python3.8/site-packages
Using sslscan against the cluster endpoint shows 19000/TCP does not speak TLS at all.
So my question becomes, which port should i connect to?
I've also tried 19080 and that gives me:
Starting new HTTPS connection (1): sfunmanaged.norwayeast.cloudapp.azure.com:19080
/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:842: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
warnings.warn((
urllib3.connectionpool : https://sfunmanaged.norwayeast.cloudapp.azure.com:19080 "GET / HTTP/1.1" 403 0
403 Client Error: Client certificate required for url: https://sfunmanaged.norwayeast.cloudapp.azure.com:19080/
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/knack/cli.py", line 206, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/local/lib/python3.8/site-packages/sfctl/entry.py", line 81, in execute
return super(SFInvoker, self).execute(args)
File "/usr/local/lib/python3.8/site-packages/knack/invocation.py", line 208, in execute
cmd_result = parsed_args.func(params)
File "/usr/local/lib/python3.8/site-packages/knack/commands.py", line 139, in __call__
return self.handler(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/knack/commands.py", line 246, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "/usr/local/lib/python3.8/site-packages/sfctl/custom_cluster.py", line 162, in select
rest_client.send(rest_client.get('/')).raise_for_status()
File "/usr/local/lib/python3.8/site-packages/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Client certificate required for url: https://sfunmanaged.norwayeast.cloudapp.azure.com:19080/
even if i pass --key and --cert to the CLI (or --pem with a pub+priv .pem bundle)
I'm confused, is that a bogus error or is there something wrong with my key material?
The text was updated successfully, but these errors were encountered:
snobu
changed the title
[sfctl] TLS error: Unexpected EOF when connecting to cluster
[sfctl] TLS error: bad handshake, Unexpected EOF when connecting to cluster
Jun 29, 2021
snobu
changed the title
[sfctl] TLS error: bad handshake, Unexpected EOF when connecting to cluster
[sfctl] TLS error: 'bad handshake: Unexpected EOF' when connecting to cluster
Jun 29, 2021
Hello, @snobu SFCTL is meant for connecting to the HTTP port of the cluster which is usually 19080 and as far as the key and cert params. those are meant to be file locations for where the key and pem file would be located.
I am not able to connect to any SF cluster using sfctl on macOS 11.4. Googling around i see mentions of sfctl attempting to negotiate TLS 1.0 instead of 1.2, however i can't find a parameter that would allow me to amend the protocol version for the handshake.
Cluster version: 8.0.514.9590 (managed SF cluster)
Cluster version: 8.0.521.9590 (unmanaged SF cluster)
^ These are two independent clusters, with independent pub/priv key pairs as client certs, the right FQDN in the subject and their SHA-1 thumbprint added via the Azure Portal to the cluster.
Using sslscan against the cluster endpoint shows 19000/TCP does not speak TLS at all.
So my question becomes, which port should i connect to?
I've also tried 19080 and that gives me:
even if i pass --key and --cert to the CLI (or --pem with a pub+priv .pem bundle)
I'm confused, is that a bogus error or is there something wrong with my key material?
The text was updated successfully, but these errors were encountered: