[NMS] Unable to communicate with magma controller: Not Found #5724
-
NMS has been working without issues and suddenly today I got the following screen with error: "Unable to communicate with magma controller: Not Found" I checked the pods and all have been running with
Last issue I had was getting forbidden when trying to into NMS and it got solved by restarting nms-nginx-proxy by running I was wondering if I should restart other or all the services or if the issue might be related to something else. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
As you mentioned everything looks alright. I suspect it is something to do with the admin cert on the NMS. Can you check if it expired and if you have to renew it. |
Beta Was this translation helpful? Give feedback.
-
@BioZrod This is the process to replace existing admin certs. cc @sudhikan @wallyrb Scenario - NMS is unable to communicate with the controller or API access is no longer functional; it used to be now it’s not. Cause - The certificate used for the TLS handshake has expired. Resolution - New admin_operator certificates need to be generated and uploaded to the NMS k8s pod for NMS access and to the browser for the API access. How to generate new admin_operator certificates:
The following commands are to be run inside the pod
NOTE: Make sure the location where these certificates are being copied to is the same location which is referenced in the main.tf file for the seed_certs_dir variable.
NOTE: terraform apply command outputs the “plan” of what it intends to add,destroy,modify. Please scrutinize this output before typing “yes” on the confirm prompt. If there are any changes that are not consistent with your expectations, please cancel the run. You can specifically target the secrets portion by doing terraform apply -target=module.
|
Beta Was this translation helpful? Give feedback.
@BioZrod This is the process to replace existing admin certs. cc @sudhikan @wallyrb
Scenario - NMS is unable to communicate with the controller or API access is no longer functional; it used to be now it’s not.
Cause - The certificate used for the TLS handshake has expired.
Resolution - New admin_operator certificates need to be generated and uploaded to the NMS k8s pod for NMS access and to the browser for the API access.
How to generate new admin_operator certificates: