By MislavSag
I have developed API endpoint using R plumber package (https://www.google.com/search?q=plumber+R&rlz=1C1GCEA_enHR855HR855&oq=plumber+R&aqs=chrome..69i57j35i39l2j69i60j69i65j69i60l2.1344j0j15&sourceid=chrome&ie=UTF-8). Endpoint is GET request with 4 query parameters. The endpoint works as expected when I try it on my PC. Then I tried to use it inside Quantconnect framework: https://www.quantconnect.com/docs/algorithm-reference/importing-custom-data
When I use their SubscriptionTransportMedium.RemoteFile method it works as expected, but when I use their SubscriptionTransportMedium.Rest method it returns an error page:
ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://207.154.227.4/alphar/radf_point?’ target=‘blank’>http://207.154.227.4/alphar/radf_point?
Access Denied.
Access control configuration prevents your request from being allowed at this time. Please contact your service provider if you feel this is incorrect.
Your cache administrator is webmaster.
Generated Tue, 11 May 2021 06:56:39 GMT by qc-gateway (squid/3.5.27)
I ma not sure if the above error is returned because of:
- my plumber endpoint setup or
- Digital ocean set up or
- Quantconnect Rest method?
I don’t know much about networks, so I can’t understand what is the problem. On the community in QC, they said I should add login creds, but I don’t understand why should I do that to make endpoint to work?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
If I am reading this correctly, the error looks like it’s coming from QuantConnect’s gateway and not your R plumber setup or DigitalOcean directly.
The key line is:
Access control configuration prevents your request from being allowed at this time.
QuantConnect’s REST transport likely goes through a proxy, which may block or sanitize some request formats or headers. If it works via RemoteFile but not Rest, their proxy might be blocking unauthenticated or plain GET requests to external endpoints.
You don’t necessarily need login credentials for your API, but QuantConnect may require them to allow the request through their system.
To narrow it down, you can try adding a simple auth header or query token and see if that changes anything or switch to RemoteFile if that works, no need to fight the Rest transport if QC blocks it at the gateway level
If it still fails, you might need to contact QuantConnect support to ask if their Rest transport blocks external APIs without auth.
- Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.