Troubleshooting

General problems with using IBM® WebSphere® Application Server in IBM Cloud® might include the inability to connect to your application or to see your environment. In many cases, you can recover from these problems by following a few easy steps.

Error: the provided instance profile ID does not exist

The error pertains to a vsi profile value, which follows "ibm_is_instance" in the error message.

on main.tf line 184, in resource "ibm_is_instance" "primary":
 184: resource "ibm_is_instance" "primary" {

The error occurs when a vsi profile value is not valid.

If the error message refers to "ibm_is_instance" "primary" then the base_vsi_profile or cell_dmgr_vsi_profile is invalid.
If it refers to "ibm_is_instance" "ihs" then cell_ihs_vsi_profile is invalid.
If it refers to "ibm_is_instance" "node" then cell_node_vsi_profile is invalid.

See available profiles at VPC Profiles.

Error: No SSH Key found

Error: No SSH Key found with name <INVALID_KEY_NAME>

The error means that the specified SSH key name (vpc_sshkey_name) is wrong or the key does not exist in the region based on the Region parameter.

Make sure that the SSH key name is specified correctly and that the key exists in the region where the VPC will be created. Refer to SSH Key for more details.

Error: SSH authentication failed while creating VSI

Error in Schematics log: timeout - last error: SSH authentication failed (USER@IP:22): ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain

The error means that the specified value for the vsi_os_admin_name or vsi_websphere_admin_name parameter is wrong.

If you changed the default value for the vsi_os_admin_name or vsi_websphere_admin_name parameter, then make sure that the new value does not contain the virtuser or wsadmin default value.