You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.
We are trying to host the latest version (downloaded from "releases" this morning, 2.4 M1) and it won't work. We get the splash page, but trying to use any corpus (including the built-in ones) fails. Trying to upload a corpus results in a never-ending spinner, while selecting something default (e.g. Jane Austen) pops up with an error "Failed Attempt to Create a Corpus". Many of the links for help also fail. I wonder if these could all be part of the same problem: half the links (and presumably the corpus creation/upload stuff) is trying to utilize addresses like "http://127.0.0.1:8888/docs/#!/guide/corpuscreator", which obviously fails for a real server that isn't localhost. Something in the code is using :, apparently, rather than respecting our real server (voyant.byu.edu). We've been having this problem for months, but now it's getting urgent.
If the problem is on our end, please let me know what I need to change in server-settings.txt or something else; right now we've stayed away from touching anything other than the port, which we are accessing in Apache via a ReverseProxy. My suspicion, though, is that the code mis-constructing paths.
The text was updated successfully, but these errors were encountered:
We are trying to host the latest version (downloaded from "releases" this morning, 2.4 M1) and it won't work. We get the splash page, but trying to use any corpus (including the built-in ones) fails. Trying to upload a corpus results in a never-ending spinner, while selecting something default (e.g. Jane Austen) pops up with an error "Failed Attempt to Create a Corpus". Many of the links for help also fail. I wonder if these could all be part of the same problem: half the links (and presumably the corpus creation/upload stuff) is trying to utilize addresses like "http://127.0.0.1:8888/docs/#!/guide/corpuscreator", which obviously fails for a real server that isn't localhost. Something in the code is using :, apparently, rather than respecting our real server (voyant.byu.edu). We've been having this problem for months, but now it's getting urgent.
If the problem is on our end, please let me know what I need to change in server-settings.txt or something else; right now we've stayed away from touching anything other than the port, which we are accessing in Apache via a ReverseProxy. My suspicion, though, is that the code mis-constructing paths.
The text was updated successfully, but these errors were encountered: