Public Key missing after upgrading to latest firezone

1

Public key missing on new device created after restarting firezone server.

1 Like
2

Hi @herbertrivera – is this a persistent issue with Firezone 0.6.16? Could you elaborate a little more on the steps required to reproduce this error? Thanks!

3

This has been resolved by restarting firezone couple of times. this version is very stable. No connection issue at all unlike the newer version. The only problem though is the ipv6 even when disabled gets an error “IPv6 address pool is exhausted. Increase network size or remove some devices”. this server has set to disable ipv6 and is using 100.xx.xx.xx/10 CGNAT. Any thoughts Jamil?

4

This issue of missing public key is happening again after upgraded to 0.7.8 all users wont be able to connect until public key is present. Restarted server and did restart docker but not working.

5

Was there any fix or workaround for this? I face this occasionally.

05:58:13.771 erl_level=info application=phoenix domain=elixir file=lib/phoenix/logger.ex function=phoenix_endpoint_start/4 line=217 mfa=Phoenix.Logger.phoenix_endpoint_start/4 module=Phoenix.Logger pid=<0.1472.0> request_id=F-5GBM2OdgNc
4n8AAAKh [info] GET /devices/5e7427d0-70df-4303-afe9
05:58:13.784 erl_level=error application=fz_http domain=elixir file=lib/fz_http_web/views/wireguard_config_view.ex function=render/2 line=17 mfa=FzHttpWeb.WireguardConfigView.render/2 module=FzHttpWeb.WireguardConfigView pid=<0.1472.0> request_id=F-5GBM2OdgNc4n8AAAKh [error] No server public key found! This will break device config generation. Is fz_vpn alive?
05:58:13.785 erl_level=info application=phoenix domain=elixir file=lib/phoenix/logger.ex function=phoenix_endpoint_stop/4 line=231 mfa=Phoenix.Logger.phoenix_endpoint_stop/4 module=Phoenix.Logger pid=<0.1472.0> request_id=F-5GBM2OdgNc4n8AAAKh [info] Sent 200 in 13ms
05:58:14.179 erl_level=info application=phoenix domain=elixir file=lib/phoenix/logger.ex function=phoenix_endpoint_start/4 line=217 mfa=Phoenix.Logger.phoenix_endpoint_start/4 module=Phoenix.Logger pid=<0.1473.0> request_id=F-5GBOXZFOqS_OoAAALx [info] GET /
05:58:14.182 erl_level=info application=phoenix domain=elixir file=lib/phoenix/logger.ex function=phoenix_endpoint_stop/4 line=231 mfa=Phoenix.Logger.phoenix_endpoint_stop/4 module=Phoenix.Logger pid=<0.1473.0> request_id=F-5GBOXZFOqS_OoAAALx [info] Sent 200 in 2ms
05:58:15.157 erl_level=info application=phoenix domain=elixir file=lib/phoenix/logger.ex function=phoenix_socket_connected/4 line=306 mfa=Phoenix.Logger.phoenix_socket_connected/4 module=Phoenix.Logger pid=<0.1475.0> [info] CONNECTED TO Phoenix.LiveView.Socket in 31<C2><B5>s
  Transport: :websocket
  Serializer: Phoenix.Socket.V2.JSONSerializer

The containers seem to be up and running:

sudo docker ps
CONTAINER ID   IMAGE                      COMMAND                  CREATED         STATUS         PORTS                                           NAMES
af98cbe84c8a   firezone/firezone:0.7.36   "/app/bin/server"        3 minutes ago   Up 3 minutes   0.0.0.0:51820->51820/udp, :::51820->51820/udp   firezone-firezone-1
5d588d25a856   postgres:15                "docker-entrypoint.s…"   3 minutes ago   Up 3 minutes   5432/tcp                                        firezone-postgres-1
a77f2d1ee541   caddy:2                    "/bin/sh -c 'cat <<E…"   3 minutes ago   Up 3 minutes                                                   firezone-caddy-1
6

Hi @mzs047 – did you save all the env vars from the previous installation? This can happen if the DATABASE_ENCRYPTION_KEY has changed.

1 Like
7

Thank you, yes the setup is fine, we finally we figured it out, the subnets were conflicting, Firezone’s docker-compose file has the default as 172.25.0.0/24, we had to change it to something else which is different from out network.

Edit: It fails for a new setup, the Pub key is missing from new devices.