-
Notifications
You must be signed in to change notification settings - Fork 111
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
error loading prompt... is the backend running? #15
Comments
Make sure you have set the corpus path in docker-compose.yml. |
I got a similar error on windows. the batch script is broken, had to fix many things to make it work. But a major error was |
I had the same issue when accessing not by localhost url. autossh -L 3000:localhost:3000 DestinationIPFrontend Then recording with http://localhost:3000 in your local browser should work. |
check index.js file in api folder in frontend. in there apiRoot is mentioned as localhost change the localhost to your backend running IP. |
I am assuming this code has never been fixed because a) this ticket is still open and b) I just got this error in 2023. Feels like this product needs some love if even the prebuilt dockers don't work properly. Seems to be a lot of bugs which have simple (for a developer) fixes. |
I've just installed MRS on Linux with docker. So far it builds everything and I have two new containers:
My docker instances are on a NAS server (192.168.1.100) and I'm accessing it with my network computers (192.168.1.0/24). My mrs-backend IP is 172.21.0.2/16 while the mrs-frontend is 172.21.0.3/16. I can ping between them through IP and hostname as expected.
I can also telnet to ports 5000 and 3000 of my docker host from my network computers.
So far, I can connect to the frontend just fine. But when I go to start recording, a error loading prompt... is the backend running? message appears on the screen
On the
/src/prompts/
I have both theenglish_corpus.csv
andenglish_corpus_no_dups.csv
files.So, I'm a bit lost, becasue logs shows no errors
The text was updated successfully, but these errors were encountered: