Learn how to identify and recover from issues in WebLogic Server or WebLogic Remote Console.
Perform these preliminary troubleshooting steps to get started:
If the Administration Server cannot reach a Managed Server or cluster, you may be able to determine the cause using WebLogic Remote Console.
In the Monitoring Tree, go to Environment, then Servers. Use the State column to determine the current life cycle state of a server instance or cluster.
If the Administration Server cannot reach the server to determine its state, the server will be marked as Unreachable.
Click on a server or cluster whose state is Unreachable.
Click the Troubleshoot tab. WebLogic Remote Console will automatically attempt to send test administration traffic to the server or cluster.
Depending on the result of the test, WebLogic Remote Console provides different information:
unknown.Use the information gathered from this troubleshooting test to help determine the cause of the connection issues between the Administration Server and server instances or clusters.
If you experience any issues with WebLogic Remote Console, then you can check its log files to determine the cause of the issues.
Open Help, then Toggle Developer Tools and select the Console tab.
Read the log messages to see they provide enough information to determine the cause of your issue.
WebLogic Remote Console also generates a log file, out.log, for each session. Open the log file and review its contents.
The location of out.log varies depending on your platform:
$HOME/.config/weblogic-remote-console/out.log/Users/user/Library/Application Support/weblogic-remote-console/out.logC:\Users\user\AppDataRoaming\weblogic-remote-console\out.log
Log file entries from previous sessions are saved to a new file in the same directory, marked by date: out-yyyy-mm-dd.log.If you want to generate log files for WebLogic Server, see Log Messages instead.
This page describes the known issues associated with WebLogic Remote Console.
You cannot:
WebLogic Remote Console includes most of the MBean properties that the WebLogic Server Administration Console supported. However, due to limitations in the WebLogic REST API, some MBeans are omitted, including some that are deprecated. If you require an MBean property that is not currently available in WebLogic Remote Console, then file an enhancement request in the WebLogic Remote Console GitHub repository.
If you are sure your login credentials are correct but you’re receiving an Unexpected Error Response error, it might be because your credentials contain unsupported characters.
By default, WebLogic Remote Console uses HTTP Basic Authentication which supports a limited character set. Characters outside that set, for example, Japanese characters, cannot be used in either usernames or passwords.
Workaround: If you wish to continue using credentials with these characters, then when you connect to an Administration Server from WebLogic Remote Console, you must enable Use Web Authentication in the provider connection dialog box. The WebLogic Remote Console will send you to the external authentication portal. See Configure Web Authentication.
In Hosted WebLogic Remote Console, an orange banner appears along the top of the console that indicates it cannot reach the Administration Server.
Solution: Try logging into Hosted WebLogic Remote Console again. In the browser’s address bar, enter http://hostname:port/rconsole/signin (or https://hostname:port/rconsole/signin) and re-enter your credentials.
If you delete an item but then discard the change instead of committing it, WebLogic Remote Console will not show the restored item immediately.
Workaround: Navigate away and then back to the affected page and the previously deleted item will become visible. If the deletion affected the navigation tree, such as deleting a node, you can collapse and then re-expand the navigation tree and the node will re-appear.
If you open Hosted WebLogic Remote Console in multiple browser tabs and edit the domain, the different instances will interfere with each other and may result in configuration errors.
Solution: Only use Hosted WebLogic Remote Console in one browser tab at a time.
If you use an HTTP proxy server (such as Oracle HTTP Server or Apache HTTP Server) and use path based routing to manage access to your WebLogic Server instances, then, when using web authentication, WebLogic Remote Console cannot properly resolve the paths to direct users to the appropriate URLs.
WebLogic Remote Console cannot connect to a WebLogic Server Administration Server.
If you experience issues connecting to an Administration Server when using WebLogic Remote Console, then you may need to update the connection settings between the application and the domain. Use the following methods to identify which setting may be causing the issue.
Test access to the Administration Server using curl. Make sure to use a WebLogic user that is assigned one of the following roles: Admin, Deployer, Operator or Monitor.
For HTTP connections, run:
curl -v --user *username*:*password* http://*adminServerHost*:*adminServerPort*/management/weblogic/latest/domainConfig
For HTTPS connections, run:
curl -v -k --user *username*:*password* https://*adminServerHost*:*adminServerPort*/management/weblogic/latest/domainConfig
If you can connect successfully over HTTPS, then the problem is likely that WebLogic Remote Console does not trust the SSL certificate of the Administration Server. You can either import the Administration Server’s certificate into your client’s keystore, or, if you’re using demo certificates, enable the Make Insecure Connection option when you connect to the Administration Server.
Make sure your Administration Server’s management endpoint, management/*, is accessible to clients. It may be blocked if your domain is behind a load-balancer or firewall, or is in a Docker container. You will need to expose the endpoint manually.
You should also make sure that the value of the Remote Console Helper Context Path attribute (RemoteConsoleHelperMBean.ContextPath) has not been changed. The default value is console, which WebLogic Remote Console appends to the domain URL. If you modify the context path, it may prevent WebLogic Remote Console from successfully connecting to the Administration Server. Do not change it unless you understand the possible impacts to Desktop WebLogic Remote Console. See Configure Web Authentication.
If the Administration Server resides in a different network than WebLogic Remote Console, then make sure the proxy settings of WebLogic Remote Console are properly configured to allow communication between the two. See Connect using a Proxy Server.
You may need to add a location match stanza for the management/* endpoint to the domain configuration file, config.xml.
Certain features or screens in WebLogic Remote Console are hidden if your current user is not assigned the appropriate permissions.
For security purposes, WebLogic Remote Console restricts what a user can see or do depending on their role. Only administrators have access to the full functionality of WebLogic Remote Console.
Try logging in as a user with more elevated permissions.
For more information, see Access Limitations.
If you believe a feature is missing and it is not a case of inadequate permissions, you can open an enhancement request in the WebLogic Remote Console GitHub repository.
WebLogic Remote Console reports that it is experiencing REST communication issues between servers.
When REST communication is blocked, it may prevent further configuration to the domain or cause the Monitoring Tree perspective to report inaccurate statuses for Managed Servers.
Certain configuration changes can block REST communication between servers, including, but not limited to the following examples:
weblogic-jwt-token from the default Identity Asserter provider’s Active Types.You must update your configuration changes so they no longer block REST communication.
WebLogic Remote Console reports an invalid configuration in your domain.
To make sure that changes to your domain are valid, WebLogic Remote Console performs validation checks whenever you save or try to commit a change. If WebLogic Remote Console reports an invalid configuration error, then you must identify and correct the change before you can commit your changes.
If you still cannot determine the cause of the error, then you may need to discard all of your changes and then reapply them one at a time to isolate the change responsible for the error.
WebLogic Remote Console does not validate WDT model files. It will accept changes or values that are invalid and which may prevent the WDT model file from building or updating a domain. For example, if you add integer values that are invalid or out of range for a specific setting, or remove a server or target but do not update the deployments to select a different server or target, WebLogic Remote Console will not flag these errors.
For information on acceptable values, refer to the WDT Documentation.
WebLogic Remote Console shuts down unexpectedly with a Failure reading auto prefs error.
The auto-prefs.json file saves state information about WebLogic Remote Console including details on projects and providers. Users should not touch this file unless it becomes corrupted.
If auto-prefs.json does become corrupted, you can reset it, but all of your data regarding your projects will be lost. The data for your domain will be unaffected.
auto-prefs.json. The location of auto-prefs.json varies depending on your platform:
$HOME/.config/weblogic-remote-console/auto-prefs.json/Users/user/Library/Application Support/weblogic-remote-console/auto-prefs.jsonC:Users\user\AppDataRoaming\weblogic-remote-console\auto-prefs.json