Front End Nodejs Status "Show Output" terminal blank white screen

miacias · September 13, 2024, 11:55pm

What issue or error are you experiencing?

The Show Output window is a blank white screen with no text.

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Open Local. Click Start Site on any given site. Then once it is spun up, click Show Output to view a blank white window. This also occurred on a previous version of Local, not just the latest. I tried updating with no luck.

System Details

Local Version: Version 9.0.5+6706
Operating System (OS) and OS version: macOS Ventura v13.6.1

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-lightning-verbose.log (357.1 KB)
local-lightning.log (859.6 KB)
local-lightning1.log (1016.9 KB)
local-lightning2.log (1024.0 KB)
local-lightning3.log (1016.9 KB)
local-lightning4.log (1023.3 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

Nick-B · September 17, 2024, 1:24pm

Hi @miacias

Do you recall if there was a specific version of Local where this worked normally for you?

miacias · September 17, 2024, 4:40pm

Hi Nick! I can say that I used this feature previously, but I’m not sure which version I was using when it worked. I believe I had Local 8.3.2, and I want to say that it was working then and then stopped, but it may be an even earlier version where this was working as intended. I wish I knew!

Nick-B · September 17, 2024, 5:28pm

If you’d be willing to test @miacias you could try downgrading to 8.3.2 or older and see if that does the trick. It also might provide you with a workaround if you need.

miacias · September 17, 2024, 5:40pm

I’ll give that a try and report back, thank you! Do you think this could be a centralized issue with my workspace or a potential bug?

Nick-B · September 18, 2024, 1:22pm

Hi @miacias! Following up here to let you know that myself and one of our Devs were able to replicate and confirm this is a bug. We don’t have an ETA on a fix for this, so for now your best bet will be to try and roll back to a version where that works for you again using the resources I shared above.

Thank you for raising this to us!

miacias · September 18, 2024, 4:22pm

Sorry for the trouble! I’m glad I could help find it at least. Thanks for everything!

system · September 20, 2024, 4:23am

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.

miacias · December 20, 2024, 2:57am

I was afraid to follow Nick’s advice back in September because I didn’t want to somehow lose the precious environment I was working on. I just tried 8.3.2 and 8.3.1 as suggested, and the white terminal box persists. What can I do?

Original bug post here:

Nick-B · December 20, 2024, 2:10pm

Hi @miacias - Apologies that this closed I’ve reopened the original bug object here since it’s still ongoing. We aren’t quite sure when this started, I was just going off your comment when you mentioned that you thought it might have worked in 8.3.2. Can you try downgrading any further?

miacias · December 20, 2024, 4:37pm

Hi Nick, thanks for that! Is there a public GitHub repo for this app? I think I found Local but wasn’t able to identify which repo to open an Issue on. I don’t remember which version I was using initially. Here’s my results from testing previous versions one at a time:

Testing Show Output feature within Local WP versions

8.3.2 > white box

8.3.1 > white box

8.2.1 > white box

8.2.0 > white box

8.1.0 > white box

8.0.2 > white box

8.0.1 > Show Output will not open at all

8.0.0 > white box

7.2.1 > Show Output will not open at all

7.2.0 > Show Output will not open at all

7.1.2 > Show Output will not open at all

7.1.0 > Show Output will not open at all

7.0.2 > Show Output will not open at all

7.0.1 > white box

7.0.0 > Show Output is unavailable (no button). cannot install WPE Atlas (error message: “Atlas: Headless WP requires Local ^6.5.2”

6.7.2 > white box
6.7.1 > white box

6.7.0 > white box

6.6.1 > white box

6.6.0 > white box

6.5.2 > white box

6.5.1 > not compatible with WPE Atlas plugin

After clicking “upgrade to latest” from v6.5.1, my computer partially crashed (black screen, then gray loading screen). Based on these results, I remember having modified the nginx files but cannot remember if I undid the changes. Perhaps that could be a catalyst for the issue since none of the previous versions resolved the Show Output box from either whiting out or being wholly inaccessible. What are your thoughts on next steps?

site.conf.hbs file:

upstream php {
  {{#each fastcgi_servers}}
  server {{this}};
  {{/each}}
}

server {
	listen 127.0.0.1:{{port}};
	listen [::1]:{{port}};
    root   "{{root}}";

    index index.php index.html index.htm;

    #
    # Generic restrictions for things like PHP files in uploads
    #
	include includes/restrictions.conf;

    #
	# Gzip rules
	#
	include includes/gzip.conf;

    #
	# WordPress Rules
	#
    {{#unless site.multiSite}}
    include includes/wordpress-single.conf;
    {{else}}
    include includes/wordpress-multi.conf;
    {{/unless}}

	#
	# Forward 404's to WordPress
	#
	error_page 404 = @wperror;
	location @wperror {
		rewrite ^/(.*)$ /index.php?q=$1 last;
	}

    #
	# Static file rules
	#
	location ~* \.(?:css|js)$ {
        access_log        off;
        log_not_found     off;
        add_header        Cache-Control "no-cache, public, must-revalidate, proxy-revalidate";
    }

    location ~* \.(?:jpg|jpeg|gif|png|ico|xml)$ {
        access_log        off;
        log_not_found     off;
        expires           5m;
        add_header        Cache-Control "public";
    }

    location ~* \.(?:eot|woff|woff2|ttf|svg|otf) {
        access_log        off;
        log_not_found     off;

        expires           5m;
        add_header        Cache-Control "public";

        # allow CORS requests
        add_header        Access-Control-Allow-Origin *;
    }

    #
    # PHP-FPM
    #
	location ~ \.php$ {
		try_files $uri =404;

		fastcgi_split_path_info ^(.+\.php)(/.+)$;

		fastcgi_param   QUERY_STRING            $query_string;
		fastcgi_param   REQUEST_METHOD          $request_method;
		fastcgi_param   CONTENT_TYPE            $content_type;
		fastcgi_param   CONTENT_LENGTH          $content_length;

		fastcgi_param   SCRIPT_FILENAME         $document_root$fastcgi_script_name;
		fastcgi_param   SCRIPT_NAME             $fastcgi_script_name;
		fastcgi_param   PATH_INFO               $fastcgi_path_info;
		fastcgi_param   PATH_TRANSLATED         $document_root$fastcgi_path_info;
		fastcgi_param   REQUEST_URI             $request_uri;
		fastcgi_param   DOCUMENT_URI            $document_uri;
		fastcgi_param   DOCUMENT_ROOT           $document_root;
		fastcgi_param   SERVER_PROTOCOL         $server_protocol;

		fastcgi_param   GATEWAY_INTERFACE       CGI/1.1;
		fastcgi_param   SERVER_SOFTWARE         nginx/$nginx_version;

		fastcgi_param   REMOTE_ADDR             $remote_addr;
		fastcgi_param   REMOTE_PORT             $remote_port;
		fastcgi_param   SERVER_ADDR             $server_addr;
		fastcgi_param   SERVER_PORT             $server_port;
		fastcgi_param   SERVER_NAME             $host;

		fastcgi_param   HTTPS                   $fastcgi_https;

		fastcgi_param   REDIRECT_STATUS         200;

		fastcgi_index index.php;
		fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

		fastcgi_pass php;
		fastcgi_buffer_size      64k;
		fastcgi_buffers          32 32k;
		fastcgi_read_timeout	 1200s;

		proxy_buffer_size        64k;
		proxy_buffers            32 32k;
		proxy_busy_buffers_size  256k;
	}
}

pjwilson1977 · December 22, 2024, 1:26am

Hi All,

Please note that I’m also experiencing the same issue on MacOS and PC using the latest release version 9.1.1
And from the last response from Miacias, it appears that downgrading is not a viable solution.
I wanted to provide this information and ensure that I get updates from this thread should a solution for th bug become available.
Thanks

miacias · December 22, 2024, 3:02pm

Hi PJ, could you clarify which version you were working with previously? For the life of me, I’m not sure which version I was on back when this feature was available. Have you tried uninstalling and reinstalling? My efforts were on MacOS and followed the Local docs instruction to use the “Replace” option rather than remove then reinstall a previous version from fresh. If you have tested that out already, did you have a different experience?

Nick-B · December 23, 2024, 3:06pm

Thank you for your patience and communication here @miacias and @pjwilson1977

Our Local team does have a bug filed for this issue but I don’t have any updates to provide at this time. As far as a working version for an alternative, it seems like your testing was pretty extensive already @miacias, but I’ll circle back with our Dev team and see what we can find.

pjwilson1977 · December 24, 2024, 12:23am

Hi @miacias,
This is my first leap into a headless setup and wanted to run some experiments quickly. And in the past at work I run an Ubuntu VM and I’m new to using Local WP.
So prior to this current version I was running v8.9.6, if I can recall.
@Nick-B, I really appreciate you providing the update around this issue being logged with your team for fixing.
Thanks

pjwilson1977 · December 30, 2024, 8:23am

Hi @Nick-B
Do you know if there is a way in which using Site Shell, we can stop the original NodeJS terminal and start it up again?
I was thinking this could be a work around to get the output starting to come through. My biggest issue is that I can’t tell if FaustJS & NextJS are working correctly to resolve the correct page template that should be used as per a GraphQL query.
Thanks

nickc · January 7, 2025, 3:42pm

@pjwilson1977 We have a test build of the Atlas add-on that should fix console output.

Would you like to try it and confirm if it works for you?

You can use the latest version of Local, this should work without downgrading.

In Local, stop all sites. Browse to add-ons → installed.
Click the options menu (…) to the right of Atlas: Headless WP, choose “Uninstall” and confirm the uninstall and restart (your existing Atlas sites will not be affected).
Download version 1.7.5 of the add-on.
In Local, browse to add-ons → installed, choose “install from disk”, and select the file you downloaded in step 3.
Activate the add-on and restart Local.

Try starting your Atlas site and checking console output. You should see something like the output below. If this works for you, feel free to let us know and we’ll release the add-on update through the official updater.

nickc · January 8, 2025, 11:22am

We tested some more internally and deployed version 1.7.5 of the Atlas plugin to production.

If anyone sees empty console output, check that your Atlas add-on shows 1.7.5 at Add-ons → Installed.

pjwilson1977 · January 14, 2025, 9:39am

Great work @nickc & @Nick-B
Unfortunately, I got to it late and used the newly deployed update available in Local WP.

Topic		Replies	Views
Local not booting/running Support installation , performance , mac	2	576	October 14, 2022
No Local window displayed MacOS Support	6	172	November 21, 2024
Local Window doesn't open on screen Support	1	461	January 2, 2021
Local runs code that isnt there Support	2	126	April 24, 2024
Head's up! Local's router is having trouble trouble starting Support mac-mojave	6	2365	January 11, 2020

Front End Nodejs Status "Show Output" terminal blank white screen

What issue or error are you experiencing?

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

System Details

Local Logs

Related topics