Error 503 with http after migration

Migration with ISPConfig migration script.
i stopped and started then networkd
when i put the command:
systemctl start systemd-networkd-wait-online
i get the following result:

Code:

root@server4:~# systemctl status systemd-networkd-wait-online
● systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; >
     Active: failed (Result: exit-code) since Sun 2020-11-22 11:08:38 CET; 2 da>
       Docs: man:systemd-networkd-wait-online.service(8)
   Main PID: 2139 (code=exited, status=1/FAILURE)

Nov 22 11:06:38 server4.cl-i.net systemd[1]: Starting Wait for Network to be Co>
Nov 22 11:08:38 server4.cl-i.net systemd-networkd-wait-online[2139]: Event loop>
Nov 22 11:08:38 server4.cl-i.net systemd[1]: systemd-networkd-wait-online.servi>
Nov 22 11:08:38 server4.cl-i.net systemd[1]: systemd-networkd-wait-online.servi>
Nov 22 11:08:38 server4.cl-i.net systemd[1]: Failed to start Wait for Network t>
lines 1-11/11 (END)

I just installed the server according to:
https://www.howtoforge.com/tutorial...l-pureftpd-bind-postfix-doveot-and-ispconfig/
any idea what i can do more?

 

Hi,
systemctl stop systemd-networkd

systemctl start systemd-networkd

this is what i just did to stop and start the service again but after starting i had the same problem.
should i reboot the server?

 

same problem after reboot:

Code:

root@server4:~# systemctl status systemd-networkd-wait-online
● systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; >
     Active: failed (Result: exit-code) since Tue 2020-11-24 14:26:29 CET; 25s >
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 328 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exit>
   Main PID: 328 (code=exited, status=1/FAILURE)

Nov 24 14:24:29 server4.cl-i.net systemd[1]: Starting Wait for Network to be Co>
Nov 24 14:26:29 server4.cl-i.net systemd-networkd-wait-online[328]: Event loop >
Nov 24 14:26:29 server4.cl-i.net systemd[1]: systemd-networkd-wait-online.servi>
Nov 24 14:26:29 server4.cl-i.net systemd[1]: systemd-networkd-wait-online.servi>
Nov 24 14:26:29 server4.cl-i.net systemd[1]: Failed to start Wait for Network t>
lines 1-12/12 (END)

but this command without any problems:

Code:

root@server4:~# systemctl list-units --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

 

1. Does network access work on that host?
2. How did you do the network configuration?
3. What is the configuration now?

 

i can ping to other hosts, and the websites on this server are available.
the configuration according to this:
https://www.howtoforge.com/tutorial...l-pureftpd-bind-postfix-doveot-and-ispconfig/

 

Can you ping from other hosts this host and get answers back?
Are you websites working now, so the error about networkd-wait-online is just annoying? You could disable that service, if it does nothing useful. If you want to fix the error, my guess is there is something wrong in 00-installer-config.yaml that makes networkd-wait-online fail. Use Internet Search Engines with error message to find reasons and possible repairs.

 

I just made a fresh installation according to:
https://www.howtoforge.com/tutorial...l-pureftpd-bind-postfix-doveot-and-ispconfig/
and i get the same error with networkd when i put the command

Code:

systemctl list-units --failed

then i get this result:

Code:

root@server6:/tmp/ispconfig3-nightly/install# systemctl list-units --failed
  UNIT                                 LOAD   ACTIVE SUB    DESCRIPTION                     
● systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured

so i think this is a common problem and not a problem caused by my installation.
Can i just let it like this and use the new server or should this problem should be resolved?
thanks for your idea and help as always