Just a quick update.
Found the note about setting up the “Portal Domain Name”.
I am not sure if this is a bug but it changes the API urls too. The case that we have is
This is the link that ALL our APIs live on. so you would access
gateway.mydomain.com/api/v/info
gateway.mydomain.com/otherapi/v1/info
When users hit this domain on NGINX via port 80, NGINX proxy_passes the request to an upstream server called tyke which is running on 5000 which then serves the request.
dashboard.mydomain.com
This is where admin access the dashboard. This is also served by NGINX with an upstream to :3000
portal.mydomain.com
This is the “marketing url” that we will use for people who want to consume our APIs. This is the semantic equivalent of http://dashboard.mydomain.com/portal. NGINX rewrites the url via:
location /{
# rewrite ^/\$ /portal break;
rewrite /(.*) /portal/$1 break;
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_pass http://dashboard;
}
I have turned off tyk managing hosts as previously advised. Using this:
Results in the gateway subdomain changing as well which is undesired.
The current setup still results in an:
Homepage Not Found error
at a loss 