Is there still a way to make netmaker work with ca...
# netmakerr
ripe-fireman-83813
10/13/2022, 6:00 PMIs there still a way to make netmaker work with caddy? Before upgrading to 16.x it worked, now my netclients cannot connect to the server, even though I do not relay mq traffic via caddy
j
jolly-london-20127
10/13/2022, 6:12 PMis it an MQ issue?
r
ripe-fireman-83813
10/13/2022, 6:19 PMit appears so, judging from the netclient logs
ripe-fireman-83813
10/13/2022, 6:21 PMthis is a part of the mq log:
Copy code
2022-10-12T21:02:09.832776958Z 1665608529: New connection from <corretnetclinetplublicip>:52154 on port 8883.
2022-10-12T21:02:09.832837373Z 1665608529: Client <unknown> disconnected due to protocol error. Copy code
[localport.go-47] UpdateLocalListenPort(): could not publish local port change connection timeout
[mqpublish.go-252] publish(): could not connect to broker at broker.mydomain.tld:8883
[mqpublish.go-149] Hello(): Network: <mynetwork> error publishing ping, connection timeoutb
bored-island-21407
10/13/2022, 6:23 PMjust checking ::: your netmaker server and netclient node are running the same version.
bored-island-21407
10/13/2022, 6:23 PMon the client run
netclient pull -n <network name> -vvvvr
ripe-fireman-83813
10/13/2022, 6:26 PMthis results in:
Copy code
netclient pull -n mynet-net -vvvv
[netclient] 2022-10-13 18:26:00 [common.go-391] informPortChange(): network: mynet-net node hass is using port 51821
[netclient] 2022-10-13 18:26:03 [common.go-165] InitWireguard(): waiting for interface...
[netclient] 2022-10-13 18:26:03 [common.go-193] InitWireguard(): interface ready - netclient.. ENGAGE
[netclient] 2022-10-13 18:26:03 [commands.go-110] Pull(): pulled network config for mynet-net
[netclient] 2022-10-13 18:26:03 [commands.go-116] Pull(): reset network mynet-net and peer configsripe-fireman-83813
10/13/2022, 6:29 PMthe netlcient runs in a docker container
ripe-fireman-83813
10/13/2022, 6:29 PM16.1
j
jolly-london-20127
10/13/2022, 6:37 PMwhich version did you upgrade from?
r
ripe-fireman-83813
10/13/2022, 6:40 PM16.0
ripe-fireman-83813
10/13/2022, 6:40 PMi started fresh with the docker image, and deleted the host mounted volume holding the old config
ripe-fireman-83813
10/13/2022, 6:46 PMwith 16.0 it seemed to stop working
j
jolly-london-20127
10/13/2022, 6:51 PMthere was a change in 0.16.1 that will definitely affect MQ connectivity, but nothing in 0.16.0 should affect it.
jolly-london-20127
10/13/2022, 6:52 PMwhich public port are you using for MQ?
r
ripe-fireman-83813
10/13/2022, 7:09 PM8883
ripe-fireman-83813
10/13/2022, 7:09 PMsince I think 443 would go by caddy and caddy won't forward raw tcp
ripe-fireman-83813
10/13/2022, 7:10 PM8883 is opened on the server via ufw
ripe-fireman-83813
10/13/2022, 7:13 PMhere's a full log with a freshly started container:
ripe-fireman-83813
10/13/2022, 7:20 PMhmm now it seems to work
j
jolly-london-20127
10/16/2022, 4:59 PMsometimes you just need to wait a few minutes for clients to reset themselves
9 Views