# EProto errors in meshed services

**URL:** <https://linkerd.buoyant.io/t/eproto-errors-in-meshed-services/160>\
**Category:** Linkerd General Discussion\
**Tags:** configuration\
**Created:** [June 15, 2023, 11:49pm UTC](https://linkerd.buoyant.io/t/eproto-errors-in-meshed-services/160 "2023-06-15T23:49:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rogerjiang](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@rogerjiang](https://linkerd.buoyant.io/u/rogerjiang)\
**Post date:** [June 15, 2023, 11:49pm UTC](https://linkerd.buoyant.io/t/eproto-errors-in-meshed-services/160/1 "2023-06-15T23:49:07Z")

</div>

I am fairly new to Linkerd and trying to mesh two of my services together. Both server and client are meshed with simply addition of `linkerd.io/inject: "enabled"`. The server configuration is as following

```auto
apiVersion: v1
kind: Service
metadata:
  annotations:
    cloud.google.com/app-protocols: '{"http": "HTTP", "grpc":"HTTP2"}'
  creationTimestamp: "2022-04-22T17:10:50Z"
  name: svc-myserver
  namespace: default
  resourceVersion: "174877786"
  uid: 3468a38c-0b0d-4de1-bb63-963e6544f100
spec:
  clusterIP: 172.20.139.61
  clusterIPs:
  - 172.20.139.61
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: https
    port: 443
    protocol: TCP
    targetPort: 8080
  - name: grpc
    port: 50053
    protocol: TCP
    targetPort: 8081
  selector:
    app: myserver
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

```

and the deployment has

```auto
ports:
        - containerPort: 8080
          name: http
          protocol: TCP
        - containerPort: 8081
          name: grpc
          protocol: TCP

```

The server is serving http at port 8080. However, when I tried to hit the server from my client with openssl, I am getting a EProto error as if the server is not servicing https.

````auto
echo | openssl s_client -tls1_3 -connect svc-myserver.default.svc.cluster.local:443 -ciphersuites TLS_CHACHA20_POLY1305_SHA256
CONNECTED(00000003)
139694947120448:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 255 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
----
```.
I have verified that neither `linkerd-init` and `linkerd-debug` containers are generating errors. Any directions where to go next?
````

---

<div class="post-metadata">

**Author:** ![Alex](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/alex/32/63_2.png) [@Alex](https://linkerd.buoyant.io/u/Alex)\
**Post date:** [June 26, 2023, 7:08pm UTC](https://linkerd.buoyant.io/t/eproto-errors-in-meshed-services/160/2 "2023-06-26T19:08:16Z")

</div>

I’m not sure exactly what’s going on with the openssl handshake here, but can you confirm that you’re able to send traffic between the client and server successfully? Other ways to check that the connection is encrypted include using the `linkerd edges` command (which lists the encryption status of each edge) or attempting to read data off the connection directly with a packet capture.