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

Update eval's PWS_HOST to Resolve 500 Errors When Running Locally #167

Closed
soufianerafik opened this issue Jan 16, 2025 · 1 comment · Fixed by #168
Closed

Update eval's PWS_HOST to Resolve 500 Errors When Running Locally #167

soufianerafik opened this issue Jan 16, 2025 · 1 comment · Fixed by #168
Assignees

Comments

@soufianerafik
Copy link
Contributor

Description:
During a recent live session, we encountered an issue with the PWS_HOST configuration while running locally. The following was observed:

  1. Using PWS_HOST=https://it-wseval1.s.uw.edu consistently resulted in 500 errors.
  2. Switching to PWS_HOST=https://wseval.s.uw.edu resolved the issue, and the application worked as expected.
@soufianerafik
Copy link
Contributor Author

Update: I verified that the change took effect in EWS EVAL environments on 5/25/23. Any configurations or bookmarks still pointing to the old endpoint will no longer work.

For more information please refer to UW Connect's REQ7051889.

@soufianerafik soufianerafik self-assigned this Jan 16, 2025
soufianerafik added a commit that referenced this issue Jan 16, 2025
@soufianerafik soufianerafik linked a pull request Jan 16, 2025 that will close this issue
2 tasks
soufianerafik added a commit that referenced this issue Jan 16, 2025
* fix(config): Update PWS_HOST with new value from REQ7051889

* chore(backend): Update old comment to replace it-wseval1 with wseval
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.

1 participant