• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Wireguard Site-to-Site Gateways disabled after reboot - service not starting

Scheduled Pinned Locked Moved WireGuard
35 Posts 9 Posters 4.6k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    lcbbcl @buzz2912
    last edited by Feb 25, 2023, 9:37 PM

    @buzz2912
    This is hilarious again after restart i got the GW disabled and i manually enabled the gateway, this made my tunnel work but the wireguard is not running.
    But still on others threads they claim that is working as it should.
    Well i will give a try also to open.
    Screenshot_20230225_222918.png
    Screenshot_20230225_223222.png

    1 Reply Last reply Reply Quote 1
    • B
      buzz2912
      last edited by Feb 25, 2023, 10:47 PM

      I do not understand what we do different.

      L 1 Reply Last reply Feb 26, 2023, 7:09 AM Reply Quote 0
      • L
        lcbbcl @buzz2912
        last edited by Feb 26, 2023, 7:09 AM

        @buzz2912
        We don't do nothing different , i did try everything. 1/10 reboots wg is working as it should so it is clear to me that is not how i set up. Its is something different, pppoe could be a coincidence or not. without adding a gw to the tunnel wg is coming up.

        1 Reply Last reply Reply Quote 0
        • V
          vjizzle
          last edited by Feb 26, 2023, 12:01 PM

          Hi,

          I have the same problem with wireguard tunnels. I am on 22.05 and there this problem also exists. Every reboot it’s a 50-50% chance my wireguard tunnels will come up.

          I was briefly on 23.01 and there 100% of the time my wireguard tunnels would not come back after a reboot. Reinstalling the wireguard package did fix it for the next reboot after reinstalling the package but every following reboot would turn up the same problem. Gateways disabled and wireguard tunnels and service both down and not way of enabling or starting them. Definitely a bug. I have pppoe as well on WAN.

          I returned to 22.05 because of a bug with igmp and for now this is ok. Hopefully some fixes will come for the next release. I read somewhere that on the other *sense firewall this problem does not exist. Wondering how they solved it 🧐

          L 1 Reply Last reply Feb 26, 2023, 12:42 PM Reply Quote 0
          • L
            lcbbcl @vjizzle
            last edited by Feb 26, 2023, 12:42 PM

            @vjizzle
            Well i have this problem long time ago, i moved from 2.6 to 22.01 22.05 and now 23. I had always pppoe connection and it did work in the past but after last updates to wg i start to have problems. I might try to use openvpn just to see because that was working years without any problems and now i see posts about openvpn also with similar problems.
            I don't expect bugs free, it is just that the bug was reported and they close saying that wg work as it should be.

            1 Reply Last reply Reply Quote 0
            • B buzz2912 referenced this topic on Mar 28, 2023, 9:23 PM
            • B
              buzz2912
              last edited by May 14, 2023, 9:28 PM

              Here is a workaround:

              Install package cron
              Add cron job

              Minute: @reboot
              user: root
              Command:
              sleep 60 && /usr/local/sbin/pkg install -f -y pfsense-pkg-WireGuard

              After reboot the wireguard pkg is force reinstalled. After that the service and the tunnels and the gateways come up. Takes some time.

              Hope that helps, Sebastian

              M M 2 Replies Last reply May 16, 2023, 1:45 PM Reply Quote 0
              • M
                Misterb @buzz2912
                last edited by May 16, 2023, 1:45 PM

                I've had this same problem since almost the start of the 2.7.0 dev releases appearing. The wireguard tunnel always comes up but the gateway reports as down and the wireguard service says it's down. I can return things to normal by going to Status->Services and restarting dpinger followed by starting wireguard. The service starts and the gateway on the front page comes back online.

                B 1 Reply Last reply May 16, 2023, 2:19 PM Reply Quote 0
                • B
                  buzz2912 @Misterb
                  last edited by May 16, 2023, 2:19 PM

                  @misterb
                  do you have a cron command for that?

                  I can not understand why this is not fixed after all this time.
                  It seems, that no one cares.

                  Sebastian

                  1 Reply Last reply Reply Quote 0
                  • M
                    moelassus @buzz2912
                    last edited by May 24, 2023, 3:09 AM

                    @buzz2912 Ugh, this is a good solution to a bad problem. It's a shame that Wireguard behaves like this. I didn't know I was experiencing this until I rebooted prior to upgrading and my peer would not handshake. I rebooted again and it came back. I thought I was out of the woods so I upgraded to 22.05 and Wireguard hasn't worked since. I just tried the uninstall reinstall and it did eventually work. It took awhile for the peer to handshake but it eventually did. I hadn't rebooted since the last update so hopefully I won't run into this again for a long time.

                    1 Reply Last reply Reply Quote 0
                    • G
                      Gektor
                      last edited by May 28, 2023, 3:04 PM

                      Have same issue on pfSense + 23.05, after Save + Apply WG Gateways, it's start wotking.

                      S 1 Reply Last reply Jun 29, 2023, 12:42 PM Reply Quote 0
                      • S
                        Seeking Sense @Gektor
                        last edited by Jun 29, 2023, 12:42 PM

                        @Gektor are you referring to the WireGuard INTERFACE that you created for your WireGuard tunnel found in the pfSense Interfaces list?

                        If so then I have also found that to be my only solution to reestablish my WireGuard tunnel.

                        I am required to DISABLE, SAVE and APPLY and then ENABLE, SAVE and APPLY the WireGuard Interface to reestablish my WireGuard tunnel.

                        Is there a fix for this?

                        Has anyone written a script to check if a WireGuard Gateway is down, offline, etc... to DISABLE and then ENABLE its associated interface?

                        M 1 Reply Last reply Jun 29, 2023, 1:45 PM Reply Quote 0
                        • M
                          michmoor LAYER 8 Rebel Alliance @Seeking Sense
                          last edited by Jun 29, 2023, 1:45 PM

                          @Seeking-Sense I would say to open a redmine if you believe this is a bug or a regression but the odds of that getting actioned by a dev are extremely low.
                          Have you tried disabling gateway monitoring?

                          Firewall: NetGate,Palo Alto-VM,Juniper SRX
                          Routing: Juniper, Arista, Cisco
                          Switching: Juniper, Arista, Cisco
                          Wireless: Unifi, Aruba IAP
                          JNCIP,CCNP Enterprise

                          S 1 Reply Last reply Jun 29, 2023, 1:55 PM Reply Quote 0
                          • S
                            Seeking Sense @michmoor
                            last edited by Seeking Sense Jun 29, 2023, 1:58 PM Jun 29, 2023, 1:55 PM

                            @michmoor said in Wireguard Site-to-Site Gateways disabled after reboot - service not starting:

                            Have you tried disabling gateway monitoring?

                            Sure have. Not only that but disabled take action as well.

                            And just to be clear the WireGuard Interface fails to come online after reboot.

                            B 2 Replies Last reply Jun 29, 2023, 2:00 PM Reply Quote 0
                            • B
                              buzz2912 @Seeking Sense
                              last edited by Jun 29, 2023, 2:00 PM

                              @Seeking-Sense
                              The Solution is restarting dpinger after reboot.
                              Search for my post in the solution for site to site gateway down after Reboot

                              M S 2 Replies Last reply Jun 29, 2023, 2:08 PM Reply Quote 0
                              • M
                                Misterb @buzz2912
                                last edited by Jun 29, 2023, 2:08 PM

                                What Buzz said, restart dpinger and then start Wireguard.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Seeking Sense @buzz2912
                                  last edited by Jun 29, 2023, 2:22 PM

                                  Thanks for the reply @buzz2912 I may have tried that in the past not exactly sure and just stumbled across the DISABLE & ENABLE Interface solution.

                                  I will reboot pfSense later and try your solution.

                                  Never the less I need an unattended automated method to implement your or my solution for the times that my internet connect flakes out or there is a power outage and yes I have pfSense on a UPS.

                                  Also WireGuard "is running" just not functioning when I DISABLE and ENABLE it's Interface.

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    buzz2912 @Seeking Sense
                                    last edited by buzz2912 Jun 29, 2023, 2:29 PM Jun 29, 2023, 2:26 PM

                                    @Seeking-Sense
                                    install cron and service watchdog. Add wireguard to service watchdog. Create a cron job @reboot && sleep 30 for designer restart Here is the link

                                    S 1 Reply Last reply Jun 29, 2023, 4:30 PM Reply Quote 0
                                    • S
                                      Seeking Sense @buzz2912
                                      last edited by Seeking Sense Jun 29, 2023, 4:34 PM Jun 29, 2023, 4:30 PM

                                      @buzz2912 are you saying to reinstall the WireGuard each time this happens? If so that is bonkers Or are you saying restart dpinger utilizing CRON and WATCHDOG?

                                      B 1 Reply Last reply Jun 29, 2023, 5:07 PM Reply Quote 0
                                      • B
                                        buzz2912 @Seeking Sense
                                        last edited by buzz2912 Jun 29, 2023, 5:08 PM Jun 29, 2023, 5:07 PM

                                        @Seeking-Sense
                                        At First i reinstalled. Now I am using dpinger restart

                                        M 1 Reply Last reply Jun 29, 2023, 5:12 PM Reply Quote 0
                                        • M
                                          Misterb @buzz2912
                                          last edited by Jun 29, 2023, 5:12 PM

                                          I've just installed 2.7.0-RELEASE and the same issue and fix exists.

                                          L S 2 Replies Last reply Jun 29, 2023, 7:30 PM Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received