Skip to main content

The browser can’t open Trade

When the page doesn’t open after installation, the inbound port is usually blocked or the address is wrong.

Common causes

  • The page loads until it times out: most cloud servers block inbound traffic by default. In the security group or firewall in your cloud console, add a rule that allows inbound TCP 443. This is the only port needed (on Alibaba Cloud ECS, tick Web HTTPS traffic in the security group; on AWS EC2, tick Allow HTTPS traffic from the internet). Then run the install command with --enable-ip-cert to switch to a trusted certificate.

  • The browser warns that the certificate is not trusted: the installer failed to get a trusted certificate for the public IP, so Trade uses a self-signed one for now. In the certificate details, compare the SHA-256 fingerprint with the one the installer printed. Continue only if they match. After you open the port, run the install command with --enable-ip-cert to switch to a trusted certificate.

  • Wrong address: copy the link the installer printed on a line by itself, and paste that whole line into the browser’s address bar without any text around it. On the same network, use the LAN URL. A server behind NAT or a shared public IP also needs port forwarding for remote access.

  • The trading service isn’t running: the page opens System maintenance. Sign in as administrator and choose Start Trade.

You don’t have the address

Run the install command on the server again. With an existing deployment it only checks the runtime status, keeps the current version and configuration, and prints the URL again. Install has the command.

Was this article helpful?