Projects and addresses
Each project in your instance (your own development server) has its own address. Here you can read how it is built and who can see your project.
Where can my project be reached?
Section titled “Where can my project be reached?”Each project has its own address:
https://<project>.<customer>.envbay.dev<customer> stands for your instance name, <project> for the project name. The padlock in the browser shows that the connection is encrypted (HTTPS). Envbay obtains the certificate (the digital ID of this connection) automatically. You do not need to set anything up.
Who can see my project?
Section titled “Who can see my project?”New projects are private. Anyone who knows the address must first sign in to your instance.
To let someone else take a quick look, share a link:
- Open your project.
- Click More actions at the top.
- Click Share publicly.
- Copy the address shown.
- Send the address on.
The link expires after the time you chose. You can also end it earlier. Share only copies without important data.
Your own domain
Section titled “Your own domain”Your own domain (for example www.beispiel.de) is not planned at the moment. Your projects run under Envbay addresses.
If something does not work
Section titled “If something does not work”- Share publicly is greyed out: Your plan excludes sharing. Open a ticket with us (a message to support). The steps are in the Help chapter.
- The page shows “is stopped”: The project is not running. Start it in your instance. If your instance is locked, read Security and fair use.
- The browser warns about the certificate: Wait a moment and reload the page. If the warning persists, open a ticket with us.
Addresses at a glance
Section titled “Addresses at a glance”| What | Address |
|---|---|
| Interface of your instance | https://envoryx.<customer>.envbay.dev |
| Project | https://<project>.<customer>.envbay.dev |
| SSH gateway | ssh.<customer>.envbay.dev, see SSH and ports |
All names under <customer>.envbay.dev lead to your instance via wildcard DNS. The DNS entries are public and run without an upstream proxy service. In Envoryx, each domain name belongs to exactly one project.
Certificates
Section titled “Certificates”HTTPS is always active. Port 80 redirects to HTTPS. Envbay obtains a wildcard certificate for <customer>.envbay.dev and *.<customer>.envbay.dev via Let’s Encrypt (DNS-01) and renews it 30 days before expiry. The Fleet Manager of Envbay fetches the certificate, not your instance; Envoryx shows it as “Certificate from your host”. For a new instance, the fetch starts right after setup; otherwise it runs in the hourly cycle. You cannot upload your own certificate for these addresses. You also do not need to install a local certificate authority: the certificate is publicly trusted.
Your own domains
Section titled “Your own domains”Your own domains (for example via a CNAME to a project address) are currently not supported at Envbay: the platform only routes names under envbay.dev to your instance and issues no certificate for foreign names. Therefore, do not enter foreign domains in Envoryx and do not set up a CNAME to your project address.
Private, shares and visibility
Section titled “Private, shares and visibility”New projects are private (fixed in the plan). The interfaces of add-on services, such as database tools, also sit behind your instance’s sign-in, and the ports of your projects listen only locally. A project is reachable from outside via:
- your instance’s interface (after signing in),
- a time-limited share: More actions → Share publicly starts a tunnel with a random address. Duration in the dialog: 15 minutes, 1, 4 or 24 hours (default 1 hour). The address is new for each share and ends earlier when stopped, renamed or deleted, or with End the share. Details: Sharing,
- an SSH tunnel,
- permanent public visibility for individual projects, if your plan allows it.
Public projects and public shares are features the plan can switch off. If Share publicly is disabled for you, ask support. Whoever opens a project is responsible for it; release only staging copies without sensitive data.
Rules in front of your application (address allow lists, HTTP Basic Auth, redirects, headers) are set in Envoryx; see Domains and HTTPS. Anyone who publishes a service’s port directly bypasses these rules.
If a lock is in place
Section titled “If a lock is in place”If your instance is locked (open invoice or suspected misuse), all projects are stopped. Project addresses then respond with “is stopped” (HTTP 503). The sign-in page of the instance stays reachable; you see the lock notice after signing in. See Security and fair use.