EMS 7.4.4 Web Server 500 Error after migration

This doesn't look as certificate error.

Try check service logs from CLI.

https://docs.fortinet.com/document/forticlient/7.4.4/ems-cli-reference/370213/emscli-service-log

Hi,
service log --all.
I can't attach/upload the logfile?? 
I see several errors in the log, including this one:

I don't know if this is the cause.

It suddenly occurred to me that I haven't configured a static IP address.
When I try to do this now, I get the error below.

Thanks.

Thanks. I overlooked that.
I've now set a static IP address, but after a restart, I still can't start the console.

I'm seeing several errors, but I'm not sure which ones might be related to my inability to access the console.
The output of the "service log --all" exceeds the number of characters I can post.
Is there a specific log file I can post the contents of?

Yeah, it does appear broken at present. I can't download it either.

Considering it's freely available anyway, I've grabbed it off the Support Portal for you and dropped it here.

@pukalsu1
I think you posted your comment in the wrong post. :-))

The temporary location of the log file is valid for 6 days.
https://filebin.net/7yy95cba1plqqmkc

The reason for not being able to reach the web console is apparently that after the migration, the connection is made with the IP address of the Windows EMS server instead of the Ubuntu EMS server.

The IP address of the Ubuntu EMS server is 10.10.10.22.

Did something go wrong during the migration? I didn't see any error during or after migration process

How can I change the listener IP?

I see the following error frequently appearing in various log files:
2025-09-20T08:54:49.024+0200 ERROR manager/socket_pool.go:212 Failed to create new socket connection: dial tcp 127.0.0.1:65432: connect: connection refused

Is this related to a server restart? The server was restarted around 8:54 AM.

Thanks

I see the DB port is 6432 while I think the default should be 5432.

Can you share the following:

service get --all
config get db db.host
config get db db.port

Hi AEK,
See printscreen

I see it is configured on the default port 5432, so I wonder why the app is trying to connect to 6432 instead?

I don't know how this could happen, and I don't find a way how to tell the app to use 5432 instead of 6432, but as a workaround I'd suggest to try change the DB port to 6432 so the app can find it with its current setting.

config set db --db.port 6432

The reboot the VM (probably required).

In case it doesn't work then rollback the change like this:

config unset db --db.port

Hope it helps.

Unfortunately, changing the DB port to 6432 didn't solve the problem.

I'll run the migration again.

Fortunately, I created a snapshot, so I can start the migration in a few minutes.

I only ran certain commands after the migration, such as configuring a static IP address and the timezone.

I don't think that's the cause, but I'll run the following before migrating:

system set network ip --adapter="eth0" --ip="10.10.10.22/24" --dns="10.10.10.1" --gateway="10.10.10.1"

execute timezone set Europe/Amsterdam

Are there any other commands I can run before starting the migration?

For example, I see that updates can be installed.

How can I install the updates?