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

Getting a 403 response from dev.cid.contact #1288

Closed
TorfinnOlsen opened this issue Feb 20, 2023 · 2 comments · Fixed by #1290
Closed

Getting a 403 response from dev.cid.contact #1288

TorfinnOlsen opened this issue Feb 20, 2023 · 2 comments · Fixed by #1290

Comments

@TorfinnOlsen
Copy link
Collaborator

TorfinnOlsen commented Feb 20, 2023

When attempting to resolve to https://dev.cid.contact receiving a 403 response from the gateway.

https://dev.cid.contact/

403 ERROR
The request could not be satisfied.
Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: KXC0UqN_O3EFVYUFS1txQ2EV9ILcGe0BVUZMVvsdsCazeg4HEqI8xQ==

First reported by Muhammad Arslan @thebeard on slack 12:36pm PST 02/20/23

https://filecoinproject.slack.com/archives/C02T827T9N0/p1676925391520659

Troubleshooting steps taken so far:

I attempted to duplicate the issue from my machine and got the same response.

@masih
Copy link
Member

masih commented Feb 20, 2023

Issue was with the landing page only and restored by #1289

Root cause likely due to chagnes introduced as part of latest commits to indexstar.

@masih
Copy link
Member

masih commented Feb 20, 2023

OK found the root cause: missing -- here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants