Yes , we followed the same document for installation.
We are using the proxy for internet in server where we have installed TYK setup . In upstream endpoint we have put server ip address instead of hostname as we don’t have DNS entry for FQDN .
I can see the error in tyk-gateway as below :-
[Mar 20 12:27:16] ERROR Request failed with error Get 127.0.0.1/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:27:21] ERROR Request failed with error Get 127.0.0.1/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:27:26] ERROR Request failed with error Get 127.0.0.1/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:27:31] ERROR Request failed with error Get 127.0.0.1/register/node: unsupported protocol scheme “”; retrying in 5s
As per previous error in tyk-gateway , we changed ip address(127.0.0.1) for “connection_string” to actual ip address of system and restarted tyk-gateway service but error is same as following :-
root@tyk:/var/log/upstart# tail -f tyk-gateway.log
[Mar 20 12:39:55] ERROR Request failed with error Get <system_ip>/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:40:00] ERROR Request failed with error Get <system_ip>/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:40:05] ERROR Request failed with error Get <system_ip>/register/node: unsupported protocol scheme “”; retrying in 5s
[Mar 20 12:40:10] ERROR Request failed with error Get <system_ip>/register/node: unsupported protocol scheme “”; retrying in 5s
We have deployed TYK in another system having white listed ip address and there is no any error in tyk-gateway but still not able to access the new tyk API url
root@newtyk:/var/log/upstart# tail -f tyk-gateway.log
[Mar 20 13:17:25] INFO main: Sub-router created for domain domain=
[Mar 20 13:17:25] INFO main: Loading API api_name=test
[Mar 20 13:17:25] INFO main: Checking security policy: Token api_name=test
[Mar 20 13:17:25] INFO gateway: Loaded: test api_id=8ec9b8e0cd9943e25c7d023fd1f59384 org_id=5aa908057bd7d51a5a2984e1 server_name=-- user_id=-- user_ip=–
[Mar 20 13:17:25] INFO main: Processed and listening on: /test/{rest:.*}
[Mar 20 13:17:25] INFO host-check-mgr: Loading uptime tests…
[Mar 20 13:17:25] INFO main: Initialised API Definitions
[Mar 20 13:17:25] INFO main: API reload complete
[Mar 20 13:17:25] INFO reload: complete
[Mar 20 13:17:25] INFO Initiating coprocess reload