Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
SteveJW
New Contributor III

EMS 7.4.4 Web Server 500 Error after migration

In my test environment, I migrated from FortiEMS client 7.2.2 to 7.4.4.
We deployed EMS on a Hyper-V VM.
I didn't encounter any issues during the migration.
I want to start the console now, but I'm getting the error below.
WebserverError.jpg

I think it has something to do with the certificate, among other things.
How can I remove it and/or configure/import a new certificate?

20 REPLIES 20
AEK
SuperUser
SuperUser

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

AEK
AEK
SteveJW
New Contributor III

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

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.
ipsettings.jpg

Thanks.

AEK

It seems you forgot the "ip" sub command.

system set network ip | FortiClient 7.4.4 | Fortinet Document Library https://docs.fortinet.com/document/forticlient/7.4.4/ems-cli-reference/230835/system-set-network-ip

AEK
AEK
SteveJW
New Contributor III

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

AEK

Can you share the new error from the log file?

AEK
AEK
SteveJW
New Contributor III

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?

pukalsu1
New Contributor

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.

10.0.0.0.1 192.168.1.254
SteveJW
New Contributor III

@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.
Fortiemems7.4.4Error.jpg

The IP address of the Ubuntu EMS server is 10.10.10.22.
EMSUbuntuIP.jpg

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
Fortiems7.4.4Error.jpgFortiems7.4.4Error1.jpg
Is this related to a server restart? The server was restarted around 8:54 AM.

Thanks

AEK
SuperUser
SuperUser

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

 

AEK
AEK
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors