github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #6388] wireguard: cannot connect to server (configuration issue) #3259

New issue
Closed
opened 2026-05-05 09:52:10 -06:00 by gitea-mirror · 5 comments
gitea-mirror commented 2026-05-05 09:52:10 -06:00
Owner
Copy link

Originally created by @luckylinux on GitHub (Jun 19, 2024).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6388

Description

Describe the bug
Wireguard cannot connect to external Server. Apparently (looking at my OPNSense Router/Firewall=, there is (ALMOST) no attempt at even trying to connect to the Remote Server. I think there was like 1 connection attempt within a Day or so (and not sure if I was playing with some sysctls or what at that point).

I had setup some Wireguard stuff in my Homelab between 2 Debian Machines (without firejail & with apparmor disabled) and no problems there. Connection occurs immediately.

I don't blame it all on firejail, it might be a combination with apparmor (missing) Rules.

There is definitively some cryptic apparmor Entry in dmesg with DENIED status.

Steps to Reproduce

Steps to reproduce the behavior

This is probably not only firejail related, since the wg Program appears to be resolving to /usr/bin/wg, NOT /usr/local/bin/wg. I don't even know if there is a Wireguard Profile ...

root@HOST:/# which wg
/usr/bin/wg

Expected behavior

What you expected to happen
Wireguard connecting successfully to Remote Server.

Actual behavior

What actually happened
Wireguard failing / not even trying to connect to Remote Server.

Behavior without a profile

What changed calling LC_ALL=C firejail --noprofile /path/to/program in a
terminal?
Probably not relevant (see above).

Additional context

Any other detail that may help to understand/debug the problem
Output of sysctl -a attached.

Environment

  • Ubuntu GNU/Linux 24.04 Noble AMD64
  • Firejail version (firejail --version): firejail version 0.9.72
  • If you use a development version of firejail, also the commit from which it was compiled (git rev-parse HEAD): N/A
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Consumed 27ms CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit wg-quick@wg0.service completed and consumed the indicated resources.
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Will spawn child (service_enter_start): /usr/bin/wg-qui>
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Passing 0 fds to service
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: About to execute: /usr/bin/wg-quick up wg0
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Forked /usr/bin/wg-quick as 297436
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Changed dead -> start
Jun 19 18:51:35 HOST systemd[1]: Starting wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0...
░░ Subject: A start job for unit wg-quick@wg0.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit wg-quick@wg0.service has begun execution.
░░ 
░░ The job identifier is 114526.
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Child 297436 belongs to wg-quick@wg0.service.
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Main process exited, code=exited, status=0/SUCCESS (suc>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit wg-quick@wg0.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 0.
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Changed start -> exited
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Job 114526 wg-quick@wg0.service/start finished, result=>
Jun 19 18:51:35 HOST systemd[1]: Finished wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0.
░░ Subject: A start job for unit wg-quick@wg0.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit wg-quick@wg0.service has finished successfully.
░░ 
░░ The job identifier is 114526.
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Failed to send unit change signal for wg-quick@wg0.serv>
Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Control group is empty.

Checklist

  • The issues is caused by firejail (i.e. running the program by path (e.g. /usr/bin/vlc) "fixes" it).
  • I can reproduce the issue without custom modifications (e.g. globals.local).
  • The program has a profile. (If not, request one in https://github.com/netblue30/firejail/issues/1139)
  • The profile (and redirect profile if exists) hasn't already been fixed upstream.
  • I have performed a short search for similar issues (to avoid opening a duplicate).
    • I'm aware of browser-allow-drm yes/browser-disable-u2f no in firejail.config to allow DRM/U2F in browsers.
  • I used --profile=PROFILENAME to set the right profile. (Only relevant for AppImages)

Log

Output of LC_ALL=C firejail /path/to/program 

output goes here

Output of LC_ALL=C firejail --debug /path/to/program 

output goes here

Originally created by @luckylinux on GitHub (Jun 19, 2024). Original GitHub issue: https://github.com/netblue30/firejail/issues/6388 <!-- See the following links for help with formatting: https://guides.github.com/features/mastering-markdown/ https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax --> ### Description _Describe the bug_ Wireguard cannot connect to external Server. Apparently (looking at my OPNSense Router/Firewall=, there is (ALMOST) no attempt at even trying to connect to the Remote Server. I think there was like 1 connection attempt within a Day or so (and not sure if I was playing with some sysctls or what at that point). I had setup some Wireguard stuff in my Homelab between 2 Debian Machines (without firejail & with apparmor disabled) and no problems there. Connection occurs immediately. I don't blame it all on `firejail`, it might be a combination with `apparmor` (missing) Rules. There is definitively some cryptic `apparmor` Entry in `dmesg` with `DENIED` status. ### Steps to Reproduce _Steps to reproduce the behavior_ This is probably not only `firejail` related, since the `wg` Program appears to be resolving to `/usr/bin/wg`, NOT `/usr/local/bin/wg`. I don't even know if there is a Wireguard Profile ... ``` root@HOST:/# which wg /usr/bin/wg ``` ### Expected behavior _What you expected to happen_ Wireguard connecting successfully to Remote Server. ### Actual behavior _What actually happened_ Wireguard failing / not even trying to connect to Remote Server. ### Behavior without a profile _What changed calling `LC_ALL=C firejail --noprofile /path/to/program` in a terminal?_ Probably not relevant (see above). ### Additional context _Any other detail that may help to understand/debug the problem_ Output of `sysctl -a` attached. ### Environment - Ubuntu GNU/Linux 24.04 Noble AMD64 - Firejail version (`firejail --version`): `firejail version 0.9.72` - If you use a development version of firejail, also the commit from which it was compiled (`git rev-parse HEAD`): N/A ``` Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Consumed 27ms CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit wg-quick@wg0.service completed and consumed the indicated resources. Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Will spawn child (service_enter_start): /usr/bin/wg-qui> Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Passing 0 fds to service Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: About to execute: /usr/bin/wg-quick up wg0 Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Forked /usr/bin/wg-quick as 297436 Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Changed dead -> start Jun 19 18:51:35 HOST systemd[1]: Starting wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0... ░░ Subject: A start job for unit wg-quick@wg0.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit wg-quick@wg0.service has begun execution. ░░ ░░ The job identifier is 114526. Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Child 297436 belongs to wg-quick@wg0.service. Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Main process exited, code=exited, status=0/SUCCESS (suc> ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit wg-quick@wg0.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 0. Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Changed start -> exited Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Job 114526 wg-quick@wg0.service/start finished, result=> Jun 19 18:51:35 HOST systemd[1]: Finished wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0. ░░ Subject: A start job for unit wg-quick@wg0.service has finished successfully ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit wg-quick@wg0.service has finished successfully. ░░ ░░ The job identifier is 114526. Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Failed to send unit change signal for wg-quick@wg0.serv> Jun 19 18:51:35 HOST systemd[1]: wg-quick@wg0.service: Control group is empty. ``` ### Checklist <!-- Note: Items are checked with an "x", like so: - [x] This is a checked item. --> - [ ] The issues is caused by firejail (i.e. running the program by path (e.g. `/usr/bin/vlc`) "fixes" it). - [ ] I can reproduce the issue without custom modifications (e.g. globals.local). - [ ] The program has a profile. (If not, request one in `https://github.com/netblue30/firejail/issues/1139`) - [ ] The profile (and redirect profile if exists) hasn't already been fixed [upstream](https://github.com/netblue30/firejail/tree/master/etc). - [ ] I have performed a short search for similar issues (to avoid opening a duplicate). - [ ] I'm aware of `browser-allow-drm yes`/`browser-disable-u2f no` in `firejail.config` to allow DRM/U2F in browsers. - [ ] I used `--profile=PROFILENAME` to set the right profile. (Only relevant for AppImages) ### Log <details> <summary>Output of <code>LC_ALL=C firejail /path/to/program</code></summary> <p> ``` output goes here ``` </p> </details> <details> <summary>Output of <code>LC_ALL=C firejail --debug /path/to/program</code></summary> <p> <!-- If the output is too long to embed it into the comment, create a secret gist at https://gist.github.com/ and link it here. --> ``` output goes here ``` </p> </details>
gitea-mirror 2026-05-05 09:52:10 -06:00
gitea-mirror commented 2026-05-05 09:52:13 -06:00
Author
Owner
Copy link

@luckylinux commented on GitHub (Jun 19, 2024):

sysctl.txt

<!-- gh-comment-id:2179184110 --> @luckylinux commented on GitHub (Jun 19, 2024): [sysctl.txt](https://github.com/user-attachments/files/15904040/sysctl.txt)
gitea-mirror commented 2026-05-05 09:52:14 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Jun 26, 2024):

There is definitively some cryptic apparmor Entry in dmesg with DENIED
status.

This looks like a potential duplicate of #6389.

Does the problem still happen after running sudo firecfg --clean and
rebooting?

This is probably not only firejail related, since the wg Program appears
to be resolving to /usr/bin/wg, NOT /usr/local/bin/wg. I don't even know
if there is a Wireguard Profile ...

There isn't.

root@HOST:/# which wg
/usr/bin/wg

What is the output of the following commands:

which -a wg
ls -l /usr/bin/wg
<!-- gh-comment-id:2192559388 --> @kmk3 commented on GitHub (Jun 26, 2024): > There is definitively some cryptic `apparmor` Entry in `dmesg` with `DENIED` > status. This looks like a potential duplicate of #6389. Does the problem still happen after running `sudo firecfg --clean` and rebooting? > This is probably not only `firejail` related, since the `wg` Program appears > to be resolving to `/usr/bin/wg`, NOT `/usr/local/bin/wg`. I don't even know > if there is a Wireguard Profile ... There isn't. > ``` > root@HOST:/# which wg > /usr/bin/wg > ``` What is the output of the following commands: ```sh which -a wg ls -l /usr/bin/wg ```
gitea-mirror commented 2026-05-05 09:52:15 -06:00
Author
Owner
Copy link

@luckylinux commented on GitHub (Jun 27, 2024):

What is the output of the following commands:

which -a wg
ls -l /usr/bin/wg

root@HOST:/# which -a wg
/usr/bin/wg
/bin/wg
root@HOST:/# ls -l /usr/bin/wg
-rwxr-xr-x 1 root root 101672 Apr  8 18:22 /usr/bin/wg
<!-- gh-comment-id:2194008587 --> @luckylinux commented on GitHub (Jun 27, 2024): > What is the output of the following commands: > > ```shell > which -a wg > ls -l /usr/bin/wg > ``` ```shell root@HOST:/# which -a wg /usr/bin/wg /bin/wg root@HOST:/# ls -l /usr/bin/wg -rwxr-xr-x 1 root root 101672 Apr 8 18:22 /usr/bin/wg ```
gitea-mirror commented 2026-05-05 09:52:16 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Jul 4, 2024):

root@HOST:/# which -a wg
/usr/bin/wg
/bin/wg
root@HOST:/# ls -l /usr/bin/wg
-rwxr-xr-x 1 root root 101672 Apr  8 18:22 /usr/bin/wg

So wireguard does not have a profile and is not using any symlinks either.

Does the problem still happen after running sudo firecfg --clean and
rebooting?

This question still remains.

If you can demonstrate that the issue is indeed caused by firejail, feel free
to add a comment.

Closing as a likely duplicate of #6389.

<!-- gh-comment-id:2208347277 --> @kmk3 commented on GitHub (Jul 4, 2024): > ```shell > root@HOST:/# which -a wg > /usr/bin/wg > /bin/wg > root@HOST:/# ls -l /usr/bin/wg > -rwxr-xr-x 1 root root 101672 Apr 8 18:22 /usr/bin/wg > ``` So wireguard does not have a profile and is not using any symlinks either. > Does the problem still happen after running `sudo firecfg --clean` and > rebooting? This question still remains. If you can demonstrate that the issue is indeed caused by firejail, feel free to add a comment. Closing as a likely duplicate of #6389.
gitea-mirror commented 2026-05-05 09:52:18 -06:00
Author
Owner
Copy link

@luckylinux commented on GitHub (Jul 4, 2024):

@kmk3: Sorry for the Trouble 😞.

Actually this specific Issue one was neither caused by firejail neither by System Hardening.

I needed to add this to the end of /etc/wireguard/wg0.conf on both Server and Client at the End of the [Peer] Section:

# This is for if you're behind a NAT and
# want the connection to be kept alive.
PersistentKeepalive = 25

Then it works like a Charm 👍.

<!-- gh-comment-id:2208430401 --> @luckylinux commented on GitHub (Jul 4, 2024): @kmk3: Sorry for the Trouble :disappointed:. Actually **this** specific Issue one was neither caused by `firejail` neither by System Hardening. I needed to add this to the end of `/etc/wireguard/wg0.conf` on both Server and Client at the End of the `[Peer]` Section: ``` # This is for if you're behind a NAT and # want the connection to be kept alive. PersistentKeepalive = 25 ``` Then it works like a Charm :+1:.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#3259
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?