[bug]: Trouble with local development steup

[Rounak-stha]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

I can't seem to get the app local running instance. As far as I can tell, after all the containers are running, we should get the results at locahost but I get a Bad Gateway 502 error.

Steps to reproduce

I've followed the guide here: https://github.com/makeplane/plane/blob/c829b52c0f45ba8b86ab27733547161b3825d04d/CONTRIBUTING.md

All the containers are successfully running.

Environment

Deploy preview

Browser

Mozilla Firefox

Variant

Local

Version

v0.21.0-dev

[semyonf]

Same, except I'm able to open base URL, and then I'm getting HTTP 504 when I go to /god-mode/

[Rounak-stha]

@semyonf

My cause for this issue was due to the EOF issue in windows. This issue is fixed.
Maybe there's some other reason behind your issue

[FinalExiledDuck]

I am also getting the same issue when I attempt to create a new instance I am getting a 502. Here are some of the logs I am getting:

2024-09-12 23:06:44 2024/09/13 03:06:44 [error] 8#8: *577 connect() failed (113: Host is unreachable) while connecting to upstream, client: 192.168.65.1, server: , request: "GET / HTTP/1.1", upstream: "http://172.22.0.10:3000/", host: "localhost", referrer: "http://localhost/god-mode/authentication/"
2024-09-12 23:06:44 192.168.65.1 - - [13/Sep/2024:03:06:44 +0000] "GET / HTTP/1.1" 502 559 "http://localhost/god-mode/authentication/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36"
2024-09-12 23:06:44 192.168.65.1 - - [13/Sep/2024:03:06:44 +0000] "GET /god-mode/_next/webpack-hmr HTTP/1.1" 101 347 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36"
2024-09-12 23:06:47 2024/09/13 03:06:47 [error] 8#8: *577 connect() failed (113: Host is unreachable) while connecting to upstream, client: 192.168.65.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.22.0.10:3000/favicon.ico", host: "localhost", referrer: "http://localhost/"
2024-09-12 23:06:47 192.168.65.1 - - [13/Sep/2024:03:06:47 +0000] "GET /favicon.ico HTTP/1.1" 502 559 "http://localhost/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36"

It seems like my local instance is attempting to communicate with http://172.22.0.10:3000 but is timing out.

[FinalExiledDuck]

I found after doing some investigation that plane-web-1 container had the following network settings:

	"NetworkSettings": {
		"Bridge": "",
		"SandboxID": "6af7133215f1b6847f61c9e9fa226d80a404fd86cc274e3bf9d6cd0cd0b8f966",
		"SandboxKey": "/var/run/docker/netns/6af7133215f1",
		"Ports": {
			"3000/tcp": null
		},
		"HairpinMode": false,
		"LinkLocalIPv6Address": "",
		"LinkLocalIPv6PrefixLen": 0,
		"SecondaryIPAddresses": null,
		"SecondaryIPv6Addresses": null,
		"EndpointID": "",
		"Gateway": "",
		"GlobalIPv6Address": "",
		"GlobalIPv6PrefixLen": 0,
		"IPAddress": "",
		"IPPrefixLen": 0,
		"IPv6Gateway": "",
		"MacAddress": "",
		"Networks": {
			"plane_dev_env": {
				"IPAMConfig": null,
				"Links": null,
				"Aliases": [
					"plane-web-1",
					"web"
				],
				"MacAddress": "02:42:ac:1c:00:07",
				"NetworkID": "6eead13a344d0047c7bcf7672678b354a88d26814775aa26f2c5061ed4d61ec2",
				"EndpointID": "e51db712ffc8009d7b1c89c00fb0b7f46024dd1b4f917907c2932a7237259a09",
				"Gateway": "172.28.0.1",
				"IPAddress": "172.28.0.7",
				"IPPrefixLen": 16,
				"IPv6Gateway": "",
				"GlobalIPv6Address": "",
				"GlobalIPv6PrefixLen": 0,
				"DriverOpts": null,
				"DNSNames": [
					"plane-web-1",
					"web",
					"5667c4f7b8c1"
				]
			}
		}
	}

I can see that the IPAddress for the web container is 172.28.0.7 but the proxy thinks it is 172.23.0.10.

For now I have fixed this locally by running docker-compose restart proxy

Still unsure why the proxy gets into this state, so more investigating would be necessary to rectify this.

[pushya22]

hi @Rounak-stha hope the issue is resolved, Please re-open the issue still persists.