You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a NODEJS restful api web service that I have built in order to call this nodejs library from my custom application. When serving up the web service locally using LocalHost, the nodeJS service works great and brings back all the resellPrices as expected. However, when I deploy NODEJS restful api online for consumption, I get strange results. For example when deploying to AWS, I get no resellPricing at all. And then when deploying to Render, I get flightClub prices but no prices for stockX. As mentioned when running it via LocalHost, all resellPrices are brought back.
Does anyone have any idea why I might be having issues with the deployed hosted version where the Local Version works fine?
The text was updated successfully, but these errors were encountered:
I'm almost certain that this is due to bot protection. If you use a proxy on your server, it might eliminate this issue. Bot protection on these services probably filters the ISPs that your servers are hosted on. While this library is unmaintained, I'm sure a workaround is available if you use a proxy.
Hello,
I have a NODEJS restful api web service that I have built in order to call this nodejs library from my custom application. When serving up the web service locally using LocalHost, the nodeJS service works great and brings back all the resellPrices as expected. However, when I deploy NODEJS restful api online for consumption, I get strange results. For example when deploying to AWS, I get no resellPricing at all. And then when deploying to Render, I get flightClub prices but no prices for stockX. As mentioned when running it via LocalHost, all resellPrices are brought back.
Does anyone have any idea why I might be having issues with the deployed hosted version where the Local Version works fine?
The text was updated successfully, but these errors were encountered: