# Server Settings: "Proxy IP" is not being used at all?

**URL:** <https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340>\
**Category:** Archive\
**Created:** [June 3, 2025, 5:28am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340 "2025-06-03T05:28:57Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 3, 2025, 5:28am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/1 "2025-06-03T05:28:57Z")

</div>

I have an Allstarlink Server (Raspberry Pi with the official Image) running inside a network which  
can’t have/does not support port forwarding. So what I did is settings up a proxy server for UDP port 4569 on a server in the Internet (IP is 65.109.113.117 as shown in the screenshot below).

When I directly connect to this IP on port 4569 with my SharkRF M1KE it works perfectly.

However, in the list of nodes/servers, when I select my server (DO1MJ), a different IP address shows up (probably the external IP of my home network) and not the Proxy IP I configured in the server settings. It seems like this setting is not being used?

What can I do to solve this?

 ![CleanShot 2025-06-02 at 19.43.59](https://community.allstarlink.org/uploads/default/original/2X/d/d734914244984ddc3e1e55e044a64b6a2725874a.png)

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [June 3, 2025, 5:48am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/2 "2025-06-03T05:48:06Z")

</div>

While I might be off on this,  
Don't you still need to register with that proxy IP ?

What is the node number ?  
What IP/Port does it show in the registration database ? That is what is actually used.

You did not mention if this was asl3 and I have learned not to assume.

.

---

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 3, 2025, 9:05am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/3 "2025-06-03T09:05:29Z")

</div>

Hello Mike,

yes, it's ASL3, Node Number is 65412, yes, I need to register with the static Proxy IP because my Node is behind Carried Grade NAT with no way in for any traffic. The IP address that is being sent in the list of all Allstarlink-Nodes is "176.83.120.23" and not "65.109.113.117".

I hope this helps! 73, Marc

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [June 3, 2025, 1:29pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/4 "2025-06-03T13:29:18Z")

</div>

Well, I have never used a proxy with asl, but you kinda answered yourself.

When registering, the server is using it's actual WAN IP.

You need to change something likely in your network so it's registering with your proxy.

The registration system updates frequently to catch changes, so whatever ip it registers with is what it uses and puts in the node list to be securely evaluated for connection.  
I have to say I don't know what the setting in the self service portal actually does.  
It does seem natural to think it would change what is being reported in the node list data.

I believe there is a way to setup a second network and select it on same if.  
No experience with such things, so, perhaps someone has a better answer.

But it seems from your text that what you actually need is a port proxy.  
Can't you use a different port and port and forward it to the needed port at your router ?

If you fail to get a resolution, perhaps try the helpdesk on the proxy in the self service.

Someone may chime in that has done this.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [June 3, 2025, 3:41pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/5 "2025-06-03T15:41:13Z")

</div>

Specifying a proxy IP for a server, and then associating one or more nodes to that server, will cause the proxy IP used in the connection database rather than the 'discovered' IP address. Calling it a "proxy" is incorrect nomenclature. It's basically "My IP is always this regardless of what the registration servers see". It's only useful/functional in a very limited set of advanced circumstances.

---

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 4, 2025, 6:46am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/6 "2025-06-04T06:46:33Z")

</div>

Yes, that is also what I thought. But my point is: it's not working. I entered a "Proxy IP" in the server settings and attached a node to it and still this Proxy IP is not being delivered from the connection database. So it seems like there is something wrong with this setting...

---

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 4, 2025, 6:48am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/7 "2025-06-04T06:48:35Z")

</div>

Hello Mike, thanks for all the information. I contacted the helpdesk already and they asked me to contact the community because it's not something that they can help with.

---

<div class="post-metadata">

**Author:** ![KK6RQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6rq/32/3511_2.png) [@KK6RQ](https://community.allstarlink.org/u/KK6RQ)\
**Post date:** [June 4, 2025, 8:02am UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/8 "2025-06-04T08:02:07Z")

</div>

I think he meant to say webportal rather than helpdesk.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [June 4, 2025, 12:42pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/9 "2025-06-04T12:42:21Z")

</div>

Can you provide an example?

---

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 4, 2025, 1:08pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/10 "2025-06-04T13:08:37Z")

</div>

Sure. With my SharkRF M1KE, when I connect to my Node DO1MJ (65412), the IP address in the node list is the one shown in the image. My expectation would be that the static configured "ProxyIP" (65.109.113.117) is returned but it seems it's not. You can try it yourself. Search for "DO1MJ" in the node list and when the IP address of the node is not "65.109.113.117" it's not the correct one.

 ![CleanShot 2025-06-04 at 15.05.07](https://community.allstarlink.org/uploads/default/original/2X/b/b20f0927389d13cb918697233f3b910e62664467.png)

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [June 4, 2025, 1:53pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/11 "2025-06-04T13:53:21Z")

</div>

I'm not sure what app you're looking at there but the AllStarLink database is returning 65.109.113.117 for node 65412. That is what is configured in the ASL portal for your server labelled "PRIVATE" and what's in the DNS and file databases:

```bash
$ dig +short 65412.nodes.allstarlink.org
65.109.113.117

$ wget -O- -q https://snodes.allstarlink.org/diffnodes.php | grep 65412
65412=radio@65.109.113.117:4569/65412,65.109.113.117

```

---

<div class="post-metadata">

**Author:** ![DO1MJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@DO1MJ](https://community.allstarlink.org/u/DO1MJ)\
**Post date:** [June 4, 2025, 3:23pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/12 "2025-06-04T15:23:48Z")

</div>

Hello, thanks, that was exactly the answer I was looking for.

So it seems like it's a problem with the SharkRF M1KE device which does not update the database frequently enough or delivers a false response.

Thank you, I'll contact the SharkRF support.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [June 4, 2025, 3:29pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/13 "2025-06-04T15:29:20Z")

</div>

Ah okay... I've never seen a SharkRF so I didn't know that's where that window came from.

---

<div class="post-metadata">

**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\
**Post date:** [June 7, 2025, 3:29pm UTC](https://community.allstarlink.org/t/server-settings-proxy-ip-is-not-being-used-at-all/23340/14 "2025-06-07T15:29:39Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
