A marketplace node is an ordinary node launched from a ready-made product image instead of a plain operating system or a GPU card. The image ships with an operating system plus a prepared software stack, so you start from a working environment rather than installing everything yourself. Plan, pricing, network, security, and Launch all work the same as for any other node. Sign-in, finding a product, launching it, and reaching the application each have an entry below. For the full creation flow, see Create a node.
Cannot sign in to the Marketplace
Section titled “Cannot sign in to the Marketplace”The marketplace uses the same sign-in as the rest of MyAccount. If it shows you as logged out, sign in to MyAccount first, then refresh the marketplace page; a successful sign-in carries across. If you do not have a MyAccount login yet, sign up there before trying the marketplace.
If you still cannot get in, contact support with the account name and the exact error message.
Cannot find a marketplace product
Section titled “Cannot find a marketplace product”The Marketplace tab lists only the products enabled for your account and region. The list can differ from another account’s.
Use the search box to filter the list by product name. To browse the whole catalog, use the Explore all Marketplace Solutions link at the top of the list; it opens the marketplace in a new tab. If no products appear at all, continue with a CPU node instead, or contact support to ask whether the product is available to your account.
Product details are incomplete
Section titled “Product details are incomplete”A product’s page shows Description and Features, plus Additional Documentation and Release Notes. Technical details you need, such as the ports an application uses, live in Additional Documentation rather than the Description. If a field is genuinely missing after you check those, contact the vendor or E2E support.
Launch Node does nothing
Section titled “Launch Node does nothing”Launch needs you to be signed in. If nothing happens when you click it, sign in to MyAccount and try again.
When you launch from the external marketplace site, the portal pre-fills the product’s OS and version on the plan screen, so you do not choose them again. If you meant to launch from inside MyAccount instead, open Compute > Nodes, click Add New Node, and pick the Marketplace tab there.
Wrong region or plan during launch
Section titled “Wrong region or plan during launch”Location is already fixed when the product appears in your list. What you pick on the plan screen is the Instance Type, the plan, and the pricing option (on-demand or committed). The product’s OS and version are fixed too.
If the plan you want is not offered, check that the product is available in your region and account, then pick the plan that matches the job you plan to run. Review the summary panel before you launch: it shows the product’s name, OS, and version instead of an Instance Type, so confirm those are the ones you meant.
Marketplace node fails to provision
Section titled “Marketplace node fails to provision”A marketplace node provisions like any other node, so a failure here is a normal node provisioning failure. Open the node from Compute > Nodes and check its state, then follow the steps for that state in Troubleshooting node actions and lifecycle. If the node never starts, contact support with the node’s name, IP address, and your customer reference number (CRN), the exact error text, and when it happened.
Node is running but the application is not reachable
Section titled “Node is running but the application is not reachable”The node being Running does not mean its application answers. The usual cause is a port the application needs that the security group does not allow. Check the product’s Additional Documentation for the ports it requires, then make sure the security group attached to the node allows those ports from the sources you connect from. Common ports are 22 for SSH, 80 for HTTP, and 443 for HTTPS, but the exact set depends on the product.
If the application still will not answer, connect to the node and check that the application itself started. See Troubleshooting node networking and connectivity for connection problems, and confirm the node’s own firewall allows the same port.
The launch configuration (VPC, public IP, security group ports, and SSH keys) is set during creation the same way as for any other node. If you need to review or change it after launch, see Create a node, and connect with Connect to a Linux node or Connect to a Windows node.