# \[Bug\] Ewon Connector **URL:** \ **Category:** 3rd Party Modules\ **Tags:** ignition81\ **Created:** [October 16, 2024, 6:56pm UTC](https://forum.inductiveautomation.com/t/bug-ewon-connector/97338 "2024-10-16T18:56:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![colin.myburgh](https://avatars.discourse-cdn.com/v4/letter/c/f4b2a3/32.png) [@colin.myburgh](https://forum.inductiveautomation.com/u/colin.myburgh)\ **Post date:** [October 16, 2024, 6:56pm UTC](https://forum.inductiveautomation.com/t/bug-ewon-connector/97338/1 "2024-10-16T18:56:43Z")
Hi all, I saw the following entry in my log file: _A critical error has occurred in the M2Web metadata synchronization thread! THIS IS A BUG -- PLEASE REPORT IT!_ I am using Ignition 8.1 with the Ignition Ewon Connector module, v2.0.1. I have set up the Ewon Connector module as per the module instructions and checked that my Talk2M Account information is correct. I have also checked the Talk2M token and Talk2M developer ID using the DMWeb\_v3.2\_Token Excel spreadsheet (and this works perfectly to read tags from the DataMailbox). I have also created a "logging" user on each of the Ewons that I want to log data from using the same username and password on each, as per the instructions for using the module. I have restarted the Ewon Connector module on Ignition after having made all my changes. I am not seeing any of my Ewon tags being displayed in my designer when I browse the data provider and this is why I checked the log. Here is a screenshot of the error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/4/a428d2678da846fe1591cfac5edea9c58eca01ea.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 16, 2024, 7:47pm UTC](https://forum.inductiveautomation.com/t/bug-ewon-connector/97338/2 "2024-10-16T19:47:45Z")
You need to report this to HMS, I think. This is not our module. > **[GitHub - hms-networks/IgnitionEwonConnector: Synchronize Ewon data to Ignition's Tag Historian](https://github.com/hms-networks/IgnitionEwonConnector)** > > Synchronize Ewon data to Ignition's Tag Historian > **[Home | Ignition Ewon® Connector](https://hms-networks.github.io/IgnitionEwonConnector/)** > > Homepage for the HMS Networks Ignition Ewon® Connector Module. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 16, 2024, 7:57pm UTC](https://forum.inductiveautomation.com/t/bug-ewon-connector/97338/3 "2024-10-16T19:57:50Z")
Also note that Ewon has been dramatically changing their cloud infrastructure recently, including getting rid of free acounts and changing their clouds server DNS names, so HMS probably has a bunch of work to do to keep up. If possible at all. (HMS owns Ewon, so it **should** be possible.) (I stopped using or recommending the Ewon Cosy product due to these changes--mainly because they broke their promise of free single-user access for the life of the product.) Excerpt from an email I received a week ago: > Important migration to new Talk2m VPN Endpoints for Ewon devices and Ecatcher > > This message is to notify you of a planned maintenance for Talk2m, our Ewon Industrial Cloud. Please carefully read this email as this change could potentially impact your ability to remotely access your equipment. > > We are announcing that in the next few months we will migrate our Talk2m VPN infrastructure to new IP endpoints. This will be a staged transition and it’s scheduled to start on October 8th, 2024. > > While this upgrade will enhance performance and security, it also comes with some changes that might impact some devices and Ecatcher usage. > > ⚠ To avoid downtime or issues while remote accessing your devices, please make sure to update your local settings (internet protection software, firewall, proxy) and the remote firewall/proxy rules of your Ewons to whitelist the new IPs. This applies only to certain network environments that use IP filtering rather than the \*.talk2m.com domain whitelisting. During the migration, the old endpoint IPs will be replaced with the new ones, one by one.