A site cannot reconnect to NxCloud [resolved]
Completed
Hello Wendy Chuang
We have again a NxCloud problem
A site that you got access (about my ticket #35140 - Brion) cannot be reconnected to NxCloud (customer call me that his system is seen "offline" on NxCloud)
I can get a remote access and make a soft-reset for the server but I still get offline on NxCloud
Under ubuntu and Nx 5.1.0.37133
Because I cannot get files from my remote NxWitness : I get this logs on monitoring logs.
2023-10-07 21:23:24.084 2823 WARNING QMessageLogContext(0x7fdf9804ff08): Bad SEI detected. SEI too short
2023-10-07 21:24:42.303 694 WARNING nx::vms::cloud_integration::CdbNonceFetcher(0x7fdfe8117170): Failed to fetch nonce from cdb: notAuthorized
2023-10-07 21:25:51.534 2823 WARNING QMessageLogContext(0x7fdf98b0de38): Bad SEI detected. SEI too short
2023-10-07 21:26:02.315 694 WARNING nx::vms::cloud_integration::CdbNonceFetcher(0x7fdfe8117170): Failed to fetch nonce from cdb: notAuthorized
2023-10-07 21:26:28.646 2823 WARNING QMessageLogContext(0x7fdf98b0de38): Bad SEI detected. SEI too short
2023-10-07 21:26:32.673 2823 WARNING QMessageLogContext(0x7fdf98745648): Bad SEI detected. SEI too short
2023-10-07 21:27:22.329 694 WARNING nx::vms::cloud_integration::CdbNonceFetcher(0x7fdfe8117170): Failed to fetch nonce from cdb: notAuthorized
2023-10-07 21:27:30.836 2823 WARNING QMessageLogContext(0x7fdf983c9188): Bad SEI detected. SEI too short
2023-10-07 21:27:33.844 2823 WARNING QMessageLogContext(0x7fdf983c9188): Bad SEI detected. SEI too short
-
Loïc TONON : le support Nx n'a pas l'air de réagir et le client ne comprend pas pourquoi du jour au lendemain, il ne peut plus se connecter à son site ...
-
Hello Julien
Have you tried this fix :
Go to : DST Root CA X3 Expiration
?
-
I'm under ubuntu, I've done procedure for self signed certificates
but i don't see how to do procedure about root CA X3 expiration for ubuntu
-
Wendy Chuang : any idea ????
-
Hi,
After use a local nxwitness, Nxwitness cannot access to internet because of no dns from router. I don't understand why, because Teamviewer which is very sensitive to dns problem works fine.
Customer hard reboot the 4G router and the connection has been reactivated and operationnal.
Post is closed for comments.
Comments
5 comments