GL-XE3000 [beta] - broken Web GUI for Cellular

Hi there :wave:

I just tried some experiments with my XE3000 on FW 0404release4 and … I broke the GL Web GUI.
For testing, I am running 2 SIM cards from Poland in Germany.

First it was not really working, and I had the normal option to choose which card I wanted to activate. After a few minutes, the first card was able to connect successfully - and broke the GUI.

Now the whole “Cellular” GUI element is missing:

Error message in browser console:

Uncaught (in promise) {“req”:{“jsonrpc”:“2.0”,“id”:17,“method”:“call”,“params”:[“vja1DWfoYAFDSZuME78uTU43YPeQzzHN”,“modem”,“get_status”,{}]},“error”:{“message”:“Internal error”,“code”:-32603}}

Error message in error.log

2023/12/14 13:32:21 [error] 4963#0: *342 upstream prematurely closed FastCGI stdout while reading response header from upstream, client: 192.168.176.117, server: , request: “POST /rpc HTTP/1.1”, subrequest: “/cgi-bin/glc”, upstream: “fastcgi://unix:/var/run/fcgiwrap.socket:”, host: “192.168.176.1”, referrer: “https://192.168.176.1/

Funny to say that the connection still works, and my router can connect to the internet. But I can’t choose any SIM anymore nor view Cellular details. This will remain even after a reboot.

Do you need any more information to resolve this bug?

Edit:
Goodcloud is broken for cellular as well:
image

but connection is still working:

That’s insane. SSH into the device & execute

/etc/init.d/fcgiwrap stop; /etc/init.d/fcgiwrap start

… but I have a distinct impression this is something related to the GL GUI, which is served by Nginx/FastCGI, choking by Multi-WAN (GL GUI → Network → Multi-WAN → $interface → [ cog ]). If it is, jacking up all counts by a couple of points & changing the track IPs to Quad9 (9.9.9.9, 149.112.112.112) should greatly help.

I’m guessing but I’ve seen Multi-WAN, left in stock configuration, do a few strange things.

mwan is disabled and even a reboot does not help. :smiling_face_with_tear:

Oh shyte! I didn’t realize you were the OP.

Yeah, I got nuffin. That thing is choking on a RPC call… whatever that may be related to the modem’s get_status. What a mess. Reflashing stock didn’t help?

1 Like

Did not try this yet because I want to give GL the opportunity to find the issue.

I’d dump the full logs then. They’ll probably just end up asking for 'em anyways.

1 Like