This assumes all Lagoon instances are using api.(domain) and ssh.(domain) but one can use whatever domain for said lagoon services

@serhat-ozkara can you specify more about your use case, what urls you are trying to use and why. This will us get a better picture of what is going on.

Hello @labboy0276,

When using custom lagoon environments, lagoon does not necessarily have to use ssh.mydomain.com or api.mydomain.com subdomains.
One can use my-own-sobdomain.mydomain.com for SSH address and my-other-subdomain.mydomain.com for API endpoint.

But on api.js file, it is assumed that lagoon SSH is hosted on SSH.mydomain.com and API endpoint on api.mydomain.com.

So, sharing the domain on ${this.host} for SSH and API endpoints for Lagoon integration, incorrectly assumes this approach.
Users should be able to set their own addresses and domains for SSH and API endpoint addresses and ports.

Hardcoding subdomains like this: https://api.${this.host}; or ssh.${this.host}; limits the usability.

Thanks,

@serhat-ozkara ok this is something we can do in the future. Most likely in Lando 4.