Learn how to prevent and recover from issues in the WebLogic Remote Console.
If you’re having trouble connecting to your Administration server from the WebLogic Remote Console, here are some steps you can take to identify and fix the issue.
Use curl to test access to the Administration server:
curl -v --user <username>:<password> http://<adminServerHost>:<adminServerPort>/management/weblogic/latest/domainConfigcurl -v -k --user <username>:<password> https://<adminServerHost>:<adminServerPort>/management/weblogic/latest/domainConfigIf the curl command was successful on an HTTPS connection, the connection issues are likely because the WebLogic Remote Console does not trust the SSL certificate of the Administration server. To fix this, you can either import the Administration server’s certificate into your client’s keystore, or, if you’re using demo certificates, turn on the Insecure Connection option when connecting to Administration server.
If you receive a 401 error after running the curl command, make sure that the WebLogic user is assigned one of the following roles: Admin, Deployer, Operator or Monitor.
If the WebLogic Server domain is in a different network, configure the proxy server of the WebLogic Remote Console.
If your domain is in a Docker container or behind a load-balancer, make sure to open a port that makes your Administration server’s management URL accessible to clients.
You may encounter this error when making changes to an Administration Server provider. The WebLogic Remote Console checks for validation errors when you click Save, or when you commit the change using the Shopping Cart. If an error message occurs, you must identify and correct the problem before you can activate the changes.
If you installed the console extension, you can review all pending changes in the Shopping Cart.
If the cause of the configuration error is not obvious:
If you cannot determine the cause of the error, try discarding your configuration changes and then making them one at a time to isolate the change responsible for the error.
The WebLogic Remote Console does not validate the data that you insert into WDT model files. As a result, the WebLogic Remote Console may accept changes or values that are invalid and which may present problems when the model file is used to build or update a domain. For example, adding integer values that are invalid or out of range for a specific setting, or removing a server or target but not updating the deployments to select a different server or target can cause issues.
For more information on acceptable values, refer to the WebLogic Deploy Tooling documentation.
If the WebLogic Remote Console application shuts down unexpectedly with this error: Failure reading auto prefs, the auto-prefs.json file may be corrupted. auto-prefs.json saves state information about the WebLogic Remote Console and should not be modified by users unless it is corrupted.
If the file is corrupted, you can reset it but you will lose all data regarding your projects.
To reset the file, delete the auto-prefs.json file, then relaunch the WebLogic Remote Console.
auto-prefs.json is located in:
$HOME/.config/weblogic-remote-console/auto-prefs.json/Users/<user>/Library/Application Support/weblogic-remote-console/auto-prefs.jsonC:\Users\<user>\AppData\Roaming\weblogic-remote-console\auto-prefs.jsonCheck the role of the user you used to log into the Administration Server. Only administrators have access to the full functionality of WebLogic Remote Console. Users with other roles such as Deployers, Operators, or Monitors have limited access to areas outside the scope of their responsibility.
For an overview of what users in each role can view or do, see Understand Access Discrepancies.
The Administration Server uses REST to communicate with itself and its Managed Servers. When REST communication is blocked, the Monitoring perspective of WebLogic Remote Console can neither report accurate information on the statuses or statistics of Managed servers nor perform most management tasks. Also, the Edit perspective cannot create or remove deployments.
To test the REST connection:
For HTTP, run:
curl -v --user <username>:<password> http://<adminServerHost>:<adminServerPort>/management/weblogic/latest/serverRuntime
For HTTPS, run:
curl -v -k --user <username>:<password> https://<adminServerHost>:<adminServerPort>/management/weblogic/latest/serverRuntime
If the command fails, then a more general connectivity issue is affecting your domain. See ‘Connectivity Issues’ for next steps.
For HTTP, run:
curl -v --user <username>:<password> http://<adminServerHost>:<adminServerPort>/management/weblogic/latest/domainRuntime/serverRuntimes/<adminServerName>
For HTTPS, run:
curl -v -k --user <username>:<password> https://<adminServerHost>:<adminServerPort>/management/weblogic/latest/domainRuntime/serverRuntimes/<adminServerName>
If this command fails, then the problem is a REST communication failure between servers.
You need to identify and resolve the issue affecting REST communication. REST issues are often due to flawed domain configurations. Possible causes include, but are not limited to: