app.forestadmin.com connecting to wrong URI

[SpekkoRice]

Hi,

I'm a new user, trying out Forest Admin for the first time.
I'm running my trial on a hosted server of mine.

I apologize in advance if I'm not entirely familiar with all the Forest Admin Jargon.

Description:

When lumber asks for your IP/hostame your app will be running on, your connector app (app.forestadmin.com) should use this provided IP/hostname to authenticate you.

Installation output:
I've changed the particulars of my domains, emails and names to more generic use cases

$ lumber generate "My_Admin"
? What's the database type?  mongodb
? What's the database name? my-sandbox
? What's the database hostname? localhost
? What's the database port? 27017
? What's the database user?  
? What's the database password? [optional]  [hidden]
? Does your database require a SSL connection?  No
? Use a SRV connection string?  No
? What's the IP/hostname on which your application will be running?  mysubdomain.domain.com
? What's the port on which your application will be running?  3050


> Hooray, installation success!

change directory: 
 $ cd My_Admin

install dependencies: 
 $ npm install

run your application: 
 $ npm start

:~$ cd My_Admin/
:~/My_Admin$ npm install
npm notice created a lockfile as package-lock.json. You should commit this file.
added 88 packages from 52 contributors and audited 172 packages in 3.27s
found 0 vulnerabilities

:~/My_Admin$     npm install lumber-forestadmin --save

> core-js@2.6.9 postinstall /home/ubuntu/My_Admin/node_modules/core-js
> node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
> https://opencollective.com/core-js 
> https://www.patreon.com/zloirock 

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

+ lumber-forestadmin@1.0.5
added 138 packages from 120 contributors and audited 783 packages in 6.119s
found 0 vulnerabilities

:~/My_Admin$     lumber install lumber-forestadmin --email myEmail@domain.com --projectName My_Admin
> Forest Admin Installation

> Create your admin panel:
> Hooray, installation success!

> Your admin panel is available here: https://app.forestadmin.com/xxxx

:~/My_Admin$ npm start

> My_Admin@0.0.1 start /home/ubuntu/My_Admin
> node ./bin/www

Your application is listening on port 3050.

To confirm that my port forward on my server is working under my domain:

cURL output:

$ curl -v -s https://mysubdomain.domain.com
*   Trying 104.27.157.109...
* TCP_NODELAY set
* Connected to mysubdomain.domain.com (123.123.123.123) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: OU=Domain Control Validated; OU=PositiveSSL Multi-Domain; CN=sni49711.cloudflaressl.com
*  start date: May 24 00:00:00 2019 GMT
*  expire date: Nov 30 23:59:59 2019 GMT
*  subjectAltName: host "mysubdomain.domain.com" matched cert's "*.domain.com
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO ECC Domain Validation Secure Server CA 2
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55f7729ad720)
> GET / HTTP/2
> Host: mysubdomain.domain.com
> User-Agent: curl/7.64.0
> Accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200 
< date: Wed, 29 May 2019 08:29:29 GMT
< content-type: text/html; charset=utf-8
< set-cookie: __cfduid=d5269e66fe3185d0c94d4aaf834ac3ae31559118568; expires=Thu, 28-May-20 08:29:28 GMT; path=/; domain=.domain.com; HttpOnly
< x-powered-by: Express
< vary: Origin
< access-control-allow-credentials: true
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
< cf-ray: 4de719ceb8d4ac70-JNB

Also when I visit my subdomain, I'm greeted with "Your application is running!"

However when I try to login, it tries to hit localhost:

Expected Behaviour:

app.forestadmin.com adheres to the configured parameters set by the application loaded.

Is there another step I'm missing in setting up my Forest Admin UI?

EDIT:
For now I'm just run the environment locally, I have a hunch that my application is limited because I'm still in "Development", although I'm not 100% sure how I can remove myself from "Development" on ForestAdmin.

[SpekkoRice]

I see I'm able to define production environment AFTER I've set things up locally. Then I'm able to define my custom domain and the app adheres to it.