The Amlen WebUI is not working
There are several common reasons why the Amlen WebUI might not work.
Is the Amlen WebUI container running in your Docker environment?
If the Amlen WebUI container is not running, you cannot connect to the Amlen WebUI. To determine whether the container is running, enter the following command:
docker ps -a
If the status is not Running
, start the Amlen WebUI container.
You can start the container by entering the following command: docker start
<WebUI container name>
Does restarting the Amlen WebUI process resolve the issue?
With some issues, restarting the Amlen WebUI process can resolve the issue.
- You can stop the container by entering the following command:
docker stop <WebUI container name>
- You can start the container by entering the following command:
docker start <WebUI container name>
- You can stop the process by entering the following command:
systemctl stop imawebui
- You can start the process by entering the following command:
systemctl start imawebui
Is the port in use?
If you have changed the port, and can no longer access the Amlen WebUI you can check if the new port is in use.
You must first stop the Amlen WebUI.
If you are using Docker you can stop the process by entering the following command:
docker stop <WebUI container name>
If you are not using Docker you can stop the process by entering the following
command: systemctl stop imawebui
You can then check to see whether the port is in use. If the port is in use, you might be able to locate the application that is using that port and temporarily stop that application. This might provide you with enough time to start the Web UI again by using the port. You can then select a new port that is valid and available.
To start the Amlen WebUI you can use one of the following commands:
If you are using Docker you can start the process by entering the following command:
docker start <WebUI container name>
If you are not using Docker you can start the process by entering the following
command: systemctl start imawebui
Does closing the browser application resolve the issue?
If you experience problems with the Amlen WebUI, closing the browser application might resolve the issue. After you close the browser application and all of your browser windows, open a new browser application and log in again.
Can you ping the Amlen WebUI host from the machine that you are running the browser from?
If the ping test is not successful, there might be a problem with your network setup or the Eclipse Amlen server might not be powered on. If the ping test is successful, check that the network Eclipse Amlen server configuration is correct.
Is the Amlen WebUI connection timing out?
If you have a slow connection, your connection to the Amlen WebUI might time out.
By default, the HTTP Read timeout is set to 20 seconds. If you increase this value, you can reduce the chance of a timeout. For more information about changing the HTTP Read timeout, see Changing the HTTP read timeout.
Is the Amlen WebUI not working after a firmware update?
The Amlen WebUI might show a blank page after a firmware update. To resolve this issue, clear your browser cache and try again.
Is the Amlen WebUI not loading in Firefox?
- If you have a DNS server that can map a host name to the Amlen WebUI IP address, you can assign a host name to the static IP address and use the host name to access the Amlen WebUI.
- Replace the Amlen WebUI self-signed certificate with a certificate from a certifying authority. You must use a different browser to replace the certificate. For more information about replacing the Amlen WebUI certificate, see Changing the Amlen WebUI security certificate.
- Replace the Amlen WebUI self-signed certificate with a certificate that the user can install into Firefox. You must use a different browser to replace the certificate. For more information about replacing the Amlen WebUI certificate, see Changing the Amlen WebUI security certificate.
Are you using Internet Explorer 10?
Ensure that you are using the latest version with the latest fixes by running Windows™ Update.
Is the URL used to connect to the Amlen WebUI the fully qualified domain name?
If you use a short name in the URL,
for example, https://abc:9087
, you might see the
error code CWLNA5001
, and a server status of UNKNOWN
.
To resolve this issue, you must use the fully qualified domain name,
for example, https://abc.example.com:9087
.
Is the IP address that you are using configured correctly?
If you are using a static IP address, ensure that the address is from the IP range that is defined for a given VMnetX adapter in the Virtual Network Editor.
If you are using a dynamic IP address, ensure that DHCP is enabled for the corresponding VMnetX adapter(s) in the Virtual Network Editor. The Use local DHCP service to distribute IP address to VMs checkbox must be selected.