@jolly-london-20127 @bored-island-21407 If you can help here please. what does the highlighted fatal error mean[ss attached] ? After updating it to v.16.1 unable to access the dashboard. Please help me out to troubleshoot, If I have deviated while installing.

Looks like you have a few things misconfigired. The browser error is due to a lack of cert, is traefik configured correcly? The netmaker error is probably due to not setting the mq password

Please find the attached ss, is there any issue.? Thanks MQ_Admin_Password is same as MAster Key, Can it create a problem

look at your traefik logs

docker logs traefik

error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: dashboard.netmaker.**.kmd.dk, retry after 2022-10-16T00:59:02Z: see https://letsencrypt.org/docs/duplicate-certificate-limit/" ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=netmaker-ui@docker rule="Host(

dashboard.netmaker.****.kmd.dk

)" providerName=http.acme this might be a potential reason for the dashboard issue, I believe. Thanks for letting me know to check trafeik container logs

the fatal broker error looks like it's due to an incorrect address. Make sure it's actually mq:1883 that's opened

I can see that in v0.16.0, mq is running fine while in v0.16.1 it's throwing error. 1883 is opened as I can see in the logs of containers. P.S. bothe the versions are running with different systems having different netmaker base domain Any suggestions, how to fix it? in v0.16.0, I can see for mosquitto.conf, listener 1883 allow_anonymous true

netmaker logs

master node of kubernetes is unable to have interaction and subsequently going in error stage. [Note there is no impact on Worker nodes] This I am trying on the same netmaker where all the above issues are being faced

QA-KUBE-MN-1 is not communicating with the broker try running

netclient pull -n short -vvvv

on that node

I will reconfigure netmaker 0.16.1 from scratch will let you know on further updates. Thanks for your support.

after upgrading to v0.16.1 you need to run

netclient pull

on all your nodes

Will let you know shortly, was occupied with other works.😉

can you send the mq logs?

these are today's logs I see there's no fatal error except [netmaker] 2022-10-20 15:21:12 failed to get node info [6014d904-a197-4239-b77d-0ab2f395f7af]: could not find any records [netmaker] 2022-10-20 15:21:12 processed request error: could not find any records and all the nodes added are installed with latest version of netclient just now I created, installed and added to the network

were these clients already running or you just started them with v0.16.1?

yes

and you joined the network with v016.1 client? or were they already part of the network?

no they were not part of any network, joined with v0.16.1 server and client both

is that your new node id (6014d904-a197-4239-b77d-0ab2f395f7af)?

you mean netmaker-1 node id ?

any of the nodes that you added to network has that id?

no this is not the id earlier when it was configured with v.16.0, that time I have created a network and added a node after that I deleted that server and created a fresh new server with v0.16.1 is it taking anything from previous configuration?

can you just leave from that old network on your nodes

netclient leave -n NETWORK_NAME

so that files related to that will be cleaned up i guess the daemon is picking from that configuration

these nodes are not connected to old network

that's alright doing this

netclient leave -n OLD_NETWORK_NAME

will just cleanup the old files if there are any

done, it says no such file or directory

@cool-army-24422 can you check your DMs from me