Problem – IEM Virtual Installation and Configuration : regsecgen-init Job Remains Active, No Further Progress

0
  Hello!   I'm encountering an issue during the registration of Industrial Edge Manager Virtual. I can go through all the steps without any problems (Network & Proxy, Credentials, System Settings, etc.) until the moment I click "Submit" after copying the recovery key. The setup process proceeds normally until the following log lines appear — and then nothing else happens, even after waiting several hours:   time="2025-04-10T12:34:47Z" level=info msg="serviceaccounts \"regsecgen-hook-serviceaccount\" not found" time="2025-04-10T12:34:47Z" level=info msg="creating 1 resource(s)" time="2025-04-10T12:34:47Z" level=info msg="creating 1 resource(s)" time="2025-04-10T12:34:47Z" level=info msg="Watching for changes to Job regsecgen-init with timeout of 0s" time="2025-04-10T12:34:47Z" level=info msg="Add/Modify event for regsecgen-init: ADDED" time="2025-04-10T12:34:47Z" level=info msg="regsecgen-init: Jobs active: 0, jobs failed: 0, jobs succeeded: 0" time="2025-04-10T12:34:47Z" level=info msg="Add/Modify event for regsecgen-init: MODIFIED" time="2025-04-10T12:34:47Z" level=info msg="regsecgen-init: Jobs active: 1, jobs failed: 0, jobs succeeded: 0"   I'm on a corporate network that includes a proxy. On an open network without security policies, everything works fine. However, on the corporate network, all communication with Siemens is supposedly working properly — the "System Info" and "Connectivity Check" tabs both show "Connected" everywhere.   I’ve also checked the logs and didn’t notice any differences compared to a successful registration — everything looks the same up to this exact point.   Is this a known issue, or is there any solution or workaround?   Thanks in advance!
asked
2 answers
0

Hello Pierrick,  since you mentioned your IEMV is running within a environment behind a proxy server, did you also add the proxy server during the onboarding of the IEM Virtual?

 

In addition, just as a sanity check, please check again that all the domains listed in the official documentation are reachable witin your corporate network .

 

As far as I know, most problematic during onboarding can be :

 

  • cr.eu1.edge.siemens.cloud
  • prod-eu-central-1-starport-layer-bucket.s3.eu-central-1.amazonaws.com

I hope you find this info useful :)

answered
0

Hello,

Thank you for your response! I double-checked all the domains, and after a long wait of about ten hours, the IEM finally configured itself. The process is significantly longer compared to usual configurations on a network without security restrictions.

Also, I’m currently trying to download applications to my IEM from the IEH, and I do have access to all domains (except for https://prod-eu-central-1-starport-layer-bucket.s3.eu-central-1.amazonaws.com, https://portal-relay.eu1.edge.siemens.cloud, and tcp://portal-relay.eu1.edge.siemens.cloud, which seem to be inaccessible). The download of the Common Configurator is taking several hours, which doesn’t seem normal.

I’m experiencing these issues on another company’s network located in a different geographical area.

Have you encountered similar slowness issues before?

answered