Hi Alex,
Am 29.05.25 um 17:05 schrieb Alexander Wiegand:
the netstat -ant does not really work because it immediately finishes before I am able to start the connection in the X2Go client. I have no experience in netstat. Is there any way to run it continuously so that I can see what is happening?
If you run it immediately after your connection attempt ends, you should still see "lingering" traces of the connection, e.g. an entry that says "TIME_WAIT" or "CLOSE_WAIT" in the last column (assuming you have LANG=C set; other locale settings might change that to a different text).
You could also run something like
watch -n 1 --diff "netstat -ant | grep 192\.168\.178\.71"
which would only output lines matching the IP from your screenshot, update every second, and highlight any changes to the previous output.
I have now connected to the local lan with Wireguard and used the IP address of the host in the local lan. Unfortunately still unchanged, I do not see anything in the nginx logs. Here is a screenshot of my configuration:
Can you spot any mistakes in my configuration?
Assuming 192.168.178.71 really is the IP of your nginx proxy, it looks okay.
Could you run
nc -l -p 4223
in a terminal on the proxy, then change the port in X2GoClient from 80 to 4223 and try to connect?
If that results in some sort of output on the nc command line, it would show that you can indeed connect from X2GoClient to the proxy. That would hint at nginx doing things not the way squid does them.
Are you sure you don't have something else running on the proxy that already occupies port 80? Another nginx instance, maybe? Could you try running the particular nginx instance you want to use for proxying on port 8080, 3128, or 4223 instead, change your X2GoClient config accordingly, and see if that changes anything?
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243