Skip to content

"Internal Server Error" when trying to activate domain #2205

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

Closed
GamiumWorld opened this issue Apr 18, 2022 · 3 comments
Closed

"Internal Server Error" when trying to activate domain #2205

GamiumWorld opened this issue Apr 18, 2022 · 3 comments
Labels
stale Issues that are old and soon to be closed

Comments

@GamiumWorld
Copy link

GamiumWorld commented Apr 18, 2022

Describe the bug
A clear and concise description of what the bug is.
Custom domain vote.gamium.world has been added to domain.json and approved. All steps instructed at https://docs.snapshot.org/spaces/add-custom-domain have been completed, but when calling to https://ina9pk8175.execute-api.us-west-2.amazonaws.com/dev?domain=vote.gamium.world the server answers with {"message": "Internal server error"}

To Reproduce
Steps to reproduce the behavior:

  1. Just execute https://ina9pk8175.execute-api.us-west-2.amazonaws.com/dev?domain=vote.gamium.world
  2. See error
@mktcode
Copy link
Contributor

mktcode commented Apr 19, 2022

Hey! We are discussing possible improvements. I assume the issue right now is that we have an additional deployment step, so the updated domain list is not immediately "live". But not sure about this.

@stale
Copy link

stale bot commented Jun 18, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Jun 18, 2022
@samuveth samuveth added stale Issues that are old and soon to be closed and removed wontfix This will not be worked on labels Jun 19, 2022
@stale stale bot removed the stale Issues that are old and soon to be closed label Jun 19, 2022
@stale
Copy link

stale bot commented Aug 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issues that are old and soon to be closed label Aug 30, 2022
@stale stale bot closed this as completed Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues that are old and soon to be closed
Projects
None yet
Development

No branches or pull requests

3 participants