# Expose wireguard servers endpoint on gl-sdk

**URL:** <https://forum.gl-inet.com/t/expose-wireguard-servers-endpoint-on-gl-sdk/68356>\
**Category:** Feedback\
**Created:** [April 25, 2026, 3:55pm UTC](https://forum.gl-inet.com/t/expose-wireguard-servers-endpoint-on-gl-sdk/68356 "2026-04-25T15:55:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xize11](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/xize11/32/5340_2.png) [@xize11](https://forum.gl-inet.com/u/xize11)\
**Post date:** [April 25, 2026, 3:55pm UTC](https://forum.gl-inet.com/t/expose-wireguard-servers-endpoint-on-gl-sdk/68356/1 "2026-04-25T15:55:56Z")

</div>

Hello,

I think it would be nice to have the endpoint field inside the profiles section visible and it's port.

As how the current behaviour is:

Normally under the expected situation the profile peer gets automatically the endpoint defined from wan which gets fetched from ip.sb I think, because it even shows my public ip on dual nat.

This will work in alot of situations.

But this fail to work when the router is a second router, whereas the first router portforwards, or when the upstream router routes a vpn, then the endpoint for wan shows the vpn ip.

I'm not requesting to change the automatic behaviour, but I think there needs head room to manually set the endpoint and port in the profile/peer and so on the QR code gets adjusted.

Currently I have Brume3 sitting as a backup vpn server I really want to have my configuration map to a specific port and endpoint.

This is also usefull if one already has a different ddns setup other than glddns on a upstream router which already routes on vpn too.

---

<div class="post-metadata">

**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\
**Post date:** [April 27, 2026, 1:35am UTC](https://forum.gl-inet.com/t/expose-wireguard-servers-endpoint-on-gl-sdk/68356/2 "2026-04-27T01:35:57Z")

</div>

Hi

Thank you for your suggestion.

The feature to allow custom addresses when exporting VPN configuration profiles from the VPN server page is already on roadmap.

---

<div class="post-metadata">

**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\
**Post date:** [August 13, 2026, 9:51am UTC](https://forum.gl-inet.com/t/expose-wireguard-servers-endpoint-on-gl-sdk/68356/5 "2026-08-13T09:51:59Z")

</div>