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

'Server not reachable'; (re)open if Kõnele default server not working #63

Closed
mrts opened this issue Dec 29, 2018 · 33 comments
Closed

'Server not reachable'; (re)open if Kõnele default server not working #63

mrts opened this issue Dec 29, 2018 · 33 comments

Comments

@mrts
Copy link

mrts commented Dec 29, 2018

Hello!

Many-many thanks once again for this great app! I find it indispensable and use it a lot. However, since yesterday I get the 'server not reachable' error message when I try to dictate something.

@alumae
Copy link

alumae commented Dec 29, 2018

Seems that TTÜ network maintenance has broken something. Should be fixed in a few days if not sooner.

@mrts
Copy link
Author

mrts commented Dec 29, 2018

Alright, fingers crossed that it's an easy fix!

@alumae
Copy link

alumae commented Dec 29, 2018

Should be fixed now.

@mrts
Copy link
Author

mrts commented Dec 30, 2018

Yep, works again, many thanks!

@mrts mrts closed this as completed Dec 30, 2018
@Te-M
Copy link

Te-M commented Jan 10, 2019

I haven't actually been able to try this app out because a webservice used for my configuration (http://bark.phon.ioc.ee/speech-api/v1) has been down since before the new year. As you can see it throws a "503 Service Temporarily Unavailable" which I thought might be related but it's certainly not fixed. Hope that was helpful, thanks for your time!

@Kaljurand
Copy link
Owner

@Te-M The service that you refer to (labeled as "grammar support" in the Kõnele UI) will probably be deprecated, because the corresponding server is difficult to maintain. For most tasks it is better use the "fast recognition" service (with the URL ws://bark.phon.ioc.ee:82/dev/duplex-speech-api/ws/speech) instead. The only feature of the "grammar support" service that is not provided by the "fast recognition" service is support for uploading and using GF or JSGF grammars (to replace the LM). Are you relying on this feature?

@Te-M
Copy link

Te-M commented Jan 11, 2019

Hmm, probably just an outdated tutorial. Thanks for your help!

@Kaljurand
Copy link
Owner

Kaljurand commented Jan 11, 2019 via email

@mrts mrts reopened this Apr 28, 2019
@mrts
Copy link
Author

mrts commented Apr 28, 2019

Hello! Same error again, I hope it is an easy, hassle free fix this time too.

Heartfelt thanks for your good work once again!

@Kaljurand Kaljurand pinned this issue Apr 28, 2019
@Kaljurand Kaljurand changed the title 'Server not reachable' as of December 28 'Server not reachable'; (re)open this issue if the Kõnele default server is not working Apr 28, 2019
@Kaljurand
Copy link
Owner

Thanks for reporting. I can confirm that the server is down at least since yesterday evening. The issue is being investigated. For some cases the work-around is to set up and use your own server, see https://hub.docker.com/r/alumae/docker-konele/ and http://kaljurand.github.io/K6nele/docs/et/user_guide.html#tuvastusserver-koduv%C3%B5rgus

@sheminnyoka
Copy link

Is the server down issue will be solved soon

@alumae
Copy link

alumae commented Apr 29, 2019

Works again.

@mrts
Copy link
Author

mrts commented Apr 29, 2019

I can confirm that it works - thank you!

@mrts mrts closed this as completed Apr 29, 2019
@Kaljurand Kaljurand changed the title 'Server not reachable'; (re)open this issue if the Kõnele default server is not working 'Server not reachable'; (re)open if Kõnele default server not working Apr 29, 2019
@Kaljurand Kaljurand reopened this Jun 20, 2020
@mrts
Copy link
Author

mrts commented Jun 20, 2020

I see that you already noticed that the service is down, hope it is an easy fix yet again!

@mrts
Copy link
Author

mrts commented Jun 20, 2020

Works again, thank you for a quick fix!

@mrts
Copy link
Author

mrts commented Jun 23, 2020

Hm, seems that the service is down again after such a short time. Is there a systemic issue perhaps?

@Kaljurand Kaljurand reopened this Jun 23, 2020
@BalooRJ1
Copy link

Hello,

The default server for English is once again no longer working...I am getting the same error "Server not reachable." Is there any way to fix this? Thank you.

@Kaljurand
Copy link
Owner

@BalooRJ1 sorry for the delay, can you clarify what do you mean by "the default server for English". As far as I can see, Kõnele does not come with any server for English...

@BalooRJ1
Copy link

BalooRJ1 commented Jul 27, 2020

Thanks @Kaljurand. The default server URL ws://bark.phon.ioc.ee:82/dev/duplex-speech-api/ws/speech and also http://bark.phon.ioc.ee/speech-api/v1/recognize bring back errors saying [server not reachable.] Now I'm not sure if this is because I have it set to English as the default language or if the servers actually are not functioning at all.

@Kaljurand
Copy link
Owner

@BalooRJ1 again, sorry for the delay...

http://bark.phon.ioc.ee/speech-api/v1/recognize is not maintained anymore, so it is expected that it does not work. The corresponding menu option will be removed from Kõnele at some point.

The "fast service" URL (ws://...) should work, but it only supports Estonian. I still don't understand what did you set to English? Can you provide a screenshot?

@khlsvr
Copy link

khlsvr commented Feb 18, 2021

The current situation on the english server is same as in the previous message I guess? Anyone happen to know a version understanding finnish?

I installed the vosk android demo (link below), and I am able to use it for speech to text in its app. I wonder if I can somehow incorporate that into the IME, perhaps using the k6nele app.
https://github.com/alphacep/vosk-android-demo/releases

@Kaljurand
Copy link
Owner

Answers to your questions:

@nshmyrev
Copy link

talk to the makers of vosk-android-demo, all they have to do is implement the SpeechRecognizer API (as described in

I was hoping for your help @Kaljurand ;)

@Kaljurand
Copy link
Owner

@nshmyrev what help would be needed? It's just about implementing a standard Android API (+ ideally a few Kõnele-specific EXTRAs). In general, Kõnele is agnostic to what backend is being used. See also the related request #78

@nshmyrev
Copy link

Nevermind, we'll get some student to do this ;)

@khlsvr
Copy link

khlsvr commented Feb 20, 2021

I'm happy to see that this is being considered!

So what I understood is that the plan is to for example fork the K6nele-service project and then replace the code in it that currently connects to a remote kaldi-gstreamer-server to the code of the vosk-android-demo or perhaps some parts of it adding some API functionality to be able to "attach" it to this main k6nele app?

@Kaljurand
Copy link
Owner

Kaljurand commented Feb 20, 2021

@khlsvr yes, that would be the way to do it. The app needs to implement the service and declare it in the manifest (see e.g. https://github.com/Kaljurand/K6nele-service/blob/8a5ad02e19eb943736e02b44131a2c2bb34351b0/app/src/main/AndroidManifest.xml#L75), then Kõnele (or any other app) can find it.

@nshmyrev
Copy link

Also #68

@mrts
Copy link
Author

mrts commented Jun 28, 2023

Getting 'server does not work' on Android 13, is the service down?
Screenshot_20230628-125256

@Kaljurand
Copy link
Owner

Issue has been resolved

@mrts
Copy link
Author

mrts commented Jun 28, 2023

Works like a charm again, thanks a lot!

@Kaljurand Kaljurand reopened this Aug 16, 2023
@mrts
Copy link
Author

mrts commented Jan 3, 2024

Happy new year and many thanks for this great service once again! Getting "serveriga puudub ühendus" again.

@Kaljurand Kaljurand reopened this Jan 4, 2024
@Kaljurand
Copy link
Owner

Meanwhile fixed.

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

No branches or pull requests

8 participants