Skip to main content
Ted
Staff
Staff
June 26, 2025

Troubleshooting Tip: Replacement Message lost after upgrading to v7.4

  • June 26, 2025
  • 0 replies
  • 474 views

 

Description

This article describes an issue with the system.replacemsg.webproxy configuration is lost after upgrading FortiGate from before v7.4.1 to v7.4.1 or later, and the configuration is replaced with the default value.

Scope FortiGate.
Solution
  1. Where a FortiGate is running on 7.2.11, it has its web proxy replacement message, 'deny'.

 

FortiGate-VM64 # config system replacemsg webproxy "deny"
FortiGate-VM64 (deny) # show full-configuration

config system replacemsg webproxy "deny"
    set buffer "<!DOCTYPE html>
<html lang=\"en\">
<head>
<meta charset=\"UTF-8\">
<meta http-equiv=\"X-UA-Compatible\" content=\"IE=8; IE=EDGE\">
<meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">
<style type=\"text/css\">
..skip..
</style>
<title>Access Denied</title>
</head>
<body><div class=\"message-container\">
<div class=\"logo\"></div>
<h1>Access Denied</h1>
<p>FortiOS 7.2.11 - Customized Replacement Message before an upgrade</p>
</div></body>
</html>
"
set header http
set format html
end

 

  1. After upgrading to v7.4.4, the replacement message 'deny' is replaced with the default replacement message.

 

FortiGate-VM64 (deny) # show full-configuration
config system replacemsg webproxy "deny"
    set buffer "<!DOCTYPE html>
<html lang=\"en\">
<head>
<meta charset=\"UTF-8\">
<meta http-equiv=\"X-UA-Compatible\" content=\"IE=8; IE=EDGE\">
<meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">
<style type=\"text/css\">
body {
height: 100%;
font-family: Helvetica, Arial, sans-serif;
color: #6a6a6a;
margin: 0;
display: flex;
align-items: center;
justify-content: center;
}
..skip..
</style>
<title>Access Denied</title>
</head>
<body><div class=\"message-container\">
<div class=\"logo\"></div>
<h1>Access Denied</h1>
<p>The page you requested has been blocked by a firewall policy restriction.</p> ---> Default replacemsg.
</div></body>
</html>
"
    set header http
    set format html
end

 

The problem is fixed starting from v7.4.8 and v7.6.3.