# CM 10 - The hostname could not be parsed **URL:** \ **Category:** Deployment\ **Tags:** v10.2, installation\ **Created:** [August 27, 2025, 7:16am UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543 "2025-08-27T07:16:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ana\_Silva](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@Ana\_Silva](https://community.criticalmanufacturing.com/u/Ana_Silva)\ **Post date:** [August 27, 2025, 7:16am UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543/1 "2025-08-27T07:16:09Z")
I have this error after an upgrade from 8 to v10.2.9 and there’s this error “The hostname could not be parsed”, does anyone know why? MES is working and I use the same .json configuration from V8 so I really don’t know where’s could be the problem, any ideas? ---
**Author:** ![Joao\_Moreira](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@Joao\_Moreira](https://community.criticalmanufacturing.com/u/Joao_Moreira)\ **Post date:** [September 1, 2025, 9:24pm UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543/2 "2025-09-01T21:24:38Z")
Hi Ana, Its common for configuration files to have changes between versions. It’s a good practice to always upgrade your environment first and then either adapt the new configuration files or compare the old and new versions to identify what’s changed. To be able to help, could you please provide some more information about your environment and the issue you’re facing? - ## What version of MES are you running (e.g., v10.2.9)? ## Are you still running the host on Windows? When is this issue occurring? Is it happening all the time, on specific pages, or during specific service calls? If you can, please use your browser’s developer tools to identify the REST service that’s being called when the issue occurs. Also, check if the REST call is being executed with the retry parameter enabled. The **RestOperationInvoker** is a CM MVC pipeline task that handles retries. Best regards, João Moreira ---
**Author:** ![mike\_brunner](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@mike\_brunner](https://community.criticalmanufacturing.com/u/mike_brunner)\ **Post date:** [January 31, 2026, 12:20am UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543/3 "2026-01-31T00:20:29Z")
I have this same problem on 10.2.13. It appears to be related to the chat bot. I can’t access Joao’s linked ticket with the resolution. Can you post it here? ---
**Author:** ![Ana\_Silva](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@Ana\_Silva](https://community.criticalmanufacturing.com/u/Ana_Silva)\ **Post date:** [February 2, 2026, 8:38am UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543/4 "2026-02-02T08:38:46Z")
Hello Mike,Bug description : After upgrading from 8.3.6 to 10.2.9 in the productive environment using the standard JSON configuration (EnvironmentConfig.json) the client detected that the login screen does not load correctly. After Refreshing the page the MES load correctly. This is especially critical for all the TV screen that show the production Dashboards. On the Host has this error To solve the problem, was this part: [Authentication Portal](https://developer.criticalmanufacturing.com/explore/guides/migration/version-specific/1020/ui_service_worker/) ---
**Author:** ![mike\_brunner](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@mike\_brunner](https://community.criticalmanufacturing.com/u/mike_brunner)\ **Post date:** [February 5, 2026, 2:23am UTC](https://community.criticalmanufacturing.com/t/cm-10-the-hostname-could-not-be-parsed/543/5 "2026-02-05T02:23:09Z")
Thanks for replying. The only change I needed to make was the last one, removing index.html in ngsw-config.json. I restarted my UI and am still seeing the error.