Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors in console (failed names resolutions) after entering realm details #856

Open
Tracked by #819
michalinacienciala opened this issue Dec 7, 2023 · 0 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@michalinacienciala
Copy link
Contributor

michalinacienciala commented Dec 7, 2023

Sometimes (~50% of time) after entering given realm's details for the first time since reloading the page, there are some warnings/errors in the logs:

Access to fetch at 'https://resolve.unstoppabledomains.com/domains/?owners=0x277c1d7a4c4dd06733f19904d88c7f7fe3925b86&sortBy=id&sortDirection=ASC' from origin 'https://stage-live--taho-development.netlify.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
GET https://resolve.unstoppabledomains.com/domains/?owners=0x277c1d7…&sortBy=id&sortDirection=ASC net::ERR_FAILED 308 (Permanent Redirect)
GET https://resolve.unstoppabledomains.com/domains/?owners=0x200d2172fa4d6a1ae4a9e568ea4e749dd7a9ee7c&sortBy=id&sortDirection=ASC net::ERR_FAILED
react-spring_shared.modern.mjs:930 react-spring: Directly calling start instead of using the api object is deprecated in v9 (use ".start" instead), this will be removed in later 0.X.0 versions

The errors are failed names resolution (not sure if the last warning also is for the same reason).

Does not happen always for the sam realms.

@michalinacienciala michalinacienciala added the 🐛 bug Something isn't working label Dec 7, 2023
@michalinacienciala michalinacienciala changed the title Errors in console after entering realm details Errors in console (failed names resolutions) after entering realm details Dec 7, 2023
@xpaczka xpaczka assigned xpaczka and unassigned xpaczka Dec 13, 2023
@jagodarybacka jagodarybacka self-assigned this Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants