I am facing exacly the same problem as described here: Conecting to the mycroft web client. I read this whole discussion but I can’t solve my problem. Mayby I don’t understand something or there is other solution?
Thank You!
Hi there,
Welcome to the Community 
Can I clarify, you are trying to setup the Mycroft Web Client from @jcasoft and receiving the 404 response?
I’m not familiar with this package so can’t provide too much assistance, however I know the author still drops by the forums every now and then.
Is your Mycroft instance receiving the GET requests? There should be logs being written to /var/log/mycroft/bus.log
Hi, thank you for reply!
Forget about my last post and I will start from the beginning. I saw this error for the first time after I opened port 8181 in the browser to check what’s on it and I found this:
Traceback (most recent call last):
File “/home/abc/mycroft-core/.venv/lib/python3.6/site-packages/tornado/web.py”, line 1390, in _execute
result = self.prepare()
File “/home/franciszek/mycroft-core/.venv/lib/python3.6/site-packages/tornado/web.py”, line 2103, in prepare
raise HTTPError(self._status_code)
tornado.web.HTTPError: HTTP 404: Not Found
I tought “this is not good” and without any reaserch I assumed that this need to be some type of web-client that is broken. Before comming accros this message-bus documentation: https://mycroft.ai/documentation/message-bus/, I found this: Conecting to the mycroft web client and relised that web-client is not installed and I have to do it manually, but I did not succed due to the outdated README.
Long-story short, after posting my last post I succed today in installing other web-client by the same author: https://github.com/jcasoft/Web-Chat-Client-for-Mycroft I needed to perform few modifications to get it working because it also is outdated. I will post this modyfications on issues of WebChatClient GitHub.
My final question is: Is it normall and expected to have this error after fresh installation?
I hope my english is good enough to understand me.
Thank You!
1 Like
Hey glad it’s working and thanks for contributing your findings back to the repo.
If you setup a fresh mycroft-core installation without changing anything you should not get a 404. Were you getting this before you changed anything?
It was a fresh installation. When I ran “mycroft-start debug” I noticed that app was using port 8181. It wasn’t my first mycroft build. Before I build it few times but I always mess up something and rebuild it again (you know, I am learning). Before new build I removed: /opt/mycroft, ~/mycroft-core, ~/.minecroft and /usr/share/mycroft-core
I am running manjaro-cinnamon on Lenovo legion Y530
I confirm the same issue on a fresh picroft buster.
I also get the same error on fresh installations. I tried to install mycroft on docker, picroft, in a vm and android and it always gives me a error 404
After failing to install on Docker (it wouldn’t connect to pulseaudio), I turned to a baremetal install and I’m getting a 404 when following this documentation:
I’m also seeing this running the Docker container on Windows 10.
Traceback (most recent call last):
File "/opt/mycroft/.venv/lib/python3.6/site-packages/tornado/web.py", line 1681, in _execute
result = self.prepare()
File "/opt/mycroft/.venv/lib/python3.6/site-packages/tornado/web.py", line 2430, in prepare
raise HTTPError(self._status_code)
tornado.web.HTTPError: HTTP 404: Not Found
I’m launching the container without the PULSE AUDIO params because I don’t have those, and was hoping to interact at least through the command line. I’m using this launch command in a Windows CMD prompt with admin access:
docker run -d -v "X:\Users\User1\Documents\mycroft":/root/.mycroft -p 8181:8181 --name mycroft mycroftai/docker-mycroft
I then confirm it’s running with:
>docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
baa556ed515d mycroftai/docker-mycroft "/bin/sh -c \"/opt/my…" 18 minutes ago Up 18 minutes 0.0.0.0:8181->8181/tcp mycroft
After realizing I needed to pair it to get full access, I then went back in the logs, found the pairing code, and added it from account.mycroft.ai, but this doesn’t change the behavior.
In the logs I see a lot of connection_refused:
2024-01-13 00:15:36 Starting all mycroft-core services
2024-01-13 00:15:36 Initializing...
2024-01-13 00:15:36 Starting background service bus
2024-01-13 00:15:36 CAUTION: The Mycroft bus is an open websocket with no built-in security
2024-01-13 00:15:36 measures. You are responsible for protecting the local port
2024-01-13 00:15:36 8181 with a firewall as appropriate.
2024-01-13 00:15:36 Starting background service skills
2024-01-13 00:15:36 Starting background service audio
2024-01-13 00:15:36 Starting background service voice
2024-01-13 00:15:36 Starting background service enclosure
2024-01-13 00:15:36 ==> /var/log/mycroft/audio.log <==
2024-01-13 00:15:36 pa_context_connect() failed: Connection refused
2024-01-13 00:15:36 2024-01-13 05:56:23.670 | INFO | 25 | mycroft.tts.tts:_get_sentence_from_cache:511 | Found 8a5bc5c8d77c7f3a98acf821d96e0601.wav in TTS cache
2024-01-13 00:15:36 Connection failure: Connection refused
2024-01-13 00:15:36 pa_context_connect() failed: Connection refused
2024-01-13 00:15:36 2024-01-13 05:56:34.097 | INFO | 25 | mycroft.audio.speech:mute_and_speak:120 | Speak: Now I am ready for use.
2024-01-13 00:15:36 2024-01-13 05:56:34.206 | INFO | 25 | mycroft.audio.speech:mute_and_speak:120 | Speak: Try asking me things like "hey mycroft, what's the weather", "hey mycroft, tell me about abraham lincoln", or "hey mycroft, play the news".
2024-01-13 00:15:36 Connection failure: Connection refused
2024-01-13 00:15:36 pa_context_connect() failed: Connection refused
2024-01-13 00:15:36 Connection failure: Connection refused
2024-01-13 00:15:36 pa_context_connect() failed: Connection refused
2024-01-13 00:15:36
All of this is pretty frustrating since I though the point of Docker containers (which, to be fair, I’m fairly new with) is to avoid exactly this kind of local-installation dependent error.
I saw some other threads where people were having this problem and somehow solved it by installing PULSE AUDIO, but that’s not an option on Windows, or, at least is very unlikely to solve the problem.
mycroft is dead, OVOS and Neon are the surviving forks that carry the torch
we have docker containers for OVOS and awesome docs by @goldyfruit
2 Likes
This points to a different website, but it looks like the same command as on Goldyfruit’s github repo. I just tried it, but it seems to have failed in the same place. :((
...
ovos_installer : Flush handlers wireless (uninstall) ------------------------------------------------------------------------------- 0.05s
ovos_installer : Flush handlers udev (uninstall) ----------------------------------------------------------------------------------- 0.05s
ovos_installer : Flush handlers sound ---------------------------------------------------------------------------------------------- 0.04s
➤ Unable to finalize the process, please check /var/log/ovos-installer.log for more details.
Why would it fail right there? Any help will be appreciated.
1 Like
I believe this hs been fixed. Please try the installer again
1 Like
Indeed, it is fixed.
Nope :(( I got the same results.
That is very strange, it fixed the issue for the two others on Matrix.
Did you re-run the full command?
sh -c "curl -s https://raw.githubusercontent.com/OpenVoiceOS/ovos-installer/main/installer.sh -o installer.sh && chmod +x installer.sh && sudo ./installer.sh && rm installer.sh"
Yes, many times :). I just ran it on both of my RasPi 4bs with Ubuntu Desktop 22.04 installed. Both failed on:
ovos_installer : Flush handlers sound
Is there a verbose mode to get more diagnostics?
Could you please share the log /var/log/ovos-installer.log?
It was too large to paste, and not the right file type for “upload”. So I checked it in here: https://github.com/mike99mac/minimy-mike99mac/blob/main/doc/ovos-installer.log
Could you please share docker inspect ovos_phal output?
$ docker inspect ovos_phal
[]
Error: No such object: ovos_phal