When trying to log into the MOVEit Automation web page with the correct credentials, the error message,  'There was an error, please try again'. is seen. How can this be resolved?


Automation is not starting up after a patch and rebooting. There is a Windows Event Viewer error.

Some oth er symptoms to be aware of:
th eWeb Admin log f(miadminweb.log file may contain the following error:
023-03-10 08:04:50.849  INFO 7496 --- [https-openssl-apr-443-exec-2] c.j.s.e.handlers.RestExceptionHandler    : POST /api/v1/token ~> 400 BAD_REQUEST

Look in the Web Admin's tomcat folder, in the serts folder (C:\Program Files\MOVEit\MOVEit Web Admin\Tomcat\certs).
If any of the .pem files are empty (0 KB) that is illustrative of a problem:

This error often presents after a server reboot or upgrade/migration situation because the SSL Certificate involved may be flagged as invalid if it expired since the last reboot. 

The error prevents users from logging in to the Web Portal. The Admin Console may also be unavailable or it may be working depending on the affected certificate and certain encryption settings discussed in the Cause section. 

This issue is usually caused when the SSL certificate being used by the MOVEit Automation service is not valid, no longer present, or broken.

This issue can happen with any of the following situations

1. Missing/expired/broken certificate in the MOVEit Automation config.
   1. 
2. Broken or expired certificate assigned to the Tomcat server for the Automation Web Admin portal itself. 

              Possibly a certificate containing illegal characters. See https://tomcat.apache.org/tomcat-8.5-doc/config/http.html

        3. Multiple Certificates with same name and different expiration dates in Certificate Store
        4. IPV6 is enabled on the Windows server hosting the MOVEit Automation application.

Before attempting any of the below steps , please try to stop/start the Web Admin service first to see if that solves the issue and if not , move forward with the below steps :

Situation 1:   certificate missing/expired/broken in the Moveit Automation config

• Open the Automation config, under the General tab (https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/General-Tab.html), then check to make sure a certificate is applied to the config. If there is no certificate, apply a certificate to the config. If one is applied, confirm that the certificate is not expired; to do that, click on the little square with the 3 dots, navigate to Local machine and expand it, click on personal, and check the applied certificate in the personal store. If the Certificate is broken, replace it with a new one.

Situation 2:  Broken or expired certificate assigned to the Tomcat server 

• First, review the log file at the following path (X:\Program Files\MOVEit\MOVEit Automation WebAdmin\Tomcat\logs\miadminweb.log) and you should see an entry similar to this:
  • 2020-02-05 11:03:34.104 ERROR 2132 --- [https-openssl-apr-8443-exec-4] c.i.moveit.central.model.CentralAdmin : Unable to connect to Central server at host <host IP>
  • 2020-02-05 11:03:34.112 DEBUG 2132 --- [https-openssl-apr-8443-exec-4] c.i.moveit.central.model.CentralAdmin : (API 802648035): Signing off
  • 2020-02-05 11:03:34.112 DEBUG 2132 --- [https-openssl-apr-8443-exec-4] c.i.m.c.model.CentralContextManager : (Central Context 457d9373-2e30-4c58-9653-80e442214f80): Context disposed
  • 2020-02-05 11:03:34.127 INFO 2132 --- [https-openssl-apr-8443-exec-4] c.j.s.e.handlers.RestExceptionHandler : POST /api/v1/token ~> 400 BAD_REQUEST
• This entry in the miadminweb.log  shows that there is an issue with the SSL certificate applied to the Tomcat server. To resolve this, please see: How to update MOVEIt Automation(Central) Web Admin SSL certificate?  Note you may need to restart the server after this update step.
• As described above, check the Tomcat\certs folder for 0 KB length .pem files. This is illustrative of a bad certificate (the .pfx file is somehow defective). Get a new good certificate.

Situation 3: Multiple Certificates with same name and different expiration dates in Certificate Store

1. Go to Start->Run, type mmc and hit OK.
2. In the window that appears, go to File > Add/Remove Snap-in.
3. Select Certificates on the left, click Add, then choose Computer account. Next, Finish, then OK on the Add or Remove Snap-ins window.
4. On the left, expand Certificates (Local Computer), then Personal, then Certificates.
5. Verify that there are not multiple certificates with the same name that are expired listed.  (Either rename, move or delete expired certificates)

Situation 4: IPV6 is enabled on the Windows server hosting the Moveit Automation application

1. Go to the 'Control panel'.
2. Click on 'Network and Internet'.
3. Click on 'Network and Sharing center'.
4. Click on 'change adapter settings'.
5. Right click on the Ethernet adapter and chose 'properties' >>> Find the IPv6 entry and uncheck it  to disable IPv6 then click OK.
6. Restart the server.

Situation 5: Automation is holding onto an expired certificate
        1. As a last resort, try rebooting the Automation server. In one case it is believed that an expired certificate was not completely released until the Automation server was rebooted.

Siuation 6: Something happened to the certificate information within Automation
         1. In one case, the certificate appeared to be valid and NOT expired. But the error kept
occurring. Rebooting the Automation server cleared whatever was occurring and allowed logging into Web Admin and VB Admin successfully.