Hi all, I have a new Ubuntu 18.04 ISP Config (latest version) server which I'm using to replace an old server. I have migrated all the sites and data from the old server which was Ubuntu 14.04. Apache will not start on the new server since running the migration script. All the sites and structure appear to be correct but there is a depricated function in there which is not clear to me and Google hasn't been much help at all. The error is "Unknown parameter: mode=block". I'm just getting a mish mash of info on it but has anyone here had a similar issue when migrating sites to a new server? I have copied a log extract below. Thanks Jan 03 17:40:13 my_server_name systemd[1]: Starting The Apache HTTP Server... Jan 03 17:40:14 my_server_name apachectl[12425]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-i Jan 03 17:40:15 my_server_name apachectl[12425]: AH00526: Syntax error on line 122 of /etc/apache2/sites-enabled/100-example.com.vhost: Jan 03 17:40:15 my_server_name apachectl[12425]: Unknown parameter: mode=block Jan 03 17:40:15 my_server_name apachectl[12425]: Action 'start' failed. Jan 03 17:40:15 my_server_name apachectl[12425]: The Apache error log may have more information. Jan 03 17:40:15 my_server_name systemd[1]: apache2.service: Control process exited, code=exited status=1 Jan 03 17:40:15 my_server_name systemd[1]: apache2.service: Failed with result 'exit-code'. Jan 03 17:40:15 my_server_name systemd[1]: Failed to start The Apache HTTP Server.
Which migration script? How was it run? Where did the vhost file with error come from? Run Code: apachectl -S Check logs to see what is happening.
Jan 03 17:40:15 my_server_name apachectl[12425]: AH00526: Syntax error on line 122 of /etc/apache2/sites-enabled/100-example.com.vhost: Jan 03 17:40:15 my_server_name apachectl[12425]: Unknown parameter: mode=block this mode=block is on line 122 of /etc/apache2/sites-enabled/100-example.com.vhost i have no idea why it doesn't like it, or what it does. closest i can find is cross-site scripting protection. if so, you could try changing it to just Header set X-XSS-Protection "1; mode=block" or <IfModule mod_headers.c> Header set X-XSS-Protection "1; mode=block" </IfModule> or just comment out that line. then apache will either start, or let you know about the next vhost file with a configuration problem.