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

    Wireguard failing to save/create peer

    Scheduled Pinned Locked Moved WireGuard
    2 Posts 1 Posters 912 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.
    • CreationGuyC
      CreationGuy
      last edited by CreationGuy

      I have one tunnel set up with two peers. I just created an additional tunnel which seemed to have saved. I then added a new peer to that tunnel; when I go to save the peer, I get:

      There was a problem applying the changes. See the System Logs.
      

      and below that, the typical apply button. When I click apply it acts like it saves the peer but under status, the peer is not there.

      When I click on the link to go to the System Logs, /wg/status_logs.php, I get a 404....

      I found this in the pfsense status_logs, not sure if this helps:

      Oct 17 09:41:05 	php-fpm 	85817 	/wg/vpn_wg_peers.php: Gateway, NONE AVAILABLE
      Oct 17 09:41:05 	php-fpm 	85817 	/wg/vpn_wg_peers.php: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6' 
      
      CreationGuyC 1 Reply Last reply Reply Quote 0
      • CreationGuyC
        CreationGuy @CreationGuy
        last edited by CreationGuy

        I fixed it, it was my mistake.

        For those of you who may come across this, here's what I did wrong:

        I set the listen port for both tunnels to be the same, if I had read all of the documentation, I would have known that they need to be unique... :)

        1 Reply Last reply Reply Quote 1
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.