Accessing url blocked by fortigate action : server-rst

Server Reset is an action performed from server side, not by firewall.

Same issue here,  any idea how to solve it?

It is quite weird because it appeared after an upgrade to version 7.2.11.

Device tries to access its gateway ( Fortigate is in the middle with a virtual wire pair , in bridge mode) and this issue appeared. It tries to access it in https directly to an ip address as esa12 mentioned. I whitelisted ssl application with id 15895 but stil traffic is being blocked. Anything else (that passes through the same gateway) operates normally. 

Hi AEK , I am using virtual wire pair policy for the whole local interface (Fortigate in transparent mode) and the local devices cannot access their gateway in https. (etc https://192.168.100.1). My ssl inspection policy was in "read-only ssl inspection" mode and when i change it temporary in "no inspection" , page is accessible again. Please note that this happened after an upgrade from 7.2.9 to 7.2.11 version. So clearly Fortigate doesn't like the cerficate of this local page , but i cannot add an exception for ip address  in "read-only ssl inspection " mode. The log message is correct "server-rst". Thanks for assistance!

Greetings!

The 'server-rst' action in a log indicates that the server has reset the connection; this does not mean that the FortiGate is blocking the connection.

There are a few possible reasons that you would get a "server-rst" action, e.g. the client did not send any info for a while for some reasons and the server decides to terminate the session, or if the client sends a FIN and the server may decide to send a RST instead of a FIN.

Regards!

server-rst in this context was sent by the firewall itself, as mentioned above, most likely due to UTM not liking the cert on the server end 
some reading click 

On analyzer this looks like this