# Accessing node-red on port 1880 through public url with nginx or caddy

**URL:** <https://forums.balena.io/t/accessing-node-red-on-port-1880-through-public-url-with-nginx-or-caddy/370853>\
**Category:** Product support\
**Created:** [July 10, 2024, 10:00am UTC](https://forums.balena.io/t/accessing-node-red-on-port-1880-through-public-url-with-nginx-or-caddy/370853 "2024-07-10T10:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![cheezymcsquibble](https://avatars.discourse-cdn.com/v4/letter/c/a183cd/32.png) [@cheezymcsquibble](https://forums.balena.io/u/cheezymcsquibble)\
**Post date:** [July 28, 2024, 4:10pm UTC](https://forums.balena.io/t/accessing-node-red-on-port-1880-through-public-url-with-nginx-or-caddy/370853/6 "2024-07-28T16:10:35Z")

</div>

I managed to do it using this post: [Add nginx reverse proxy - #3 by ajlennon](https://forums.balena.io/t/add-nginx-reverse-proxy/368792/3)

The trick is to make sure every service’s base url has to be changed to accept the subfolder, so for node-red the settings.js had to be changed to include:

```auto
httpAdminRoot: '/node-red',

```

Also the Traefik solution is more practical because I only need to change the docker compose file for each change. With caddy I need to purge my data each time and upload a new caddy file.

---

_[View the full topic](https://forums.balena.io/t/accessing-node-red-on-port-1880-through-public-url-with-nginx-or-caddy/370853)._