docs(website-new): add docs on resolving @mf-types generation behind local proxy (#3765)

Author: YanPes

apps/website-new/docs/en/guide/troubleshooting/type/overview.md

@@ -41,4 +41,21 @@ The type generated by the producer contains aliases and cannot be processed norm
 ```
 
 3. Set [dts.generateTypes.compilerInstance](../../../configure/dts#compilerinstance) to `tspc`(`ts-patch` cli) 
-4. Regenerate types
+4. Regenerate types
+
+### Generated types not updating when working behind a local proxy
+
+**Phenomenon description**
+
+The types generated by the producer are successfully generated, the consumer log shows that the types are successfully processed, but the `@mf-types` directory does not update.
+The issue can be a proxy configuration problem not allowing the resource to be downloaded.
+
+**How ​​to solve**
+1. Check if the `@mf-types` directory is generated in the `dist` directory of the producer.
+2. Check your proxy log for any errors related to `TLS` or `SSL`.
+3. Adapt your proxy configuration to add `TLS` certification for your local environment.
+4. In some scenarios this is not working. An alternative is, to define the environment variable `NODE_TLS_REJECT_UNAUTHORIZED=0` to ignore the `TLS` or `SSL` errors. This will allow the `@mf-types.zip` to be properly handled.
+
+:::danger Important note
+Only set NODE_TLS_REJECT_UNAUTHORIZED=0 in your local development environment. It is not meant for production use. If you go this route, please make sure to commit the generated types to your repository.
+:::