-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
[BUG] Transcription not working at all --- SOLVED --- #65
Comments
I can confirm the exactly same behavior. Deployment done without errors, all logs are not showing any errors. It just doesn't do anything. |
Same here. Running on Windows 11 with manual installation. I can see web UI but when uploading I get an error on the web UI (but no error in console) and then a "Waiting for transcription" on the file name after a moment, but no transcription occurs. |
Experiencing the same issue on Debian 11 using the quick install setup. |
I've been able to use CPU on Debian 12 (install via docker), but GPU loads are now not appearing to work and fail straight away. $ uname -a |
Hi, thans |
I confirm the same behavior on debian 11. Fresh install via docker, once you click start the dialog does away and nothing happens. Whishper logs don't show anything Mongo logs show WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also docker-library/mongo#485 (comment) |
HI everyone,
and i got the same result, the web ui is working great but when i tried to use it nothing happens. docker compose ps
I did this test in order to prove that it is not a matter related to a missing avx support . |
Where will I find nginx.conf? Still finding my way around docker :) here's my config files below, and also what I'm getting in my logs when I try to convert something with small, in english on GPU
|
Thnx for your reply, the nginx.conf should be int same folder of the docker-compose.yml.
after a close look to your file i think that you got it working because you are using the GPU version and not the CPU one. |
Solved by using the IP of the host in which docker runs, instead of the default in .env file. Maybe a note in the documentation could be useful, because the |
This worked for me. I updated the .env file and recreated the containers. It now accepts inputs and shows a progress bar for the upload. However I then get an "upload failed" error after this I havnt looked too far at this new error yet, I shall keep going |
Same here, upload fails |
Thnx a lot, I came back to work from my holidays today and I tested what you suggested this morning. |
HI to everyone, from ---> in my case eg As suggested by zezretro this modification should be INDICATED clearly in the official documentation. With my best whishes for a great 2024 I wanted to thank all the community for the support and the participation, and of course Last but not the least https://github.com/pluja pluja for this great project. |
Hey @mikele1976 I'm happy you were able to solve it. Sorry if I wasn't able to guide you much, lately I got pretty busy with many things, and I'm unable to keep up with everything. I updated the docs to mention this issue and provide the solution: https://whishper.net/troubleshooting/transcriptions-not-working/ |
I'm having this issue while running on a VPS, I've set the IP to the exact IP I'm connecting with, but it's still not working. |
upload fails here as well. is there a fix for this? |
Description
Transcription not working at all
To Reproduce
Steps to reproduce the behavior:
Environment
Logs and Configuration
Docker Compose Logs
Docker Compose File
.env
nginx.conf
The text was updated successfully, but these errors were encountered: