The portal won’t work unless it has been correctly configured - are you able to confirm that you’ve set this up with at least one published API (details on how to do this can be found here)?
If setting that up still doesn’t work, it might be worth adding a trailing forward slash to the end of the URL when making a GET request to it (i.e., www.tyk-portal-test.com/portal/). Let me know if that works or if you’re still having trouble with your portal.
Hey Jess, Thanks for your reply. I can confirm that i have correctly setup the portal following the same tutorial. Moreover i can access the portal by directly hitting the target URL with my browser. The error is thrown only when i try to use the API proxy url.
And i just tried. Putting the extra slash does not help
Have you checked your SSL settings? One Docker user who reported the issue in the past turned out to have SSL issues which could explain your case. We do have a Troubleshooting guide that mentions a proxying issue that can cause this but it wasn’t really targeted at Docker users (you may want to update your Docker image just in case however).
I’m unable to replicate the problem unfortunately, so if fixing the SSL configuration or updating the Docker image doesn’t work, could you please try attaching your API definitions to this ticket (you can export APIs to JSON format using the yellow button on the “Edit API” page)?
I tried the tyk-docker-pro-demo , and in this it is throwing a not found error when accessing the portal link directly and a connection refused error when accessed through the proxy url . I have successfully set up the portal and also added the API catalogue to it. Is there anything I am missing.
Have you definitely added the www.tyk-portal-test.com to your hosts file? The newer Docker build that Martin linked to also mentions that you would need to add www.tyk-test.com to /etc/hosts before this could work.
one thing that i have noticed is that when i try to open the portal from the “your developer portal” menu on the top it takes me to a completely different non-existant IP address and the request fails with a connection timeout