The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException

 Connection Filters allow one to deny access to UNWANTED Connections at the network level. Connection Filters can be used to protect server resources on individual servers, server clusters, or an entire internal network or Intranet. Connection filters are particularly useful when using the Administration port. Depending on the network firewall configuration, it may be possible to use a connection filter to further restrict administration access. A typical use might be to restrict access to the Administration port to only the servers and machines in the domain.

WebLogic Server provides a default connection filter called weblogic.security.net.ConnectionFilterImpl. This default connection filter accepts all incoming connections except the ones defined in the Administration Console as a Connection filter rule. Custom connection filters may be written  by implementing the classes in the weblogic.security.net package. This post will demonstrate the steps to configure Weblogic Connection Filters.

1st method from backend:

Log will be captured like below

Modify config.xml and change "deny" to "allow" 

 Bounce the WLS services.

2nd Method from frontend:

If not already done so, in the Change Center of the Administration Console, click Lock & Edit 

1. In the left pane, click on the domain name.
    
2. In the right pane, select the Security -> Filter tab.
   
   
   
3. Click the Connection Logger Enabled attribute to enable the logging of accepted connections.
    
4. Specify the Connection Filter to be used with the domain. This example uses the default connection filter weblogic.security.net.ConnectionFilterImpl
   
   
   
5. Specify the Connection Filter Rules. Make sure to use the syntax below while writing the rules:
   
   Syntax:
   target localAddress localPort action protocols
   
   
   • target specifies the client hosts that can connect to the Weblogic Server instance
   • localAddress defines the host address of the Weblogic Server instance to which any client can connect. If specifying an asterisk (*), the match returns all local IP addresses.
   • localPort defines the port on which the WebLogic Server instance is listening to which any client can connect. If specifying an asterisk (*), the match returns all available ports on the server.
   • action specifies the action to perform. This value must be only allow or deny.
   • protocols specifies the list of protocol names to match. The following protocols may be specified: http, https, t3, t3s, giop, giops, dcom, ftp, ldap. If no protocol is defined, all protocols will match a rule.
    
6. Click Save and in the Change Center of the Administration Console, click Activate Changes.
   
    
7. Restart all the WebLogic Server instances for changes to take effect.
   
   
   

 For the reference Oracle Support Documents:

Steps to Configure Weblogic Connection Filters :- Doc ID 1508748.1

Failed to Access WebLogic Console with Error :- Doc ID 2680320.1

Happy Learning !!