# "Unable to connect to X server"

**URL:** <https://community.tempest.earth/t/unable-to-connect-to-x-server/22798>\
**Category:** WeatherFlow PiConsole\
**Created:** [November 1, 2023, 1:42am UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798 "2023-11-01T01:42:21Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 1, 2023, 1:42am UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/1 "2023-11-01T01:42:21Z")

</div>

Installed wfpiconsole onto a new RaspPi 4B running 32 bit. Install went good, but after I enter personal info for station, I get the error “Unable to connect to X server”.

```auto
[INFO] [Image] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffp yplayer ignored)
[INFO] [Window] Provider: sdl2
[INFO] [GL] Using the "OpenGL ES 2" graphics system
[INFO] [GL] Backend used <sdl2>
[INFO] [GL] OpenGL version <b'3.1 Mesa 23.2.1-0+rpt2'>
[INFO] [GL] OpenGL vendor <b'Broadcom'>
[INFO] [GL] OpenGL renderer <b'V3D 4.2'>
[INFO] [GL] OpenGL parsed version: 3, 1
[INFO] [GL] Shading version <b'1.40'>
[INFO] [GL] Texture max size <4096>
[INFO] [GL] Texture max units <24>
[INFO] [Window] auto add sdl2 input provider
[INFO] [Window] virtual keyboard not allowed, single mode, not docked
[INFO] [Text] Provider: sdl2(['text_pango'] ignored)
[INFO] [GL] NPOT texture support is available
Unable to connect to X server
[INFO] [Base] Start application main loop
[INFO] [Websocket] 2023-10-31 20:31:48 - Opening connection
[INFO] [Websocket] 2023-10-31 20:31:48 - Connection open
[INFO] [Factory] 190 symbols loaded
[INFO] [Image] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffp yplayer ignored)
[INFO] [Window] Provider: sdl2
[INFO] [GL] Using the "OpenGL ES 2" graphics system
[INFO] [GL] Backend used <sdl2>
[INFO] [GL] OpenGL version <b'3.1 Mesa 23.2.1-0+rpt2'>
[INFO] [GL] OpenGL vendor <b'Broadcom'>
[INFO] [GL] OpenGL renderer <b'V3D 4.2'>
[INFO] [GL] OpenGL parsed version: 3, 1
[INFO] [GL] Shading version <b'1.40'>
[INFO] [GL] Texture max size <4096>
[INFO] [GL] Texture max units <24>
[INFO] [Window] auto add sdl2 input provider
[INFO] [Window] virtual keyboard not allowed, single mode, not docked
[INFO] [Text] Provider: sdl2(['text_pango'] ignored)
[INFO] [GL] NPOT texture support is available
Unable to connect to X server
[INFO] [Base] Start application main loop
[INFO] [Websocket] 2023-10-31 20:31:48 - Opening connection
[INFO] [Websocket] 2023-10-31 20:31:48 - Connection open

```

---

<div class="post-metadata">

**Author:** ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Post date:** [November 1, 2023, 2:08am UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/2 "2023-11-01T02:08:23Z")

</div>

Yes folks are periodically getting that failure with the newest raspios on pi4 due to os changes by the rasperrypi folks.

I did a lot of cycles testing 64bit on a pi4 reflashing and reinstalling and changing nothing and it went away for some reason and the last few flash/reinstall tests all worked. No clue why it failed multiple times nor worked multiple times after that.

Try going back to the legacy debian-11 version at [Operating system images – Raspberry Pi](https://www.raspberrypi.com/software/operating-systems/) with the May 3rd 2023 dates. It’ll take a little longer to install probably but should be more stable.

---

<div class="post-metadata">

**Author:** ![eric](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/eric/32/13553_2.png) [@eric](https://community.tempest.earth/u/eric)\
**Post date:** [November 1, 2023, 8:48am UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/3 "2023-11-01T08:48:29Z")

</div>

latest OS Bookworm ?

---

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 1, 2023, 1:13pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/4 "2023-11-01T13:13:59Z")

</div>

Yes, just looked it up, it is the Bookworm OS. I will have to play with it some more and probably try what Vince suggested, downgrade to the older OS from May.

---

<div class="post-metadata">

**Author:** ![rrmtx07](https://avatars.discourse-cdn.com/v4/letter/r/fbc32d/32.png) [@rrmtx07](https://community.tempest.earth/u/rrmtx07)\
**Post date:** [November 1, 2023, 3:42pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/5 "2023-11-01T15:42:22Z")

</div>

Yeah. Looks like it. May just need to reimage theSD card and start clean.

---

<div class="post-metadata">

**Author:** ![peter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/peter/32/1365_2.png) [@peter](https://community.tempest.earth/u/peter)\
**Post date:** [November 1, 2023, 3:46pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/6 "2023-11-01T15:46:39Z")

</div>

What is really strange about this error is how it doesn’t affect everyone. I have just installed 32 bit Bookworm onto my Pi 4, and I have no issues at all 🤔

---

<div class="post-metadata">

**Author:** ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Post date:** [November 1, 2023, 7:06pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/7 "2023-11-01T19:06:18Z")

</div>

I had repeated failures doing reflash-reinstall tests and then it went away just as magically as it appeared. No explanation. Last four or five tries with 64bit it worked fine.

---

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 1, 2023, 7:57pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/8 "2023-11-01T19:57:35Z")

</div>

So the wfpiconsole will work under the 64 bit environment?

---

<div class="post-metadata">

**Author:** ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Post date:** [November 1, 2023, 8:31pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/9 "2023-11-01T20:31:05Z")

</div>

Always use the versions @peter recommends and supports. I’m helping him test his new stuff and how it works (or might not be quite there) for the new raspios. They did change a lot for pi4 users at the os level when they moved to debian12.

---

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 2, 2023, 11:25pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/10 "2023-11-02T23:25:21Z")

</div>

I am at a loss what to try next. I tried using the May version that was recommended, flashed several times and also reflashed several times the current version and keep coming up with the same error of “Server X”. I have also tried using different SD cards and even a flash drive with same results.  
Anyone have any other ideas on cause? Could this be a RaspPi hardware issue? like I said, brand new, just bought

---

<div class="post-metadata">

**Author:** ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Post date:** [November 2, 2023, 11:29pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/11 "2023-11-02T23:29:41Z")

</div>

The new os uses Wayland for the windowing subsystem on pi4 so that is a major difference. That said, at this point my available pi3+ (32bit) and pi4 (32bit and 64bit) both install and run ok with the 10-10-2023 new os.

I can not explain why I had the unable-to-connect problem for a few attempts on the pi4 previously because now it works every time I do the reflash/install tests.

---

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 3, 2023, 12:01am UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/12 "2023-11-03T00:01:22Z")

</div>

I will try the 64 bit. Will be awhile before I can get to it again, will update when I do.

Thanks for your help

---

<div class="post-metadata">

**Author:** ![fritz614](https://avatars.discourse-cdn.com/v4/letter/f/f05b48/32.png) [@fritz614](https://community.tempest.earth/u/fritz614)\
**Post date:** [November 4, 2023, 1:48pm UTC](https://community.tempest.earth/t/unable-to-connect-to-x-server/22798/13 "2023-11-04T13:48:08Z")

</div>

Well, I was able to get it to work with the 32 bit OS. I just had an odd feeling that the monitor I had the RaspPi connect to was causing this issue, so before I installed wfpiconsole, I disconnected to monitor, rebooted and used vnc to remote into it (probably would have worked with SSH also). I then did system updates and rebooted again, remoted in and installed wfpiconsole, rebooted, but this time I connected monitor back up to it and it is now working!  
This is a fairly new monitor, 2020, LG. I am thinking that something with the Mini HDMI\>HDMI\>HDMI to monitor was somehow causing this issue.
