3/19/24, 1:01 PM Document 2680320.

1
PowerVLast Login: March 18, 2024 3:18 PM AST Switch to Cloud Support abdul (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community 2680320.1

Give Feedback... You have been directed to this document based on an ID match. Alternatively, click here to search on this phrase. Hide
Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

Failed to Access WebLogic Console with Error "[Socket:000445]Connection rejected, filter blocked Socket, To Bottom
weblogic.security.net.FilterException" (Doc ID 2680320.1)

In this Document Was this document helpful?

Symptoms Yes
No
Cause
Solution
Document Details
References

Type:
PROBLEM
APPLIES TO: Status:
PUBLISHED
Last Major
Jun 16, 2023
Update:
Oracle WebLogic Server - Version 10.3.1 to 12.2.1.4.0 Last Update:
Dec 16, 2023
Information in this document applies to any platform.

SYMPTOMS Related Products

Oracle WebLogic Server
When trying to login to WebLogic console URL, the following errors are seen in the browser:
Information Centers
Information Center: Oracle
WebLogic Server [1298857.2]

Get Proactive with Fusion

Middleware : Find Product
Certifications [1532687.2]

Information Center: WebLogic

Server Java Message Service
The Server Logs shows error (JMS) [1373135.2]

<Jun 12, 2020 7:53:05,492 AM GMT> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read
from it on <IP_ADDRESS>,507 during the configured idle timeout of 5 seconds.> Document References
<Jun 13, 2020 5:56:11,560 AM GMT> <Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked
No References available for
Socket[addr=<CLIENT_IP_ADDRESS>,port=<REMOTE_PORT>,localport=<WEBLOGIC_PORT>,protocol=http],
this document.
weblogic.security.net.FilterException: [Security:090220]rule 2>

Recently Viewed

Failed to Access WebLogic Cons

CAUSE Error &quot;[Socket:000445]Co
rejected, filter blocked Socket,
weblogic.security.net.FilterExce
It was found that the incoming traffic was blocked by the configuration filter for this IP address. [2680320.1]
Additional Information About th
WebLogic Server Vulnerability C
SOLUTION 2628 [2395745.1]
Steps to Configure WebLogic Co
To implement the solution follow the steps below: Filters [1508748.1]
WebLogic Server Support Patter
1. From a workstation that is not blocked by the filters (please see last NOTICE at end of this document otherwise), check the Server Hang [1264286.1]
configuration filter setting from the WebLogic Console >Domain name>Security tab>Filter. After Configuring Connection Fi
Disable t3/t3s, Web Application
REFER: Steps to Configure WebLogic Connection Filters (Doc ID 1508748.1) Extremely Slow. [2424164.1]
Show More
2. Verify the blocked IP addresses.

For blocked addresses, the following entries can be seen in configuration Filters:

CLIENT_IP_ADDRESS WEBLOGIC_IP WEBLOGIC_PORT deny PROTOCOL

The following are some of the syntax rules seen when configuring the filters:

Each rule must be written on a single line.

Tokens in a rule are separated by white space.
A pound sign (#) is the comment character. Everything after a pound sign on a line is ignored.
Whitespace before or after a rule is ignored.
Lines consisting only of whitespace or comments are skipped.
Filters are activated to all servers in your domain.
Filters are stored in the config.xml file.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=157718630652229&id=2680320.1&_adf.ctrl-state=xb7q9az90_249 1/2
3/19/24, 1:01 PM Document 2680320.1

Make sure to use the correct syntax for the Connection Filter Rules.

SYNTAX:

CLIENT_IP WEBLOGIC_IP WEBLOGIC_PORT ACTION PROTOCOL

where

CLIENT_IP_ADDRESS/CIDR specifies the client hosts that can connect to the Weblogic Server instance. You can set this
as a single IP or any CIDR range.
WEBLOGIC_IP 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.
WEBLOGIC_PORT 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 to allow or deny.
PROTOCOL/S specify 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.

3. Restart the Server, if any setting are done in Configuration Filters.

NOTICE: In the unexpected case the filters configuration was wrong and it causes the denial of access from any workstation,
which will also prevent from accessing the wl-console to correct the configuration, do:
1. Have the domain down
2. Take backup of config.xml (<DOMAIN_HOME>/config/config.xml)
3. Edit config.xml and remove the lines with contents: <connection-filter> and <connection-filter-rule>
4. Save the file.
5. Start AdmiinServer and reconfigure filters.

Didn't find what you are looking for? Ask in Community...

Attachments
console error when configuration filter is denying the access (51.72 KB)

Related
Products
Middleware > Application Servers > Weblogic Server > Oracle WebLogic Server > WLS Security > CONFIG

Back to Top
Copyright (c) 2024, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=157718630652229&id=2680320.1&_adf.ctrl-state=xb7q9az90_249 2/2