# Ziti identity file not registering although it says it did **URL:** \ **Category:** Uncategorized\ **Created:** [January 22, 2025, 2:33pm UTC](https://openziti.discourse.group/t/ziti-identity-file-not-registering-although-it-says-it-did/3816 "2025-01-22T14:33:52Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![nyck33](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/nyck33/32/1466_2.png) [@nyck33](https://openziti.discourse.group/u/nyck33)\ **Post date:** [January 22, 2025, 3:05pm UTC](https://openziti.discourse.group/t/ziti-identity-file-not-registering-although-it-says-it-did/3816/5 "2025-01-22T15:05:43Z")
with the `node-server` identity in place of `node-server-hcmc` on my other computer, at least I could kind of get on the overlay although it was having issues. > [@How to implement OpenZiti for Next.js app](https://openziti.discourse.group/t/how-to-implement-openziti-for-next-js-app/3761/7): > > @curt also these kinds of errors: TypeError: parser.onIncoming is not a function at HTTPParser.parserOnHeadersComplete (node:\_http\_common:117:17) This error is coming from the Ziti SDK's HTTP parser integration with Node.js. The specific error: This suggests there's an incompatibility between how the Ziti SDK is handling HTTP requests and how Node.js expects them to be handled. The error occurs in the socket handling layer when Ziti tries to process incoming HTTP requests....is what Curso… --- _[View the full topic](https://openziti.discourse.group/t/ziti-identity-file-not-registering-although-it-says-it-did/3816)._