Consul RPC errors with no ports issues

Hi!

I managed to reach all of the servers using:
**"retry_join": ["provider=aws tag_key=Name tag_value=mytag"],**
But now, even when the host is reporting in consul UI I can see that the node does not take my service checks or service at all but instead:

    **2020-07-21T05:06:43.203Z [ERROR] agent: Coordinate update error: error="rpc error ****making call: EOF"**
**    2020-07-21T05:06:43.816Z [ERROR] agent.client: RPC failed to server: **method=Catalog.NodeServiceList server=MyIP1:8300 error="rpc error making call: EOF"**
**    2020-07-21T05:06:43.817Z [ERROR] agent.anti_entropy: failed to sync remote state: **error="rpc error making call: EOF"**
**    2020-07-21T05:07:01.537Z [ERROR] agent.client: RPC failed to server: **method=Coordinate.Update server=MyIP2:8300 error="rpc error making call: EOF"**
**    2020-07-21T05:07:01.537Z [ERROR] agent: Coordinate update error: error="rpc error making call: EOF"****

For all my nodes. All the required ports are reachable via nginx:

Stream {
    # ...
    server {
        listen     8300;
        proxy_pass 127.0.0.1:30300;
    }
    server {
        listen     8301;
        proxy_pass 127.0.0.1:30301;
    }
    server {
        listen     8302;
        proxy_pass 127.0.0.1:30302;
    }
    server {
        listen     8600;
        proxy_pass 127.0.0.1:30600;
    }
}

Am I missing a port? I am exposing the service via node port and not using the UI directly but via kubectl port-forward.

I was not able to use the auto-join for K8s for some reason :frowning:

I am not using ACL’s yet, so I have no clue on what is going on or what do they mean.

Ok figured out I was missing the certs in my config. Now no more errors like those ones.

1 Like

Thanks @ARSport for posting, and welcome to the forums.

What were the options you added to your config to get it working?

I was trying to use auto encrypt and eventually made it work with:
“ca_file”: “/consul/tls/ca/tls.crt”,
“auto_encrypt”: {
“tls”: true
]

1 Like