question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hello. I’ve worked with various commentators about this project on issue #243. I’ve seen great success from moving to from to a GitHub specific application. I’m sharing this information beforehand to state that I’ve seen the project in a working state before.

With that being said, my project is currently experiencing a cors proxy issue. Below is the following error I’m receiving:

Access to XMLHttpRequest at 'https://dev.staticman.net/v3/entry/github/discordUser/discordRepo/discordBranch/staticmanId' from origin 'http://localhost:4000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Note: Information beginning with discord and staticman have been replaced by default names because it’s a private repository.

This behavior has started happening since yesterday. Are there any known issues with the application as of then? Is anyone else able to replicate this issue with the current application v3?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

7reactions
eduardoboucascommented, Mar 21, 2019

The development API (dev.staticman.net) is running on a free tier Heroku instance. Because too many people started using it in their projects, it reached its limits.

I have merged the v3 endpoints into the production API (api.staticman.net), which should now have the exact same capabilities as the development one. If you use this one instead, you should no longer see these errors.

Please reopen this issue if the problem still occurs.

Thanks!

1reaction
onwingslikeeaglescommented, Mar 18, 2019

Update: Another developer on our team mentioned that it’s not a cors issue after all. Cors was turned off on their browser and they received an error code of 503. This to me infers that there’s an issue with the system itself. The issue still exist as of writing this comment.

Read more comments on GitHub >

github_iconTop Results From Across the Web

blocked by CORS policy? CORS Proxy is Solution
The solution to bypass CORS is to use a Proxy. A Proxy server, that forwards your request as it is. But, problems with...
Read more >
What are CORS proxies, and when are they safe? - HTTP Toolkit
CORS proxies can leak private state between independent origins · You make a request to a.com in your web page, through your CORS...
Read more >
How to Solve CORS using a Proxy Server and Koa
The good news is that there are now new and different ways to solve this issue, from using an extension for your favorite...
Read more >
What is CORS Proxy? Three APIs that Offer CORS Features
This API offers a fast proxy to bypass CORS policies in any HTTP request. If you are getting CORS errors, you can use...
Read more >
What is CORS? | Reverse Proxy for CORS - miniOrange
It is an HTTP origin header-based method that allows a server to specify any origins (domain) other than its own from which a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found