Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
See original GitHub issueI’m seeing this error in the github actions logs very often:
[2287:0204/174506.688134:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
For example here the error is logged 58 times

Fortunately this is not a critical error, as all the tests are still passing, it’s just a bit noisy 🙂
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
wsl 2 - Getting “Failed to connect to the bus: Could not parse ...
... to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX...
Read more >Running Cypress on WSL - Stack Overflow
[14874:0408/102328.150664:ERROR:bus.cc(392)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of ...
Read more >Getting multiple errors when trying to open a browser in kali ...
... to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX...
Read more >cypress-io/cypress - Gitter
... Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on...
Read more >jupyter notebook problem with 8,3 - Google Groups
[53973:54212:0808/163222.855277:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I get the same thing in my tests, love to know the answer…
Sorry for the link spam here. I had thought this issue could address my problem, but it is not.