Comments (25)
w202mg
commented on May 13, 2024
1
I started to work with Firezone on an empty Debian setup, yes. But now I have also otehr things running. On the mobile I'm using Wireguard app.
First I got this running. I had a typo in the port forwarding and I had to change the endpoint IP in the Wireguard mobile app.
But after I tried to change the endpoint IP to show automatically in the GUI I tried to reconfigure and I faced new error. I tried to purge firezone, delete the directory manually and configure new without changing the default of endpoint (keep it nil). But is still the same... Tried also to install newer Firezone version.
Running handlers:
[2021-10-08T12:02:12+02:00] ERROR: Running exception handlers
Running handlers complete
[2021-10-08T12:02:12+02:00] ERROR: Exception handlers complete
Chef Infra Client failed. 2 resources updated in 01 seconds
[2021-10-08T12:02:12+02:00] FATAL: Stacktrace dumped to /var/opt/firezone/cache/cache/chef-stacktrace.out
[2021-10-08T12:02:12+02:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2021-10-08T12:02:12+02:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[setcap_nft] (firezone::setcap line 34) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '127'
---- Begin output of setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft ----
STDOUT:
STDERR: sh: 1: setcap: not found
---- End output of setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft ----
Ran setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft returned 127
Generated at 2021-10-08 12:02:12 +0200
Mixlib::ShellOut::ShellCommandFailed: execute[setcap_nft] (firezone::setcap line 34) had an error: Mixlib::ShellOut::ShellCo>
---- Begin output of setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft ----
STDOUT:
STDERR: sh: 1: setcap: not found
---- End output of setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft ----
Ran setcap 'cap_net_admin,cap_net_raw+eip' /opt/firezone/embedded/sbin/nft returned 127
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/mixlib-shellout-3.2.5/lib/mixlib/shellout.rb:300:in `invalid!'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/mixlib-shellout-3.2.5/lib/mixlib/shellout.rb:287:in `error!'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/mixlib-shellout-3.2.5/lib/mixlib/shellout/helper.rb:130:in `shell_out_compac>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/mixlib-shellout-3.2.5/lib/mixlib/shellout/helper.rb:54:in `shell_out!'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider/execute.rb:52:in `block (2 levels) in <class:>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/mixin/why_run.rb:51:in `add_action'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider.rb:265:in `converge_by'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider/execute.rb:50:in `block in <class:Execute>'
(eval):2:in `block in action_run'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider.rb:276:in `instance_eval'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider.rb:276:in `compile_and_converge_action'
(eval):2:in `action_run'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/provider.rb:217:in `run_action'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource.rb:599:in `block in run_action'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource.rb:626:in `with_umask'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource.rb:598:in `run_action'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:74:in `run_action'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:108:in `block in run_all_actions'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:108:in `each'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:108:in `run_all_actions'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:132:in `block in converge'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/resource_list.rb:96:in `block in e>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/stepable_iterator.rb:114:in `call_>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/stepable_iterator.rb:103:in `itera>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/stepable_iterator.rb:54:in `each_w>
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/resource_collection/resource_list.rb:94:in `execute_ea>
/opt/firezone/embedded/lib/ruby/2.7.0/forwardable.rb:235:in `execute_each_resource'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/runner.rb:130:in `converge'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/client.rb:687:in `block in converge'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/client.rb:682:in `catch'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/client.rb:682:in `converge'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/client.rb:706:in `converge_and_save'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/client.rb:286:in `run'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/application.rb:305:in `run_with_graceful_exit_option'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/application.rb:281:in `block in run_chef_client'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/local_mode.rb:42:in `with_server_connectivity'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/application.rb:264:in `run_chef_client'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/application/base.rb:337:in `run_application'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-16.14.1/lib/chef/application.rb:67:in `run'
/opt/firezone/embedded/lib/ruby/gems/2.7.0/gems/chef-bin-16.14.1/bin/chef-client:25:in `<top (required)>'
/opt/firezone/embedded/bin/chef-client:23:in `load'
/opt/firezone/embedded/bin/chef-client:23:in `<main>'
from firezone.
w202mg
commented on May 13, 2024
1
Hi. Sorry for the late reply after I used the deinstallation script and configured everything new it was running well. I was also able to change the default endpoint. I can't reall tell you what was the problem because I'm sure I was following the indtructions and just wanted to change the default endpoint.
Now my issue is that after reboot firezone does not start. I tried to reconfigure and to restart, but no result. The is also no listening on 51820. Network adapter is running. Config file is still the same
Any idea?
==> /var/log/firezone/postgresql/current <==
2021-10-11_14:17:44.59263 2021-10-11 14:17:44.592 GMT [17571] LOG: received fast shutdown request
2021-10-11_14:17:44.59460 2021-10-11 14:17:44.594 GMT [17571] LOG: aborting any active transactions
2021-10-11_14:17:44.59540 2021-10-11 14:17:44.595 GMT [17571] LOG: background worker "logical replication launcher" (PID 17578) exited with exit code 1
2021-10-11_14:17:44.59545 2021-10-11 14:17:44.595 GMT [17573] LOG: shutting down
2021-10-11_14:17:44.61981 2021-10-11 14:17:44.619 GMT [17571] LOG: database system is shut down
2021-10-11_14:17:44.65796 2021-10-11 14:17:44.657 GMT [17870] LOG: starting PostgreSQL 13.3 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2021-10-11_14:17:44.65799 2021-10-11 14:17:44.657 GMT [17870] LOG: listening on IPv4 address "127.0.0.1", port 15432
2021-10-11_14:17:44.66018 2021-10-11 14:17:44.660 GMT [17870] LOG: listening on Unix socket "/tmp/.s.PGSQL.15432"
2021-10-11_14:17:44.66322 2021-10-11 14:17:44.663 GMT [17871] LOG: database system was shut down at 2021-10-11 14:17:44 GMT
2021-10-11_14:17:44.66532 2021-10-11 14:17:44.665 GMT [17870] LOG: database system is ready to accept connections
root@debian:/# firezone-ctl status
run: nginx: (pid 17792) 1895s; run: log: (pid 620) 11000s
run: phoenix: (pid 17801) 1894s; run: log: (pid 609) 11000s
run: postgresql: (pid 17870) 1894s; run: log: (pid 604) 11000s
from firezone.
jamilbk
commented on May 13, 2024
Couple questions to help diagnose the issue:
- Did you make any changes to the default
postgresqlconfiguration sections in/etc/firezone/firezone.rb? Could you post the changes here if so? - What's the output of
sudo firezone-ctl statusandsudo firezone-ctl tail postgresql?
The last error is expected and should resolve on its own: https://github.com/firezone/firezone#phoenix-restart-times-out
from firezone.
w202mg
commented on May 13, 2024
@jamilbk
Hi. Thank you for the fast reply!
- Did you make any changes to the default
postgresqlconfiguration sections in/etc/firezone/firezone.rb? Could you post the changes here if so?
Yes. This is what I updated there:
default['firezone']['nginx']['force_ssl'] = true
default['firezone']['ssl']['certificate'] = ' /etc/letsencrypt/live/fire.example.net/fullchain.pem'
default['firezone']['ssl']['certificate_key'] = '/etc/letsencrypt/live/fire.example.net/privkey.pem'
and
default['firezone']['fqdn'] = (node['fqdn'] || node['fire.example.net']).downcase
- What's the output of
sudo firezone-ctl statusandsudo firezone-ctl tail postgresql?
sudo firezone-ctl status
run: nginx: (pid 78229) 2s; run: log: (pid 74749) 2354s
run: phoenix: (pid 77187) 1022s; run: log: (pid 74904) 2350s
run: postgresql: (pid 77254) 1022s; run: log: (pid 74723) 2355s
sudo firezone-ctl tail postgresql
2021-10-05_14:34:37.24279 2021-10-05 14:34:37.242 GMT [74994] LOG: received fast shutdown request
2021-10-05_14:34:37.24919 2021-10-05 14:34:37.249 GMT [74994] LOG: aborting any active transactions
2021-10-05_14:34:37.25075 2021-10-05 14:34:37.250 GMT [74994] LOG: background worker "logical replication launcher" (PID 75001) exited with exit code 1
2021-10-05_14:34:37.25213 2021-10-05 14:34:37.252 GMT [74996] LOG: shutting down
2021-10-05_14:34:37.30548 2021-10-05 14:34:37.305 GMT [74994] LOG: database system is shut down
2021-10-05_14:41:29.67485 2021-10-05 14:41:29.674 GMT [77254] LOG: starting PostgreSQL 13.3 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2021-10-05_14:41:29.67488 2021-10-05 14:41:29.674 GMT [77254] LOG: listening on IPv4 address "127.0.0.1", port 15432
2021-10-05_14:41:29.67757 2021-10-05 14:41:29.677 GMT [77254] LOG: listening on Unix socket "/tmp/.s.PGSQL.15432"
2021-10-05_14:41:29.68124 2021-10-05 14:41:29.681 GMT [77255] LOG: database system was shut down at 2021-10-05 14:34:37 GMT
2021-10-05_14:41:29.68385 2021-10-05 14:41:29.683 GMT [77254] LOG: database system is ready to accept connections
from firezone.
jamilbk
commented on May 13, 2024
Hmmm it seems like Postgresql is running just fine. It looks like you have a space before the /etc in your nginx config, this line:
default['firezone']['ssl']['certificate'] = ' /etc/letsencrypt/live/fire.example.net/fullchain.pem'
Remove that and run another sudo firezone-ctl reconfigure and sudo firezone-ctl create_admin and see if you can connect then.
from firezone.
w202mg
commented on May 13, 2024
Yes, this was it. Thanks a lot! Sorry for taking your time for such a stupid mistake
Also I noted these errors if leaving the default port 51820 where my wireguard is running.
Running handlers:
[2021-10-05T16:23:53+01:00] ERROR: Running exception handlers
Running handlers complete
[2021-10-05T16:23:53+01:00] ERROR: Exception handlers complete
Chef Infra Client failed. 8 resources updated in 02 seconds
[2021-10-05T16:23:53+01:00] FATAL: Stacktrace dumped to /var/opt/firezone/cache/cache/chef-stacktrace.out
[2021-10-05T16:23:53+01:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2021-10-05T16:23:53+01:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[set_listen_port] (firezone::network line 64) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/firezone/embedded/bin/wg set wg-firezone listen-port 51820 ----
STDOUT:
STDERR: Unable to modify interface: Address already in use
---- End output of /opt/firezone/embedded/bin/wg set wg-firezone listen-port 51820 ----
Ran /opt/firezone/embedded/bin/wg set wg-firezone listen-port 51820 returned 1
Goes through only if I change to 51821 for example. But I think this shall stay the Wiregaurd port.
# default['firezone']['wireguard']['port'] = 51820
from firezone.
jamilbk
commented on May 13, 2024
Ah I see. It's likely you have a previous wg-firezone interface that didn't get cleaned up somehow.
Check with sudo ip link and remove it with sudo ip link delete dev wg-firezone and you should be able to use port 51820 again after doing another sudo firezone-ctl to get the interface set back up and configured.
from firezone.
w202mg
commented on May 13, 2024
I had installed and running Wireguard, yes. After executing your commands the reconfiguring and adding the admin run without showing any errors. after restarting I still can't open localhost:1580 and fire.example.net. Any ideas where to look?
The port is opened in ufw and teh redirection is set up (wireguard was running just fine)
Thanks!
from firezone.
jamilbk
commented on May 13, 2024
Check the output of sudo firezone-ctl tail which will show log output for all the services.
By default, you should be able to reach the Firezone ui on port tcp/443, https://fire.example.net so make sure that's open. Firezone does modify the host firewall mostly to add NAT/masquerading, which may (or may not) conflict with your ufw rules.
You can view these rules using the bundled nftables userspace utility:
/opt/firezone/embedded/sbin/nft list ruleset
If you can, for now, I'd recommend using nft to manage your host firewall rules to ensure you can manage them to play nicely with Firezone.
from firezone.
w202mg
commented on May 13, 2024
Just reinstalled the OS and went through the steps. The web UI is running, but when I click on the button add device nothing is happening (just the UI is starting to reload all the time) and the console in Firefox is showing the error:
Firefox can’t establish a connection to the server at wss://fire.example.net/live/websocket?_csrf_token=BTZTADgoMT8vWCcyFRkWG3VqJTMxNDFWDO0srDbry5eUM4Xs09HZtRXf&_track_static%5B0%5D=https%3A%2F%2Ffire.example.net%2Fcss%2Fapp-8a84595dc71805006e616108a9a014ec.css%3Fvsn%3Dd&_track_static%5B1%5D=https%3A%2F%2Ffire.example.net%2Fjs%2Fapp-6b53778b5885d78b50638f9c9c863bd5.js%3Fvsn%3Dd&_mounts=0&vsn=2.0.0.
and
app-6b53778b5885d78b50638f9c9c863bd5.js:2:69490
from firezone.
jamilbk
commented on May 13, 2024
@w202mg This typically happens when the FQDN used in the URL bar to access your site isn't the same as the default['firezone']['fqdn'] configuration variable. Those need to match for the WebSockets to securely connect.
If they're the same, try clearing your browser cookies for that FQDN and reloading.
from firezone.
w202mg
commented on May 13, 2024
OK, I had to adopt the config from default['firezone']['fqdn'] = (node['fqdn'] || node['fire.example.net/devices']).downcase to default['firezone']['fqdn'] = 'fire.example.net'. Now I can add the device but there is no internet connection.
Here is the output.
root@debian:/home/as# sudo lsof -i -P -n | grep LISTEN
epmd 617 firezone 3u IPv4 16571 0t0 TCP *:4369 (LISTEN)
epmd 617 firezone 4u IPv6 16572 0t0 TCP *:4369 (LISTEN)
nginx 2385 root 6u IPv4 27866 0t0 TCP *:80 (LISTEN)
nginx 2385 root 7u IPv4 27867 0t0 TCP *:443 (LISTEN)
nginx 2386 firezone 6u IPv4 27866 0t0 TCP *:80 (LISTEN)
nginx 2386 firezone 7u IPv4 27867 0t0 TCP *:443 (LISTEN)
nginx 2387 firezone 6u IPv4 27866 0t0 TCP *:80 (LISTEN)
nginx 2387 firezone 7u IPv4 27867 0t0 TCP *:443 (LISTEN)
nginx 2388 firezone 6u IPv4 27866 0t0 TCP *:80 (LISTEN)
nginx 2388 firezone 7u IPv4 27867 0t0 TCP *:443 (LISTEN)
nginx 2389 firezone 6u IPv4 27866 0t0 TCP *:80 (LISTEN)
nginx 2389 firezone 7u IPv4 27867 0t0 TCP *:443 (LISTEN)
beam.smp 2395 firezone 17u IPv4 27642 0t0 TCP *:43203 (LISTEN)
beam.smp 2395 firezone 31u IPv4 27900 0t0 TCP 127.0.0.1:13000 (LISTEN)
postgres 2462 firezone 5u IPv4 23518 0t0 TCP 127.0.0.1:15432 (LISTEN)
from firezone.
w202mg
commented on May 13, 2024
by the way, I want to run also other instances in this server using nginx. but nginx is not starting because ports are busy by Firezone. Is there a way to make also other instances running on same server using nginx?
Thanks!
from firezone.
jamilbk
commented on May 13, 2024
Now I can add the device but there is no internet connection.
Do you have ufw rules active? If so, these are probably interfering with Firezone, as noted in the README. If you need to modify firewall rules outside of Firezone, you'll have much better luck using nftables: http://netfilter.org
Firezone ships a copy of the nft utility at /opt/firezone/embedded/sbin/nft which you can use to view rulesets (and perform other rule modifications), e.g.:
$ /opt/firezone/embedded/sbin/nft list rulesetIs there a way to make also other instances running on same server using nginx?
Sure. Just change the Firezone listen ports in /etc/firezone/firezone.rb to something other than 80 and 443:
default['firezone']['nginx']['non_ssl_port'] = 8080
default['firezone']['nginx']['ssl_port'] = 8443from firezone.
w202mg
commented on May 13, 2024
The web UI is running (but have to add :port now to the UI address because I changed the listening port in the config file) but I'm not getting any internet access. If you would have some advice it would be great!
Thank you!
from firezone.
jamilbk
commented on May 13, 2024
The web UI is running (but have to add :port now to the UI address because I changed the listening port in the config file) but I'm not getting any internet access. If you would have some advice it would be great!
Thank you!
Your firewall rules are likely interfering with Firezone. Could you please post the output of sudo iptables -L, sudo ufw status and /opt/firezone/embedded/sbin/nft list ruleset?
from firezone.
w202mg
commented on May 13, 2024
At the moment I didn't setup any firewall to get Firezon run first.
root@debian:/home/as# sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
root@debian:/home/as# sudo ufw status
sudo: ufw: command not found
root@debian:/home/as# /opt/firezone/embedded/sbin/nft list ruleset
table inet firezone {
chain forward {
type filter hook forward priority filter; policy accept;
}
chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
oifname "eno1" masquerade random,persistent
}
}
from firezone.
jamilbk
commented on May 13, 2024
@w202mg Do you mean your device is unable to access the Internet when connected to your Firezone instance?
Are you using a fresh install of Debian 11? What WireGuard client are you using?
You can check to ensure the WireGuard handshakes are occurring once your device connects, e.g.:
root@debian11:~# /opt/firezone/embedded/bin/wg
interface: wg-firezone
public key: 5A4HFG/2VLxyS7zBmjXKe7qMiKuzcytIjj03MBWgskc=
private key: (hidden)
listening port: 51820
peer: p9xTMRDRccIqA3o78EWm+4Ak+MPLIq18FKQZmvcnuGc=
endpoint: 11.55.134.11:55387
allowed ips: 10.3.2.2/32, fd00:3:2::2/128
latest handshake: 1 minute, 33 seconds ago
transfer: 375.88 KiB received, 648.08 KiB sentI just tested the 0.1.11 release on a fresh Debian 11 install using the macOS WireGuard client to connect to Firezone and I can't seem to reproduce your issue. If you could share a Vagrantfile that demonstrates the problem I'd be happy to look into this further, but at this point I'm really just guessing.
from firezone.
jamilbk
commented on May 13, 2024
Looks like you're missing libcap. Try apt-get install libcap2-bin.
To uninstall Firezone, use the uninstall script as described in the README section as this will ensure all parts of Firezone are removed.
from firezone.
w202mg
commented on May 13, 2024
root@debian:/home/as# apt-get install libcap2-bin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libcap2-bin is already the newest version (1:2.44-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
from firezone.
jamilbk
commented on May 13, 2024
Hmm. setcap is pretty standard and should be there unless it was moved / deleted somehow. Have you modified your PATH variable? Could you provide the output of echo $PATH and whereis setcap please?
from firezone.
jamilbk
commented on May 13, 2024
@w202mg Thanks for the info. Let me look into this a bit further and see what the issue could be. Stay posted.
from firezone.
jamilbk
commented on May 13, 2024
@w202mg I filed bug #283 to track the reboot issue. Expect a fix the next few days. Thanks for all the feedback!
from firezone.
cowb01
commented on May 13, 2024
Hi,
I am experiencing the same issue. Any resolve this?
from firezone.
jamilbk
commented on May 13, 2024
Hi @cowb01, I think there were a few issues we covered in this thread. Since a lot has changed in Firezone since then, would you mind re-opening a new issue with the following details? That'll help me triage more quickly:
- Firezone version
- OS and kernel version
- The output of
firezone-ctl logs
Thanks in advance!
from firezone.
Related Issues (20)
- DNS mapping fails during roaming if new Relays are received in `reconnect` HOT 3
- Roaming takes 30s to recover if new Relays are received in `reconnect`
- Crash in `setDns` for edge cases onLinkPropertiesChanged
- Allow overriding `account_name` from Stripe metadata HOT 1
- bug(windows-client): Getting impossible error
- bug(connlib): connlib doesn't write to new logfile after logs are cleared HOT 5
- bug(windows-client): wintun failing to create adapter
- bug(scripts): Update gateway upgrade script to handle new permalinks HOT 3
- bug: debug symbols for IPC service aren't getting included in CI artifacts HOT 1
- change `firezone-gui-client` to `firezone-client-gui` to match new binary names
- Add version numbers to the install client docs
- Move "Danger Zone" in views to the top details card
- bug(headless-client): Headless Client won't revert `/etc/resolv.conf` when `on_disconnect` is called
- Add `blocled_tx` to gateway metrics
- Send traffic filter down to clients as part of the resources
- Make sure the standalone / headless Client enforces single-instance HOT 1
- Prop tests for traffic filtering
- Integration tests for traffic filtering
- "Too many DNS queries" HOT 3
- Add monitor alerts to Linux Client Monitor VM HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from firezone.