# Get URL from within NodeRED

**URL:** <https://discourse.nodered.org/t/get-url-from-within-nodered/100269>\
**Category:** General\
**Created:** [29 January 2026 09:45 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269 "2026-01-29T09:45:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [29 January 2026 09:45 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269/1 "2026-01-29T09:45:28Z")

</div>

Can I get from within NR the Server NR is executed on?  
The log says

`29 Jan 10:37:07 - [info] Server wird jetzt auf http://127.0.0.1:1880/ ausgeführt`

and I want to get in NR the `http://127.0.0.1:1880/` part. If so, how?

Why: I show a QR code on the Dashboard to be scanned w/ a cellphone to open NR the Dashboard right there. Easy transfer, so to say.  
When I move the flow from test to production I have to modify manually / hard code that.

I found nothing.

Cheers, Uwe

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [29 January 2026 10:40 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269/2 "2026-01-29T10:40:16Z")

</div>

> [@duaw](#):
>
> I want to get in NR the `http://127.0.0.1:1880/` part. [to] show a QR code on the Dashboard ... to open NR the Dashboard right there.

I think every Node-red log on every computer will show `http://127.0.0.1:1880/` because it is IP language for "This computer" (plus the port number). It won't work to connect to Node-red from any other device.

There is a contrib node [node-red-contrib-ip](https://flows.nodered.org/node/node-red-contrib-ip) which returns the current IP address as msg.payload.internalIPv4

eg

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/d/9d6a7e71b2f614bb4d8673f295082318774e9c33.png)

---

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [29 January 2026 12:48 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269/3 "2026-01-29T12:48:57Z")

</div>

> [@jbudd](#):
>
> I think every Node-red log on every computer will show `http://127.0.0.1:1880/` because it is IP language for "This computer" (plus the port number). It won't work to connect to Node-red from any other device.

Nearly, but 100% correct. There are some checks in the startup logic.

If (as default) NR is configured with `uiHost: 0.0.0.0` (the special case that represents all IPv4 addresses available on the machine) it will still show `http://127.0.0.1:1880` as novice users are most likely to be running NR on the same machine as the browser.

If `uiHost` is set to anything else then the startup log will use this value in the displayed URL.

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [29 January 2026 14:29 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269/4 "2026-01-29T14:29:14Z")

</div>

> [@jbudd](#):
>
> There is a contrib node [node-red-contrib-ip](https://flows.nodered.org/node/node-red-contrib-ip) which returns the current IP address as msg.payload.internalIPv4

Oh, I missed that one. Works perfectly! Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [12 February 2026 14:29 UTC](https://discourse.nodered.org/t/get-url-from-within-nodered/100269/5 "2026-02-12T14:29:21Z")

</div>

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