After Ubuntu update last week no access to axigen and no domains in list

I been running Axigen server privately for myself a couple of years without any big problems. But now last update of Ubuntu the server don’t reply(connection refused) I went to axigen/run/axigen.cfg and found the listeners, I changed the webadmin to…restarted axigen and could reach the page…But now there are no doinins listed!? What happens and what can I do?


It looks that now you are using the default Axigen configuration file.

Can you provide me the output of below system command:

ls -l /var/opt/axigen/run


Thank you for your reply.
Some configuration like smtp out seems to still be there.

Here is the output:

$ ls -l /var/opt/axigen/run
total 348
-rw-r----- 1 axigen axigen 52986 maj 30 2018 axigen-05-30-17:19:13.cfg
-rw-r----- 1 axigen axigen 54015 jul 3 14:50 axigen-07-04-11:22:29.cfg
-rw-r----- 1 axigen axigen 36865 okt 10 20:52 axigen-10-10-21:38:25.cfg
-rw-r----- 1 axigen axigen 36863 okt 16 13:29 axigen-10-16-13:30:25.cfg
-rw-r----- 1 axigen axigen 36863 okt 16 13:30 axigen-10-16-13:32:00.cfg
-rw-r----- 1 axigen axigen 37293 okt 16 13:32 axigen.cfg
-rw-r----- 1 axigen axigen 29456 mar 9 2017 axigen.cfg.old
-rw-r----- 1 axigen axigen 2179 okt 16 13:30 axigen_lk.txt
-rw-r----- 1 root root 5 okt 16 13:30
-rw-r–r-- 1 axigen axigen 190 okt 16 13:30 axigen.reg
-rw-r–r-- 1 axigen axigen 5 maj 12 2018
drwxr-x— 2 axigen axigen 36864 okt 16 13:32 old_configs


You may check the backup configuration file (axigen-10-10-21:38:25.cfg) for the domain configuration that should be similar with:

domainStorageParams = (
domainName = "YOUR_DOMAIN"
domainStorageLocation = "/var/opt/axigen/domains/YOUR_DOMAINmaxFiles=128&maxFileSize=1048576"
domainObjectStorageLocation = "/var/opt/axigen/domains/YOUR_DOMAIN/objects?maxFiles=128&maxFileSize=1048576"
messageStorageLocations = (

where YOUR_DOMAIN is your domain.

Assuming that axigen-10-10-21:38:25.cfg is the correct config file you may use the below procedure to restore the configuration

  1. Stop Axigen service (service axigen stop)
  2. create a backup of actual cfg file (mv /var/opt/axigen/run/axigen.cfg /var/opt/axigen/run/axigen.bad)
  3. restore the backup config file (cp -p /var/opt/axigen/run/axigen-10-10-21:38:25.cfg /var/opt/axigen/run/axigen.cfg)
  4. ensure that axigen system user is owner of /var/opt/axigen/run/axigen.cfg file
  5. start Axigen service (service axigen start)
  6. check in Webadmin if your domains are loaded.

This made it, one of the older file did work :smiley:
So why the config got bad in the update I don’t know yet, haven’t happened before.
But it’s up again.

Thank you so much for your time and help.

Kind regards

1 Like