• RC7 Wireguard did not start

    netsrot303

    By netsrot303

      • Minor

    After upgrading from RC5 to RC7, my wireguard tunnel no longer starts. When I try to activate the inactivity button the display immediately jumps back to inactive.

      

    May  6 17:53:38 Server wireguard: Tunnel WireGuard-wg0 started

    A wireguard process is not running either.

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    netsrot303

    i have already deleted the tunnel completely.
    As soon as I try to create a new peer via the GUI and then start the WG server, it immediately shuts down again.

     

    Edit: The problem seems to be when I try to create a configuration for ipv4 and ipv6.
    Unfortunately I can only create a configuration for ipv4 only.
    But since I have a cgnat connection I am dependent on ipv6. But with the older versions it still worked.

    Edited by netsrot303
    Link to comment
    bonienl

    This is a bug, I made an update to fix this.

    Keep in mind that VPN tunnels for Docker can only operate in ipv4 mode, but other tunnel type, e.g. remote access can work with both ipv4 and ipv6.

     

    • Thanks 1
    Link to comment
    netsrot303

    Is the update already released? With the current RC7 the bug still exists?
    Yes I'm really only interested in establishing the connection via ipv6. Internally ipv4 is good.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.