How to solve: Web Engine container fails to resolve hostname of Docker host machine and cannot connect to Identity Service or License Server

Reproduced in Version: IIoT Services 14.1.2404.17001

This is a fixed bug (BUG 281835), but it will only be included in the documentation with the new releases.

If you encounter following Error description: Error: Identity Server not available. Status code: 500

The above error occurs when a link is clicked in the web engine behind which there is a ScreenSwitchFunct to a login screen.

Problem Description:

With certain Docker Desktop for Windows installations, the Web Engine container cannot find the Identity Service via it's public hostname.
It's a DNS resolution issue within the container. So technically the stack of Docker on Windows is giving issues on certain machine configurations.

With setting the DNS manually in the Windows Docker Desktop Engine, this will also allow correct name resolution with the host machine.
With this approach, it is even not necessary anymore to add the "extra_hosts" entry for the Web Engine.

There is a solution:

1.   Update to the newest build (14.2.2405.8001)
   

Steps done:

.env file now updated to include:

When configured the Web Engine is able to be successfully connected. 

• Related Articles

• FAQ: Installation of Service Engine 12 Build 162015 in Ubuntu 22.04 LTS as Docker container

  Refer to the attached file: Docker on Ubuntu 22.04 - FAQ.pdf This guideline is solely shared for demonstration and educational purposes. Feel free to contact COPA-DATA Support for further clarifications.

• Checklist: Data Missing in Service Engine

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

  Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• FAQ: Delayed variable updates on Terminal Server Service Engine Clients occur in some scenarios.

  In some cases, Service Engine Clients on a Terminal Server might have delayed variable updates. Depending on the system those delays can be about 2 seconds. A reason for this can be a hostname resolution procedure, which is needed to determine ...

• Checklist: The Logic Service to Service Engine connection does not work

  Time estimate:   30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Screenshot and followed ...