SSH and ports

With SSH (a secure connection to your server), you work in your own editor. The gateway (the entry point for SSH) is included in all plans.

Connect with VS Code

A key is like a house key for your computer. If you do not have one yet, create it with ssh-keygen -t ed25519. The file ending in .pub is the public part.

1. In your instance (your development server), open Settings → SSH keys.
2. Paste your public key there.
3. In my.envbay.com, open the service page (the page for your instance).
4. Read the port in the SSH gateway field. A port is like a door number.
5. In VS Code, install the Remote - SSH extension.
6. Select Remote-SSH: Connect to Host….
7. Type ssh -p <port> <project>@ssh.<customer>.envbay.dev.
8. Open the folder /var/www/html.

This is your project. The project must be running for this. If Envoryx shows you a different host name under the IDE tab (envoryx.<customer>.envbay.dev), still use ssh.<customer>.envbay.dev; port and user are the same.

If something does not work

• Timeout: Check the port. Some company networks block high ports.
• Permission denied: Your key has not been added, or the username is wrong. The username is the project name.
• Nothing works at all: Is the project running? Is your instance locked? Then SSH rejects the sign-in. Read Security and fair use.
• You are stuck: Open a ticket with us (a message to support). The steps are in the Help chapter.

Connection details

Item	Value
Host	ssh.<customer>.envbay.dev (IPv4 and IPv6). Envoryx itself shows the name of your UI, envoryx.<customer>.envbay.dev, under the IDE tab; that currently works too, but only ssh.<customer> is guaranteed, including after your instance is moved
Port	22000 + n; your value is on the service page in the SSH gateway field
User	the project name (slug), optionally with runtime suffix (shop.node)
Sign-in	public key under Settings → SSH keys or an API token as password

Port 22 is not used. Inside your instance, the gateway listens on 2222; externally it is mapped to 22000 + n. Static sites offer only SFTP and scp. The author describes the username and sign-in under Terminal, SSH & logs. After several failed attempts, Envoryx briefly blocks the requesting address for the project.

In all examples, enter the value from your service page for <port>.

Example for ~/.ssh/config

Host envbay-shop
  HostName ssh.<customer>.envbay.dev
  Port <port>
  User shop
  IdentityFile ~/.ssh/id_ed25519

Editor and IDE

• VS Code (Remote-SSH): ssh -p <port> shop@ssh.<customer>.envbay.dev, then open /var/www/html.
• JetBrains: In the project, enable Allow JetBrains Gateway for this project (off by default). According to Envoryx, the backend needs 2 to 4 GB of memory and downloads about 1.5 GB. On the Free plan (1 GB) and the Starter plan (2 GB for the whole instance) this is too tight, so choose Team or Agency for this. Details: IDE and remote development.
• SFTP and scp: The project is located at /var/www/html.

Tunnel to project services

Databases and add-on services listen only locally and are not reachable from the internet. From your computer, you reach them through an SSH tunnel:

ssh -N -p <port> -L 15432:127.0.0.1:<target port> shop@ssh.<customer>.envbay.dev

Then connect your tool to 127.0.0.1:15432. Envoryx shows the target port and the ready-made connection details in the Database area, after you enable Publish port on the host; for managed instances, the IDE area shows the tunnel command. For everyday use, the database browser (Adminer) is often enough; see Databases. Debugger ports (Xdebug, Node, debugpy, Delve, rdbg, JDWP) are listed in the Envoryx docs; Delve, rdbg and JDWP have no sign-in and belong only in the tunnel.

Network rules

• Inbound, only ports 80, 443 and the instances’ SSH ports (from 22000) reach your instance.
• Outbound connections to the internet are allowed, except mail ports 25, 465 and 587. Connections to other customers and to Envbay systems are largely blocked; name resolution (DNS) and the package cache stay reachable.
• New outbound connections are limited to 50 per second (short peaks up to 200).

Caution

Port scans and connection floods from your instance trigger the automatic lock; see Security and fair use.

If the connection does not work

• Timeout: Is the port correct? Some networks, such as company Wi-Fi, block outbound connections to high ports.
• Permission denied: The key is not added under Settings → SSH keys, or the username does not match the project name. Check with ssh -v.
• Project not running: Shells and debuggers only work while the project is running.
• Instance locked: SSH and SFTP reject the sign-in; see Security and fair use.
• If the problem persists, open a ticket and attach the output of ssh -v (without keys or passwords).